Integrations
The Integrations plugin lets you connect external systems to the Booga Enterprise platform, automate data synchronization between them, and monitor both inbound and outbound webhook traffic — all from a single management console. Whether you need to pull files from cloud storage, exchange messages through Slack or Microsoft Teams, or stream financial market data, the integrations framework handles authentication, scheduling, and error recovery so you can focus on the data that matters.
Getting Started
Open Integrations from the sidebar. The plugin requires the integrations_access capability on your subscription and the INTEGRATIONS_MANAGE permission on your account.
When you first open the page you see the overview with three quick-action cards that link to the most common workflows:
| Quick Action | What It Does |
|---|---|
| Add Connection | Opens the Connector Library so you can browse and configure a new connector |
| Monitor Syncs | Jumps to the Sync Management tab to view synchronization status and metrics |
| Webhooks | Opens the Webhooks tab to review inbound and outbound webhook activity |
Interface Overview
The Integrations page is organized into tabs below the quick-action cards. The number of visible tabs depends on your capabilities and account privileges:
| Tab | Visibility | Description |
|---|---|---|
| Connections | All users | Browse, test, edit, and delete your configured connections |
| Webhooks | All users | Monitor inbound webhook events and outbound webhook deliveries |
| Sync Management | All users | View sync statistics, configure sync pipelines, and track execution history |
| Financial Data | Requires financial_data capability | Configure financial data provider routing and fallback strategies |
| Connector Registry | Superusers only | Manage the global catalog of available connector types |
Connections
The Connections tab displays all configured integration connections for your tenant with status indicators, last-tested timestamps, and quick actions.
Adding a Connection
- Click Add Connection from the quick-action card or the button in the Connections tab
- The Connector Library opens, showing all available connector types grouped by category
- Use the search bar or category filter chips (CRM, ERP, Communication, Storage, Analytics, Financial Data, Generic) to find the connector you need
- Click Configure on the connector card
- Fill in the configuration form — fields vary by connector type:
- OAuth 2.0 connectors (e.g., OneDrive, Google Drive, Slack) — provide client ID and client secret, then complete the OAuth authorization flow
- API Key connectors (e.g., Financial Modeling Prep, Alpha Vantage) — enter your API key and any required endpoint configuration
- Basic Auth connectors — provide username and password
- Webhook connectors — configure the endpoint path and event types
- Click Save to create the connection
After saving, the connection appears in the Connections list with an initial Inactive status. Test it to verify connectivity before using it in sync pipelines.
Connector Categories
| Category | Connectors | Typical Use |
|---|---|---|
| CRM | Salesforce, NetSuite | Customer data, sales pipelines, ERP records |
| Communication | Slack, Microsoft Teams, SendGrid Email, Twilio SMS | Messaging, notifications, alerts |
| Storage | OneDrive/SharePoint, Google Drive, Box, Dropbox Business | Cloud file import, document synchronization |
| Financial Data | Financial Modeling Prep, Alpha Vantage, Polygon.io, Bloomberg Open API | Market data, company financials, stock quotes |
| Generic | REST API, Webhook | Custom API endpoints and webhook receivers |
OAuth Authentication Patterns
OAuth connectors support two authentication patterns:
- App-Level — an administrator authenticates once and all users in the tenant share the resulting connection. Suitable for system-wide integrations like a shared Slack workspace
- User-Level — each user authenticates individually with their own account. Used for personal cloud storage services such as OneDrive or Google Drive where each user accesses their own files
For user-level OAuth connectors, each user sees a Connect button on the connection card. Clicking it opens the provider's authorization page in a new window. After you approve access, the platform securely stores your tokens and they refresh automatically.
Testing a Connection
Click Test on any connection card to verify that the credentials are valid and the external system is reachable. The connection status updates to reflect the result:
| Status | Meaning |
|---|---|
| Active | Connection is healthy and ready for use |
| Inactive | Connection has not been tested or has been manually deactivated |
| Error | The most recent test or sync failed — check the error message for details |
| Testing | A connectivity test is currently in progress |
API Playground
For REST API and webhook connectors, click Playground on the connection card to open an interactive testing environment. The API Playground lets you:
- Choose an HTTP method (GET, POST, PUT, DELETE)
- Enter a request path relative to the connection's base URL
- Add custom headers and a JSON request body
- Send the request and inspect the response status, headers, and body
This is useful for verifying that an endpoint behaves as expected before wiring it into a sync configuration.
Managing Connections
From the Connections list you can:
- Edit — update the connection name, description, or configuration
- Test — re-run the connectivity check
- Delete — permanently remove the connection (this also removes associated sync configurations)
- View webhook configuration — for webhook-type connectors, expand the card to see the webhook endpoint URL and secret for external system setup
Webhooks
The Webhooks tab is split into two subtabs — Inbound Webhooks and Outbound Webhooks.
Inbound Webhooks
Inbound webhooks are events received from external systems that trigger agent workflows inside the platform. The event log viewer shows a live feed of incoming webhook events with auto-refresh (every 15 seconds by default).
Each event entry displays:
- Event type and source connector
- Timestamp and processing status
- Payload preview
To configure which agents respond to incoming webhooks, click Manage Agents to navigate to the Agents plugin where webhook triggers are defined per agent.
Tip: Use the Refresh button to fetch the latest events immediately without waiting for auto-refresh.
Outbound Webhooks
Outbound webhooks send notifications to external systems when events occur inside the platform. The outbound panel shows delivery statistics (total deliveries, success rate, average delivery time) and a paginated log of recent deliveries.
Each delivery entry includes:
- Event type and subscription name
- Delivery status (pending, dispatched, delivered, failed, skipped)
- Response code and delivery time
- Retry count for failed deliveries
Outbound webhook subscriptions are managed in the Admin Portal under event configuration. The Integrations page provides a monitoring view only.
Sync Management
The Sync Management tab gives you a dashboard for data synchronization operations. It displays summary statistics at the top and a list of sync configurations below.
Dashboard Statistics
| Metric | Description |
|---|---|
| Total Syncs | Number of sync configurations across all connections |
| Active Syncs | Configurations currently enabled for scheduled or manual execution |
| Successful | Total executions that completed without errors |
| Failed | Total executions that encountered errors |
Creating a Sync Configuration
- Click New Sync Config in the Sync Management tab
- Select the source connection from the dropdown
- Configure the sync parameters:
| Parameter | Options |
|---|---|
| Sync Type | Full Sync (complete data replacement), Incremental Sync (new and updated records only), Delta Sync (change-based using timestamps or tracking tokens) |
| Direction | Inbound (pull from external system), Outbound (push to external system), Bidirectional (two-way sync) |
| Data Source | The table or endpoint in the external system to synchronize |
| Conflict Resolution | Source Wins, Target Wins, Latest Timestamp, or Manual Resolution |
- Optionally configure scheduling:
- Enable scheduled execution with a cron expression
- Set the timezone for the schedule
- Define field mappings and transformation rules as needed
- Save the configuration
Running a Sync
You can trigger a sync manually or let it execute on a schedule:
- Manual — click Run on the sync configuration row to start an immediate execution
- Scheduled — syncs run automatically according to the cron schedule. The scheduler plugin manages timing
- Webhook-triggered — syncs can be triggered by incoming webhook events
- Event-triggered — syncs can respond to internal platform events
Monitoring Executions
Each sync execution is tracked with detailed metrics:
| Metric | Description |
|---|---|
| Status | Pending, Running, Success, Partial Success, Failed, or Cancelled |
| Records Processed | Total records examined during the sync |
| Records Created | New records inserted into the target |
| Records Updated | Existing records modified |
| Records Failed | Records that encountered errors during processing |
| Duration | Total execution time |
Click on an execution row to view the full execution log, error details, and a breakdown of processed records.
Incremental and Delta Sync
For large datasets, full sync can be resource-intensive. Incremental and delta sync modes reduce load by processing only what has changed:
- Incremental Sync uses a stored checkpoint (timestamp, cursor, offset, or record ID) to resume from where the last sync left off
- Delta Sync uses a change tracking token from the external system to fetch only modified records
The platform automatically maintains sync state between executions. You can reset sync state to force a full re-sync when needed by using the reset action on the sync configuration.
Financial Data (Conditional)
If your subscription includes the financial_data capability, an additional tab lets you configure financial data provider routing for your tenant.
Provider Configuration
- Primary Provider — the first provider queried for financial data (e.g., Financial Modeling Prep)
- Fallback Provider — used when the primary provider is unavailable or rate-limited
Rate Limit Strategies
| Strategy | Behavior |
|---|---|
| Strict | Fail immediately when the provider returns a rate-limit error |
| Fallback | Automatically switch to the fallback provider on rate-limit errors |
| Queue | Queue requests and retry when the rate limit window resets |
Data Fusion
For advanced use cases, enable data fusion to combine responses from multiple providers into a single, enriched dataset. Configure fusion rules to specify how fields from different providers are merged when data overlaps.
Connector Registry (Superuser Only)
Superusers have access to the Connector Registry tab, which manages the global catalog of available connector types. The registry controls what appears in the Connector Library for all tenants.
Each registry entry defines:
- Connector type, name, and description
- Category and authentication method
- Complexity level and popularity badge
- Available features and supported data types
- Availability status (Active, Coming Soon, Deprecated, Maintenance)
- Link to the system-level connector instance (for shared or hybrid connectors)
System connectors can be configured with different management patterns:
| Pattern | Description |
|---|---|
| Shared Credentials | Platform provides API keys — all tenants use the same credentials |
| Tenant Template | Platform provides the connector template — tenants supply their own API keys |
| Bring Your Own Provider (BYOP) | Tenants must provide all credentials |
| Hybrid | Platform provides default credentials, tenants can optionally override with their own |
Cloud Storage Integration
Cloud storage connectors (OneDrive, Google Drive, Box, Dropbox) provide file browsing and import capabilities that integrate with the Files plugin:
- Connect your cloud storage account using user-level OAuth
- Browse your cloud folders and files directly from the platform
- Select files to import into the platform's file management system
- Track import progress and history
Imported files become available in the Files plugin for preview, sharing, knowledge base ingestion, and use in chat and agent workflows.
Best Practices
- Test connections immediately after creating them — verify credentials and network access before setting up sync pipelines. This catches configuration errors early
- Start with incremental sync for large datasets — full sync can be time-consuming on initial setup but switch to incremental or delta sync for ongoing operations to minimize resource usage
- Use the API Playground before building automations — test API endpoints interactively to understand response structures and error handling before configuring automated sync pipelines
- Monitor webhook delivery rates — review the outbound webhooks panel periodically to ensure delivery success rates remain high. Failed deliveries may indicate endpoint issues on the receiving side
- Organize connections with descriptive names — use clear names like "Slack - Engineering Alerts" or "OneDrive - Finance Team" so team members can quickly identify each connection's purpose
- Set up fallback providers for financial data — configure a secondary provider so that rate limits or outages on the primary provider do not interrupt data access
- Review sync execution history regularly — check for partial success or failed executions that may indicate data quality issues or schema changes in the external system
Troubleshooting
Cannot access the Integrations page
Problem: You see an "Access Denied" message when opening Integrations.
Solution: Your subscription needs the integrations_access capability and your account needs the INTEGRATIONS_MANAGE permission. Contact your administrator to enable access.
OAuth connection fails during authorization
Problem: The OAuth flow opens but returns an error or never completes. Solution: Verify that the client ID and client secret are correct and that the OAuth redirect URI is properly configured in the external provider's application settings. The platform's redirect URI is displayed in the connector configuration form.
Connection test shows Error status
Problem: A connection test fails and the status changes to Error. Solution: Check the error message on the connection card for details. Common causes include expired API keys, revoked OAuth tokens, network connectivity issues, or incorrect endpoint URLs. For OAuth connectors, try clicking Reauthorize to refresh the tokens.
Sync execution stuck in Running
Problem: A sync execution stays in Running status for an extended period. Solution: Sync operations on large datasets may take several minutes. If the execution does not complete after 30 minutes, check that the external system is responsive and that your infrastructure stack is healthy. You can cancel a stuck execution and retry.
Inbound webhook events not appearing
Problem: Events from an external system are not showing up in the webhook log. Solution: Verify that the external system is posting to the correct webhook endpoint URL and that the webhook secret matches. Check the connection status and ensure the webhook configuration is active.
Financial Data tab not visible
Problem: You do not see the Financial Data tab on the Integrations page.
Solution: The Financial Data tab requires the financial_data capability on your subscription. Contact your administrator to enable it if your plan supports financial data features.
Related Topics
- Files Management — User Guide
- AI Agents — User Guide
- Analytics & Insights — User Guide
- Knowledge Management — User Guide
⏱️ Read time: 14 minutes | 📊 Difficulty: intermediate | 🔄 Last updated: 2026-03-30