AI Agent Action: Trigger Workflow

The Trigger Workflow action starts an existing Workflow from the conversation based on your AI Agent’s instructions. Use this when the AI Agent needs to kick off more complex automations you already manage in Workflows, such as sending HTTP requests, adding a Google Sheets row, or sending a CAPI event. The Workflow then runs as configured, independently of the AI Agent.

When to use

• When you already rely on Workflows to execute core business processes and want AI Agents to plug into them instead of rebuilding logic with other actions.

• When the next step goes beyond what AI Agent actions can do on their own—for example, pushing data to external tools or orchestrating multi-step automations.

• When you want to keep business logic centralized in Workflows but let the AI Agent decide when that logic should run.

Best practices

• Turn on Trigger Workflows in your AI Agent’s Actions and describe your conditions in the When and how should this action be performed? field.

• Use ! to reference the exact Workflow name in your instructions. For example:

If the Contact asks for a refund, trigger !refund_processing.

• Make sure the Workflow you reference is published, unpublished Workflows will not run when triggered.

• Avoid building the same automation twice. If a Workflow performs the same actions as your AI Agent (for example, sending a follow-up message or updating the same Contact field), you may see duplicate messages or Contact updates.

You can define multiple conditions in the same instruction field; each condition can trigger the first step of a different Workflow.

Limitations

• Trigger Workflows only works with existing Workflows in your Workspace. If there are no Workflows, this action cannot be enabled and you’ll be prompted to create a Workflow first.

• Variables are not passed from the AI Agent to the Workflow. The Workflow cannot automatically see conversation variables like collected answers unless you configure that logic inside the Workflow itself.

• Information is not passed back from the Workflow to the AI Agent. The AI Agent does not “wait” for the Workflow’s result and cannot react to its individual steps.

• When testing an AI Agent, you’ll see a Workflow {workflow name} Started event in the Test AI Agent panel when a Workflow is triggered. Unpublished Workflows will not produce events in the test panel.