🇬🇧 EN

✅ Approval

Pauses the workflow and waits for a human to approve or reject the action before continuing. An in-app notification and (optionally) an email is sent to the assigned approver. If approved, the workflow continues to the next step. If rejected, the workflow stops with a status reflecting the rejection.

Category: Human / User Interaction · Type identifier: approval

Overview

The Approval node introduces a human decision point into an otherwise automated workflow. When execution reaches this node, the workflow enters Waiting status and a task card appears on the Tasks page for the assigned approver. The approver reads the title and description, then clicks Approve to allow the workflow to continue or Reject to stop it.

This is essential for workflows that carry real-world consequences — sending bulk emails, making financial transactions, publishing content, or triggering irreversible actions — where a human sign-off is required before proceeding.

Rejected runs end immediately. If you need to take action on a rejection (e.g. notify the content team), add a In-App Notification or Email Notification node before the Approval node, or build a separate error-handling workflow.

Configuration

Field	Status	Description
Assignee	Required	Email address or user ID of the person who should approve. Supports `{{ variable }}` references.
Title	Required	Short description shown to the approver, e.g. `Approve invoice #{{ trigger.output.invoice_id }}`.
Description	Optional	Longer explanation to help the approver make their decision. Supports `{{ variable }}` references.
Timeout	Optional	Maximum time to wait for a response, in minutes. If the timeout expires without a decision, the workflow fails. Leave blank to wait indefinitely.
Send Email	Optional	Toggle. When on, sends an email to the assignee in addition to the in-app notification. Requires SMTP to be configured in Settings.

Output Data

These fields are available to subsequent steps if the workflow was approved. A rejected workflow terminates without producing output.

Field	Type	Description
`approved`	boolean	True if the approver clicked Approve, false if they clicked Reject.
`decision`	string	`approved` or `rejected`.
`decided_by`	string	Email or user ID of the person who made the decision.
`decided_at`	string	ISO 8601 timestamp of the decision.
`notes`	string	Optional comment entered by the approver when making their decision.

Example Usage

An Agent node drafts a marketing email and stores it in its output.
An Approval node is configured with the marketing manager's email as the Assignee. The Title reads Review and approve the campaign draft, and the Description includes {{ agent.output.text }} so the manager sees the full draft inline.
If the manager clicks Approve, the workflow continues to an Email Notification node that sends the campaign to the mailing list.
If the manager clicks Reject, the workflow stops. An earlier In-App Notification node (placed before the Approval node) has already alerted the content team to stand by for feedback.

Tips & Notes

Use {{ variable }} references in the Title and Description to surface relevant data from earlier steps so the approver has full context without looking elsewhere.
The workflow remains in Waiting status indefinitely until the approver acts, unless a Timeout is set.
Set a Timeout for time-sensitive decisions such as invoice approvals or publishing windows, so the run does not hang forever if the approver is unavailable.
Use the Assignee field with a variable to route approvals dynamically — for example, assign to a team lead based on the department in the trigger payload.
Multiple Approval nodes can appear in a single workflow for multi-stage sign-off processes.

Related Nodes

Manual Input — pause and collect form data from a human instead of a simple approve/reject decision.
In-App Notification — alert the reviewer that their approval is needed.
Email Notification — send an email notification alongside or instead of the built-in Send Email toggle.