> ## Documentation Index
> Fetch the complete documentation index at: https://docs.retellai.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Integration tools in conversation flow

> Call HubSpot, Salesforce, Zendesk, or Cal.com tools from a Retell AI conversation flow function node, and branch transitions on what comes back.

In a conversation flow, integration tools run through a [function node](/build/conversation-flow/function-node): the node fires the tool on entry, and the flow transitions on the result. Retell handles the provider's API and auth, so there's no server of your own in between. For single- and multi-prompt agents, add the same tools from the Functions section instead; see [integration tools for prompt agents](/build/single-multi-prompt/integration-tools).

See the [integrations overview](/integrations/overview) for the providers Retell connects to, what each one's tools do, and how to connect them. [Subagent nodes](/build/conversation-flow/subagent-node) can use integration tools too, alongside their other tool types. Integration tools can also run outside the conversation, before it starts or after it ends; see [agent workflow](/agent/agent-workflow).

## Add an integration tool to a flow

<Steps>
  <Step title="Connect the provider">
    Connect it once on the dashboard's **Integrations** page — a workspace-level step covered in the [integrations overview](/integrations/overview#connect-a-provider).
  </Step>

  <Step title="Add the tool from the function menu">
    In the flow, add a function; connected providers' tools appear in the menu grouped by provider. You can also pick **Add integration** in the menu to connect a new provider without leaving the flow.

    <Frame caption="Adding a Microsoft Dynamics 365 tool to a conversation flow's function node.">
      <img src="https://mintcdn.com/retellai/Mg1hiS-BnevMo90k/images/integration/function-node-add-integration-tool.png?fit=max&auto=format&n=Mg1hiS-BnevMo90k&q=85&s=9e5dada931fa981d4f7050e04214d776" alt="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." style={{ maxHeight: 560 }} width="1010" height="440" data-path="images/integration/function-node-add-integration-tool.png" />
    </Frame>
  </Step>

  <Step title="Select it inside a function node">
    Pick the tool in the node, as with any function. Configuration works the same as for [prompt agents](/build/single-multi-prompt/integration-tools): inputs are fixed values or filled from the conversation, response fields map to [dynamic variables](/build/dynamic-variables), and you can test the tool with a live request before the first call.
  </Step>
</Steps>

## Branch on the result

The function node considers the tool's result for transition timing (see [when transitions happen](/build/conversation-flow/function-node#when-can-transition-happen)), so your [transition conditions](/build/conversation-flow/transition-condition) can branch on what came back: one edge for "contact found", another for "no match", each leading to a different conversation node.

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 flow still transitions, so give errors their own edge rather than letting them fall through a success path.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.