Workflow node reference
End Flow
End the workflow execution. Exact configuration, outputs, execution behavior, errors, limits, and examples for the End Flow workflow node.
What this guide covers
- Category: Actions.
- Use it to explicitly end an execution as success, failure, or cancelled, optionally with a final message and log reason.
- 9 configuration fields and 3 documented outputs.
- No later node runs after End Flow.
What this node does
End the workflow execution
Use it to explicitly end an execution as success, failure, or cancelled, optionally with a final message and log reason.
When not to use it
Do not use it where a human must take control; use Human Handoff.
Prerequisites
- Chosen end type
- Sender/recipient when a final message follows Scheduled or Webhook trigger
- Eligible conversation for free-form final text
Chosen end type. Sender/recipient when a final message follows Scheduled or Webhook trigger. Eligible conversation for free-form final text
Inputs and configuration fields
| Field | Key | Control / type | Requirement | Default | Accepted values and behavior |
|---|---|---|---|---|---|
End Type | end_type | select | Optional | success | Success (success), Failure (failure), Cancelled (cancelled) |
Send Final Message | send_final_message | toggle | Optional | false | Value accepted by the displayed control |
Final Message | final_message | variable-input | Optional | No default | shown when send_final_message equals true. Variables supported |
Log Reason | log_reason | variable-input | Optional | No default | Workflow completed: {{nodes.classifier.category_name}} handled successfully. Variables supported |
Final Message Sender & Recipient | _divider_final_message_override | divider | Optional | No default | Required when sending a final message from scheduled or webhook workflows. shown when send_final_message equals true |
Send From Number | send_from | single-number-picker | Optional | No default | Select which WhatsApp number to send from. shown when send_final_message equals true; Required for scheduled/webhook triggers. Optional for message triggers. |
Always use this sender | override_sender | toggle | Optional | false | If enabled, always send from this number even for message triggers. shown when send_final_message equals true |
Send To Number | send_to | variable-input | Optional | No default | Recipient phone number (can use variables). shown when send_final_message equals true; Required for scheduled/webhook triggers. Optional for message triggers.. Variables supported |
Always use this recipient | override_recipient | toggle | Optional | false | If enabled, always send to this number even for message triggers. shown when send_final_message equals true |
Configure the node
- Drag End Flow from Actions 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.end_flow.reason}} | string | Why the workflow ended |
{{nodes.end_flow.ended_at}} | string | Timestamp of completion |
{{nodes.end_flow.message}} | string | Completion message |
Execution behavior
- Optionally sends the resolved final message.
- Records end type and log reason.
- Emits reason, ended timestamp, and completion message and stops the path.
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
End a validation failure path as Failure with a safe internal log reason and no customer message.
Webhook → Condition → App Action → End Flow (Success) / End Flow (Failure)Common errors
| Symptom | Resolution |
|---|---|
Final message lacks sender/recipient | Configure both for Scheduled or Webhook workflows. |
Final message is rejected | Check service-window and template rules; End Flow sends free-form text. |
Limitations
No later node runs after End Flow.
A Failure end type is an explicit business outcome, not an automatic retry request.
No later node runs after End Flow. A Failure end type is an explicit business outcome, not an automatic retry request.