Add HubSpot, Salesforce, Zendesk, or Cal.com tools to a Retell AI prompt agent: connect once, configure inputs and outputs, and test with live data.
Integration tools let a single- or multi-prompt agent act on a connected provider during the conversation, or before or after it. Examples: look up the caller in a CRM, book an appointment, create a support ticket.Retell handles the provider’s API and authentication for you. Unlike a custom function, there’s no endpoint to host and no request to verify.See the integrations overview for the list of supported providers, what each provider’s tools do, and how to connect them.
When to use an integration tool
Retell offers three ways to give an agent a tool. Pick based on where the action needs to run:
Integration tool — the action runs against a supported provider (CRM record, helpdesk ticket, calendar booking). No code, no server to run.
Custom function — the action runs on your own systems, or on a provider Retell doesn’t support. You host the endpoint.
Code tool — self-contained logic or a simple API call that runs inside Retell’s sandbox.
Add a tool
1
Connect the provider
Connect it once on the dashboard’s Integrations page — a workspace-level step covered in the integrations overview. Every agent can then use the connection.
2
Add the tool to the agent
In your agent’s Functions section, click + Add. Connected providers and their tools appear in the menu, and Add integration lets you connect a new provider without leaving the agent.
Adding a HubSpot tool from the agent's Functions section.
3
Configure it
Pick the tool and set up its pieces:
Connection: which account the tool acts on, if you’ve connected several.
Inputs: choose Let AI infer to use the provider’s field guidance, Custom to write your own instructions, or Value for a fixed value or {{variable}}. Fields without built-in guidance use Description for your instructions. See input modes for availability and examples.
Response variables: map fields from the tool’s result to dynamic variables, so the prompt and later tools can use them (for example, save the contact ID from Search Contact and pass it to Create Task).
Presentation: like other tools, you can have the agent speak while the tool executes, and override the description that tells the LLM when to call it.
For a Search Contact tool, use Value with {{user_number}} to look up the calling number. Choose Custom if the agent should instead use an account phone number confirmed during the conversation.For structured inputs, see typed fields and arrays. For example, Google Calendar’s Book Event accepts an attendee list: supply fixed Array items, or let the agent collect entries using Every item instructions.
4
Test it before the first call
Test requests are 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.
In the tool’s config, enter real input values and click Run a test. Retell calls the provider and shows the actual response. Tick the response fields worth keeping and click Add selected outputs to save them as dynamic variables, instead of typing field paths by hand.
The test panel for a Search Contact tool, with three response fields selected as outputs.
To store whether the tool call succeeded, enter a dynamic-variable name in Function fields → Output → Success status. Retell sets it to success or failure separately from response fields. See configure execution status.
Chain tools through response variables: a support agent calls Zendesk’s Search User with {{user_number}}, saves the returned user ID to a dynamic variable, then passes it to List User Requested Tickets when the caller asks for a status update.
Notes
Each tool call times out after 3 to 14 seconds, depending on the provider and tool (as of August 2026). On timeout or error, the agent continues the conversation — prompt it on what to say when a lookup or booking doesn’t go through.