Browse documentation

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.

Automation buildersIntermediateAvailable

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

  1. A connected number for WhatsApp events
  2. A future time and supported timezone for Scheduled
  3. The generated URL for Webhook

Inputs and configuration fields

Workflow Trigger configuration fields
FieldKeyControl / typeRequirementDefaultAccepted values and behavior
Trigger Eventstriggerstrigger-builderRequired when shownNo defaultAdd one or more events that will start this workflow. Value accepted by the displayed control

Configure the node

  1. Drag Workflow Trigger from Triggers in the node palette.
  2. Select the node to open its configuration drawer.
  3. Complete every required field and any conditional field revealed by your choices.
  4. Insert variables only from the current trigger or an earlier node on the same path.
  5. Connect every required output handle to the intended next step.
  6. 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.

Workflow Trigger output variables
VariableTypeMeaning
{{nodes.trigger.matched_trigger_id}}stringID of the trigger configuration that matched
{{nodes.trigger.matched_trigger_type}}stringType of trigger that matched
{{nodes.trigger.match_reason}}stringWhy the trigger matched
{{nodes.trigger.message_type}}stringType of message (text, image, etc.)
{{nodes.trigger.message_content}}stringText content of the message
{{nodes.trigger.timestamp}}stringWhen the trigger fired

Execution behavior

  1. Exactly one Workflow Trigger is allowed and it cannot be deleted.
  2. The first matching configured event starts a new execution and exposes trigger context.
  3. It does not run as a normal downstream step.

Example use case

Start a support workflow whenever the selected Sender receives a text message.

Complete workflow pattern
text
Message Received → Classifier → Condition → AI Response → Send Text

Common errors

Workflow Trigger common errors
SymptomResolution
No execution startsConfirm Active status, selected number, event type, filters, and exact keyword match mode.
Scheduled start is shiftedCheck the trigger timezone and next future occurrence.
Webhook does not startUse 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.