Skip to main content
Connect your CRM, calendar, helpdesk, or knowledge source to Retell so agents can use its data and tools. Add a provider once on the dashboard’s Integrations page, and every agent in your workspace can use the connection. The supported-provider table lists each integration’s tools, sync features, and authentication method.
The Retell Dashboard's Integrations page on the Available tab, showing nine provider cards in two columns: HubSpot, Salesforce, Microsoft Dynamics 365, GoHighLevel, and Zoho CRM tagged CRM; Zendesk tagged Support; Google Drive tagged Knowledge base; and Calendly and Cal.com tagged Calendar. Each card carries a short description, a green Connected tag, and an Add Account button, and a Request integration button sits at the top right.

Examples of provider cards on the Integrations page's Available tab.

What does an integration give you?

  • Integration tools. Every provider except Google Drive, Microsoft OneDrive, and Notion adds tools your agent can call before, during, or after a call or chat: search a contact by the caller’s number, check calendar availability, book an appointment, create a support ticket. See use integration tools in an agent and agent workflow.
  • Contact sync and activity logging (CRM providers). Import CRM contacts into Retell, write Post Call Extraction results back to contact fields, and log each conversation to the CRM. CRM integrations covers this in full.
  • Knowledge base sources (Google Drive, Microsoft OneDrive, Notion). Sync files or pages from a connected account into a knowledge base so your agent answers from their content, and re-syncs them as they change.

Supported providers

Connect a provider

1

Open the Integrations page

In the Retell Dashboard, open Integrations and select the Available tab. Connecting requires an Admin or Developer role; custom roles need the App.Write and CRM.Write permissions.
2

Connect and authenticate

Pick your provider and enter what it asks for: an API key, or an OAuth sign-in on the provider’s own page. Some providers also ask for your tenant URL (Salesforce instance URL, Dynamics environment URL, Zendesk URL) or account ID (GoHighLevel Location ID). Retell encrypts stored credentials and never returns them through the API.
3

Verify the connection

Retell tests the credentials as part of connecting. The connection then appears on the Connected tab; from there you can rename it, rotate credentials, or set up CRM contact sync. A healthy connection shows no tag; a broken one carries a red Connection error tag, and the connection driving contact sync carries a blue Contacts sync on tag.
The Retell Dashboard's Integrations page with the Connected tab selected and ringed in blue. A table lists eight connections with provider icons for HubSpot, Google Drive, Microsoft Dynamics 365, GoHighLevel, Zendesk, Cal.com, Calendly, and Salesforce, with connection names redacted and Last Edited dates visible. One connection carries the blue Contacts sync on tag, and an Add integration button sits below the table.

The Connected tab, listing each connection with its provider and when it was last edited.

For the provider-side setup (creating the app, granting scopes, finding the token), follow the provider’s guide, linked in the table above.

Use integration tools in an agent

Once a provider is connected, its tools show up when you add a function to an agent, whether in a prompt agent’s Functions section or a conversation flow’s function node; see integration tools for prompt agents and integration tools in conversation flow for each surface. Each configured tool is bound to one specific connection, so if you connect two HubSpot accounts, you choose which one the tool uses.
A single prompt agent's editor with the Functions section and its + Add button ringed in blue. The add menu is open on a connection named HubSpot - API key, listing HubSpot tools such as List Contact Deals, Get Deal, Create Contact, and Log Call Activity. Update Contact is hovered, showing its description. The agent's prompt is redacted.

Adding a HubSpot tool to a single prompt agent's Functions section.

Add-function dialog with the Microsoft Dynamics 365 integration menu open. Create Task is hovered and its description is visible; the Add button is outlined in blue.

The same menu in a conversation flow's function node, here on a Microsoft Dynamics 365 connection.

Configure a tool’s inputs and outputs

Every tool config carries a Name, a Description that tells the LLM when to call it, and a Function fields card with an Input tab and an Output tab. On the Input tab, open the mode selector beside a field to choose where its value comes from. When the field displays AI will infer, you can click anywhere in that value area to open the menu. If a field has no built-in guidance, the menu offers Description instead of Custom, and Let AI infer isn’t available. Use Description to write the instructions yourself. Fields that require a fixed value offer neither AI mode nor variable references.
Salesforce Search Contact configuration on the Workflow page. The phone_number field displays AI will infer. Its open mode menu is outlined in blue, with Let AI infer selected above Custom and Value.

The input mode menu separates Let AI infer, Custom, and Value.

