Conversation Trigger

The conversation trigger marks the Flow as conversational and interactable from any chat channel.

Ce qu’il fait

The presence of a conversation trigger is what makes the Flow discoverable as a conversational agent on every supported chat channel once published.

Each conversation runs as a single Flow instance — suspending and resuming at each Wait for Message as the user sends more messages. When the Flow execution ends, the conversation gracefully completes as well; users see that the conversation has ended and cannot send more messages to the chat.

Sortie

Champ	Description
conversationId	Unique identifier for the conversation this run is serving.

Downstream conversational nodes may require a Conversation ID input. Reference the trigger's output, such as with:

$vars.conversationTrigger1.output.conversationId

Remarques

• Ensure a Wait for Message node immediately follows the conversation trigger.
• Once published, the conversation trigger only fires when it's set to the Flow's default trigger in Orchestrator. Either ensure this is the Flow's only trigger, or confirm that the conversation trigger is the default entry point in Orchestrator after publish.

Pages liées

• Wait for Message — the next node in a chat loop.
• Chat — full palette of chat conversational nodes.
• Build a chat agent workflow — end-to-end walkthrough starting with the Conversation Trigger.
• Chat deployment — publish and expose the Flow through various channels.