Integrations connect Tried to the tools your business already uses. There are three kinds, each with its own place in the dashboard:
| Kind | What it does | Where |
|---|---|---|
| Apps | Actions an agent can run during a call or chat: check availability, book, create a contact, open a ticket | Settings, Integrations, Apps |
| CRM sync | Push contacts and a call note to your CRM after every analysed call, plus full sync jobs | Settings, Integrations, CRM sync |
| Synced knowledge sources | Keep a knowledge base in step with a Google Drive folder, a OneDrive folder or a Notion page | Knowledge Base, Connect a folder |
Supported providers#
| Provider | App actions | CRM sync | Knowledge source | OAuth connect | Page |
|---|---|---|---|---|---|
| Cal.com | 5 | Yes | Cal.com | ||
| Calendly | 2 | Calendly | |||
| HubSpot | 2 | Yes | Yes | HubSpot | |
| Salesforce | 1 | Yes | Yes | Salesforce | |
| Microsoft Dynamics 365 | 1 | Yes | Yes | Dynamics 365 | |
| GoHighLevel | 1 | Yes | Yes | GoHighLevel | |
| Zoho CRM | 1 | Yes | Yes | Zoho CRM | |
| Zendesk | 1 | Zendesk | |||
| Google Drive | Yes | Yes | Synced sources | ||
| OneDrive | Yes | Yes | Synced sources | ||
| Notion | Yes | Yes | Synced sources |
Any other system can be reached with a custom function, a workflow HTTP step, or your own server reading webhooks.
Mock mode#
Every integration works without vendor credentials. With no credentials (or with TRIED_MOCK_PROVIDERS=1 on the server), a connection runs in mock mode:
- App actions return deterministic sample data. Mock Cal.com bookings are remembered, so list, reschedule and cancel behave consistently.
- CRM sync records each operation instead of sending it, and returns stable ids like
mock_hubspot_3f9a1c2b7d4e. - Synced sources import two sample documents ("FAQ" and "Price list").
- OAuth connect uses a built-in mock consent page.
The dashboard labels these connections Mock. Add real credentials or connect with OAuth to switch a connection to live. Needs keys
Credentials and OAuth#
You can connect a provider two ways:
- Paste credentials: an API key or access token. Each provider page lists the exact keys.
- Connect with OAuth: the dashboard sends you to the provider's consent page and stores the tokens. Tokens are refreshed automatically. This needs the deployment's OAuth client for that provider. See OAuth connections.
Credentials are encrypted at rest. The API and dashboard only show them masked (for example ******a9f2). URLs, subdomains, location ids and similar non-secret values are shown in full.
All vendor requests go through the same egress filter as webhooks, so instance URLs you enter cannot point at private networks.
Contact data#
The third tab, Contact memory & fields, controls what Tried writes onto its own contacts after each call. Those contact fields are what CRM sync pushes. See Contact field mappings.
Pages in this section#
integration_app tools to agents.CRM syncAfter-call push, full sync jobs and field mapping.Contact field mappingsFill contact fields from post-call data.Synced sourcesGoogle Drive, OneDrive and Notion knowledge bases.