For example, a Search Contact tool can use Value with {{user_number}} to look up the calling number. If callers may use a different number for their account, choose Custom and enter: “Use the phone number the caller confirms for their account, including the country code.” Edit a custom prompt directly in the field, then click Save in the tool dialog to keep the configuration. To discard your custom instructions and use the provider’s guidance again, select Let AI infer. The Use AI prompt undo button restores the guidance inside the custom editor while keeping Custom selected. Saving an empty custom prompt also falls back to built-in guidance when available.

Configure typed inputs

The provider defines each field’s type. Changing its input mode changes how you supply a value, not the type the provider receives. Required fields have an asterisk; Add input lets you include optional fields. Where Value supports dynamic variables, you can use a reference such as {{customer_email}} instead of a literal. Fields that require a fixed literal, such as Google Calendar’s calendar_id, don’t accept variables. Before saving, resolve invalid values and missing required fields; hover over a disabled Save button to see the reason.

Configure array inputs

Choose an array mode based on whether you already know the entries or want the agent to collect them. For example, Google Calendar’s Book Event takes an attendees array, with an email and optional name for each person.

Supply a fixed list with Array items

Choose Array items, then use the + beside the array name to add entries. Object entries are numbered [0], [1], and so on. Fill each entry’s required fields and use its trash button to remove the entry. Fields inside these rows take values, rather than AI instructions; where supported, you can use dynamic variables.
Google Calendar Book Event input configuration with attendees in Array items mode. The blue outline surrounds entry zero, whose email is jordan@example.com and name is Jordan Lee. The plus button beside attendees adds another entry.

Array items supplies a concrete attendee list, shown here with synthetic contact details.

For example, set the first attendee’s email to {{customer_email}} when an earlier function already collected it. Use a number or Boolean control for those item types, and configure nested objects or arrays within their parent entry when the provider supplies that structure. Blank rows are omitted from the request. A previously saved whole-array variable or explicit empty array ([]) can reopen in Value mode so its value is preserved, even when a new array normally offers Array items instead.

Let the agent build the list

Choose Let AI infer to use the provider’s guidance for the entire array. For an array of objects, choose Custom to write an instruction for the list and configure the fields under Every item. If the provider has no built-in guidance, this mode is called Description. The array instruction tells the agent which entries to include. Every item defines how each entry is filled: use Description for a field the agent should collect, or Const for a value shared by every entry. Enum and Boolean fields retain their Select and Boolean controls. A constant here applies to every generated entry; it doesn’t add a separate fixed entry to the list.
Google Calendar Book Event input configuration with attendees in Custom mode. The array prompt says to invite people the caller confirms should attend. The blue outline surrounds Every item, with separate email and name instructions for each attendee.

Every item applies the same field instructions to each attendee the agent collects.

For an attendee list, use the array instruction “Invite the people the caller confirms should attend.” Under Every item, set email to Description with “Use the email address confirmed for this attendee,” and name to “Use this attendee’s full name.” Switch back to Let AI infer to use whole-array inference without the Every item rules. These AI modes appear only where the function supports inferred inputs; pre-call and pre-chat integration inputs use values instead.

Run a test to get a tool’s output fields

The Output tab decides what the response gives back: which fields the agent sees, and which become dynamic variables. Most providers ship a response schema, so the field picker is already populated. Run a test when a tool has no schema, or when you want the real field names and values in front of you.
A test request is sent to the connected provider for real. A lookup reads live data, and testing a create or update tool writes a real record. Use values you don’t mind touching.
1

Run a test

On the Output tab, click Run a test, fill in the tool’s inputs, and run it. Retell calls the provider and shows the actual response: a checkable field tree on the Fields tab, the raw payload on the JSON tab.Enter concrete values here rather than {{variable}} references. A test resolves variables in the tool’s pinned inputs, but not in the values you type into the test panel.Inputs set to Let AI infer, Custom, or Description start blank in the test panel. Enter sample values yourself; this test checks the provider request with those values. Use an agent test to check how the agent fills them from a conversation.For arrays, use the + beside the array name to enter concrete sample rows. In Every item mode, configured constants prefill the corresponding fields, while fields with AI instructions need sample values. Fill required fields in each added row, including nested entries. The test doesn’t run your field instructions to generate an array.
The Test : Search Salesforce Contact dialog. The left pane, Test input, warns to provide real values because the test may modify real user data, and holds a required phone_number field whose value is pixelated, above a Run a test button. The right pane, Test output, has Fields and JSON tabs with JSON selected, showing the live Salesforce response: an attributes object with type Contact and a record url, then Id, IsDeleted false, MasterRecordId, AccountId, and a long list of fields, with the LastName, FirstName, and Name values pixelated and the remaining address fields null. Cancel and Add selected outputs buttons sit at the bottom.

