Workflow node reference
Workflow Trigger
Define what starts this workflow. Exact configuration, outputs, execution behavior, errors, limits, and examples for the Workflow Trigger workflow node.
What this guide covers
- Category: Triggers.
- Use it to define the Message Received, Keyword Match, New Conversation, Scheduled, or Webhook events that may start this workflow.
- 1 configuration fields and 6 documented outputs.
- Only one trigger node is allowed per workflow.
What this node does
Define what starts this workflow
Use it to define the Message Received, Keyword Match, New Conversation, Scheduled, or Webhook events that may start this workflow.
When not to use it
Do not use it as a mid-workflow wait or outbound webhook. Use Delay to wait and Send Webhook to call another system.
Prerequisites
- A connected number for WhatsApp events
- A future time and supported timezone for Scheduled
- The generated URL for Webhook
A connected number for WhatsApp events. A future time and supported timezone for Scheduled. The generated URL for Webhook
Inputs and configuration fields
| Field | Key | Control / type | Requirement | Default | Accepted values and behavior |
|---|---|---|---|---|---|
Trigger Events | triggers | trigger-builder | Required when shown | No default | Add one or more events that will start this workflow. Value accepted by the displayed control |
Configure the node
- Drag Workflow Trigger from Triggers in the node palette.
- Select the node to open its configuration drawer.
- Complete every required field and any conditional field revealed by your choices.
- Insert variables only from the current trigger or an earlier node on the same path.
- Connect every required output handle to the intended next step.
- Save and run Workflow Test with representative data before activation.
Outputs
Later nodes can use these values only after this node has run successfully on the same execution path.
| Variable | Type | Meaning |
|---|---|---|
{{nodes.trigger.matched_trigger_id}} | string | ID of the trigger configuration that matched |
{{nodes.trigger.matched_trigger_type}} | string | Type of trigger that matched |
{{nodes.trigger.match_reason}} | string | Why the trigger matched |
{{nodes.trigger.message_type}} | string | Type of message (text, image, etc.) |
{{nodes.trigger.message_content}} | string | Text content of the message |
{{nodes.trigger.timestamp}} | string | When the trigger fired |
Execution behavior
- Exactly one Workflow Trigger is allowed and it cannot be deleted.
- The first matching configured event starts a new execution and exposes trigger context.
- It does not run as a normal downstream step.
Do not assume a failed node is automatically retried. Review the execution result and the relevant service documentation before repeating an operation that could create a duplicate side effect.
Example use case
Start a support workflow whenever the selected Sender receives a text message.
Message Received → Classifier → Condition → AI Response → Send TextCommon errors
| Symptom | Resolution |
|---|---|
No execution starts | Confirm Active status, selected number, event type, filters, and exact keyword match mode. |
Scheduled start is shifted | Check the trigger timezone and next future occurrence. |
Webhook does not start | Use the exact generated URL and inspect the request response. |
Limitations
Only one trigger node is allowed per workflow.
Scheduled UI supports once, daily, weekly, and monthly; it is not an arbitrary cron editor.
Only one trigger node is allowed per workflow. Scheduled UI supports once, daily, weekly, and monthly; it is not an arbitrary cron editor.