Guide
Tools and integrations
Agents act through tools: actions on an integration (search issues, create a ticket, send an email) or calls to your own API.
The 50 integrations in the beta
| How you connect | Integrations | What you need |
|---|---|---|
| Your own key (30) | HubSpot, Pipedrive, Zendesk, Freshdesk, Intercom, ServiceNow, Stripe, Shopify, Mailchimp, SendGrid, Linear, Asana, ClickUp, monday.com, Trello, Notion, Coda, Airtable, Figma, Miro, Sentry, Datadog, PagerDuty, Opsgenie, Statuspage, OpenAI, Anthropic, Amplitude, Mixpanel, Postman | Paste an API key or token from the provider. |
| Google sign-in (5) | Gmail, Google Calendar, Google Drive, Google Docs, BigQuery | Sign in with Google (BigQuery also takes a service account). |
| Sign in with the provider (8) | GitHub, Slack, Jira, Confluence, Salesforce, Outlook Mail, Outlook Calendar, OneDrive | Sign in with the provider through the OAuth tab. |
| Needs setup at the provider first (4) | Twilio, WhatsApp, Zoom, QuickBooks | A Twilio number; a Meta Business app and system-user token; a Zoom Server-to-Server OAuth app; an Intuit developer app. |
| Built in (3) | Web search, image generation, video generation | Nothing to connect. |
Your own API is a custom tool (an HTTP endpoint you describe), on top of these 50.
Connect an integration
Integrations > Catalog > Connect on the integration. Use the Manual tab to paste a key, or the OAuth tab to Sign in with …. Give the connection a name; Set as default makes it the one new agents pick. Connected integrations are listed under Connected.
Shared connection or each person's own account
In the agent builder, step 3 Tools & Integrations, every tool has an Access setting:
| Access | What happens | Use it for |
|---|---|---|
| Shared connection | Every call uses the integration's own connection (your team's key or sign-in). Every end user acts as the same account. | Internal agents; read-only lookups in your own systems. |
| Each person's own account | The tool acts with the signed-in connection of whoever is chatting. Each end user connects their own account once. | Agents that read or write a user's own mail, calendar or files. |
| Forward who is chatting | Custom tools only. Your API receives X-End-User-Id and X-Customer-Group-Id from Dezifi (only for hosts on your Trusted Endpoints list), never from the model. | Your own API, when it must answer only for the signed-in user. |
| Forward the user's own token / Exchange the user's token | Custom tools only. The user's token for your API (sealed into their session token when you mint it) is sent as the bearer, or exchanged for one. | Your API when it already authorizes by the user's own token. Not after an approval: see Known beta limits. |
Your own API as a tool
Add the API's host under Settings > Trusted Endpoints, then create the tool and choose Forward who is chatting. The model never chooses whose data is read: Dezifi asserts the identity from the session token. The support sample shows this end to end with
ApiEndpoint, TrustedEndpoint and ToolAuthMode.FORWARD_IDENTITY.