The test panel for a Search Salesforce Contact function, on the JSON tab after a run.

2

Pick the fields the agent should see

In the test panel, tick the fields worth keeping and click Add selected outputs. They land in the Output tab’s list under Fields for agent context, the only part of the response the agent and the transcript see, which keeps a large provider payload from crowding the prompt. Leave the list empty to send the whole response.Select fields on the Output tab opens the same picker against the tool’s response schema, so you can choose fields without running anything; it confirms with its own Select fields button.
The Select fields for agent context dialog, headed with the line Select the fields your agent needs. A checked Select all box is labelled Including fields not listed here, followed by a checkbox tree of the Salesforce Contact response: an expanded attributes folder holding type and url, then Id, IsDeleted, MasterRecordId, AccountId, LastName, FirstName, Salutation, Name, and a run of Other address fields, every box checked. Cancel and Select fields buttons close the dialog.

The Select fields dialog, with the whole Salesforce Contact response checked.

Manually add fields takes a dot-path the schema doesn’t describe. A path names a branch and keeps everything under it; a plain segment reaches into every element of an array (deals.properties.amount keeps that field on all of them), while deals[0].id keeps only the first.
3

Name the ones you need as variables

In the Dynamic variable column, name any field you want to reuse: in the prompt, in a later tool’s input, or in a function on the agent’s workflow. Variables are extracted from the raw response, so narrowing what the agent sees never breaks one you mapped.
For example, a dental clinic connects Cal.com and HubSpot. Its inbound agent searches HubSpot for the caller’s number to greet them by name, checks Cal.com availability for the requested week, books the cleaning appointment, then logs the call on the HubSpot timeline, without a human touching either system.

Track execution status

In a tool’s Function fields → Output tab, the fixed Success status row stores whether the tool call succeeded. Enter a Dynamic variable name such as contact_lookup_status, then save. Use a name without {{ }} that differs from your response-variable names. Leave it blank if you don’t need to store status; no test run or field selection is required to configure it.
HubSpot Search Contact dialog on the Output tab. The Success status row is outlined in blue and mapped to contact_lookup_status. The id response field is separately mapped to contact_id.

Save the integration's execution status separately from the returned contact ID.

Retell writes success or failure after execution, including failures that produce no response fields. A successful lookup can still return no matching contact; check the returned data separately. If a condition or dependency skips the tool, the status variable keeps its previous value. In a conversation flow, select Wait for completion and branch on the status. The API setting is execution_status_variable, separate from response_variables and the fields selected for agent context.

Run tools before or after the call or chat

Tools can also run outside the conversation. On the agent’s Workflow page, add them as pre-call functions, which run before the call starts so the agent has context before it speaks, or as post-call functions, which run after the call ends to update your systems. Chat agents have the same two slots, named pre-chat and post-chat functions. Each slot is a dependency graph rather than a list: functions with no dependency all start at once, and a function you add as sequential waits for the one above it and can use its output through a dynamic variable. Post-conversation functions can also be gated on a condition, so a follow-up task is created only when the session earned one. Agent workflow covers the whole surface: chaining, conditions, timing budgets, failure behavior, and worked examples for both voice and chat.

FAQ

Yes. Each connection is separate, and each tool is bound to a specific connection. The one exception is CRM contact sync: only one CRM connection can drive contact sync for your workspace at a time.
No. Integration tools work as soon as the connection is made. Contact sync and automatic activity logging are separate CRM features you opt into per connection; analysis data mappings are configured once per workspace.
Each tool call times out after 3 to 14 seconds, depending on the provider and tool (as of August 2026). If the provider doesn’t respond in time or returns an error, the tool call fails and the agent continues the conversation; prompt your agent on what to say when a lookup or booking doesn’t go through.
Retell marks a connection as errored when the provider rejects its credentials, flagging it with the red Connection error tag on the Connected tab. On most providers a missing scope or permission doesn’t flag the connection, because the provider answers with a permission error rather than rejecting the credentials; the affected feature quietly stops working, so check provider-side permissions first when one tool misbehaves.Two things do flag it. The connection test, run when you connect or reconnect, flags the connection whenever it fails, including on a scope the test itself needs. And on GoHighLevel a missing scope comes back as an authorization error Retell can’t tell apart from a dead token, so a tool call can flag the connection.