Native tools (IV): transfer to another AI agent and trigger workflows

Connect your AI agents to each other and to your automations: hand off to an AI specialist or fire a workflow straight from the conversation.

Jun 26, 2026

Watch this step in the video · Transfer to another AI agent and dismiss

The most advanced tools turn your AI agent into an orchestrator: it can hand the conversation to another specialist AI agent or fire a full automation. They're ideal for operations spanning several areas.

What each tool does

  • Transfer to another AI agent: hands the conversation to another specialist AI agent (for example, from Sales to Support) when the topic is outside the current agent's area. The destination agent takes over and answers the next turn. The conversation stays with the AI.
  • Trigger workflows: fires a workflow you've already built (send a template, add to a campaign, create a task, etc.). It's identified by its slug (lowercase name) and is logged in the audit trail as an AI execution.

Key difference from "Assign to a human"

Transfer to another AI agent keeps the conversation on the bots. If you need to hand off to a person or team, use Assign to a human or team, which turns the AI off in that chat. Don't mix them up.

Before you start

  • For transfers, have the second agent (e.g. Support) created in the same workspace.
  • For workflows, have the flow built and active under Workflows, and note its slug.

Steps to enable them

  1. Open your agent from AI Agents (side menu).
  2. Go to the Custom actions tab.
  3. Turn on Transfer to another AI agent and/or Trigger workflows.
  4. In the instructions, tell it when to route and to whom: "If they ask about billing, transfer to the Support agent. If they confirm a purchase, trigger the welcome-vip workflow."
  5. For workflows, reference the exact slug so the AI doesn't guess.
  6. Save your changes.

Anti-bounce protection

So a customer doesn't ping-pong between bots, there's a hop limit between AI agents per conversation. If it's reached, the transfer is refused and the agent should hand off to a human instead.

How to verify it works

  1. Open the Sandbox tester.
  2. Raise a case that belongs to the other agent's area and confirm the conversation transfers and the second agent answers.
  3. Trigger an intent that maps to a workflow and check under Workflows that the run is logged as AI.

If it doesn't work

  • It doesn't transfer: the destination agent must exist in the same workspace and be identified by its exact name.
  • The workflow doesn't run: check the slug is correct and the flow is active. The AI shouldn't guess slugs.
  • It bounces and stops: the hop limit was reached; review your instructions to avoid loops between agents.

Tips

Design an AI "receptionist" that routes to specialist agents by topic. Each specialist keeps its own tone and knowledge base.

Use Trigger workflows for multi-step tasks (template + tag + task) instead of cramming everything into the agent's instructions.

Related articles

Was this helpful?

Related articles

Message us on WhatsApp