UiPath Documentation
maestro
latest
false
Maestro Orchestrate user guide

Conversation trigger

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

What it does​

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

Each conversation is a single run of the workflow. It suspends and resumes at each Wait for Message as the user sends more messages. When the run ends, the conversation gracefully completes as well; users see that the conversation has ended and cannot send more messages to the chat.

Output​

FieldDescription
conversationIdUnique 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
$vars.conversationTrigger1.output.conversationId

Notes​

  • Ensure a Wait for Message node immediately follows the conversation trigger.
  • Once deployed, the conversation trigger only fires when it's the workflow's default trigger. Make it the workflow's only trigger, or check after you deploy that the conversation trigger is the default entry point.

Next steps​

  • What it does​
  • Output​
  • Notes​
  • Next steps​

Was this page helpful?

Connect

Need help? Support

Want to learn? UiPath Academy

Have questions? UiPath Forum

Stay updated