Integrations
Connect external services like HubSpot, Gmail, Slack, and more so AgentForce agents can call tools across them.
Integrations let AgentForce agents reach into the tools your team already uses. Once you connect a service to your workspace, every catalog agent gains access to tools that bridge into it — reading data, drafting messages, or pulling content.
Integrations are configured at the org level by an admin. Every agent in the catalog can use any connected integration; there's no per-agent gating.
Connecting an integration
Open workspace integrations
Navigate to Settings → Integrations (or /settings/integrations). You'll see a list of available services with their current connection status.
Connect a service
Click Connect on the service you want. You'll be redirected through the service's OAuth flow to authorize Opisense.
Authorize the connection
Grant the requested permissions. Opisense only requests the scopes it needs to power the agent tools — read access for most, write access for a few specific actions.
Confirm
Once OAuth completes, you'll land back in Opisense with the integration showing as Connected. The catalog agents can now call tools backed by this integration.
Available services
| Category | Services |
|---|---|
| Communication | Gmail, Slack, Twilio, SendGrid |
| CRM | HubSpot, Salesforce |
| Productivity | Notion, Airtable, Google Drive, Dropbox |
| Project management | Asana, Linear, Monday.com, Jira |
| Support | Intercom, Zendesk |
| Development | GitHub |
| Other | Stripe and more |
The exact list depends on your plan and what's enabled for your workspace. Check /settings/integrations for the current set.
How agents use integrations
Once a service is connected, agents can use it naturally during conversations:
- "Check Gmail for the latest message from Acme Corp."
- "Summarize this prospect's recent HubSpot activity."
- "Find the deal record for Globex and tell me where it is in the pipeline."
The agent decides which integration to call based on your request — you don't need to specify the service name. If multiple integrations could answer (e.g., both Salesforce and HubSpot), the agent will pick one based on context, or ask you to clarify.
Per-user vs. per-workspace connections
Most integrations connect at the workspace level — an admin connects once, and every member uses the shared connection. Agent tool calls happen as the workspace, not as the individual user.
A few integrations (notably Gmail) can be connected per user — each member authorizes their own account. This is for cases where the agent needs to act on behalf of a specific person rather than the workspace as a whole.
The connection flow tells you which model applies for each service.
Disconnecting
To disconnect a service, click Disconnect on its row in /settings/integrations. This:
- Revokes the OAuth token
- Removes the integration tools from every agent in the catalog
- Doesn't affect chat history that referenced the integration
Disconnecting is safe — you can reconnect later without losing any per-agent configuration.
What about custom integrations?
MCP (Model Context Protocol) servers can be connected to expose custom tools to agents. See Tools and integrations (builder) for how to wire them up in the builder.
Privacy
Each integration only accesses the scopes you authorized during the OAuth flow. Opisense doesn't read more than the agent tools need. Connection metadata (which services are connected, when they were last used) is logged for audit; the data the agent retrieves is scoped to the conversation and not persisted beyond what the agent's memory naturally retains.