Overview

The Approval step routes content for human review and sign-off. Use Approval when you need explicit human confirmation before proceeding with a workflow.

Use When

• You need human sign-off on AI-generated outputs

• Contracts or documents require executive review

• High-value decisions need human oversight

• You want to implement approval workflows

Configuration Options

Content to Approve

Specify what content requires approval:

• Generated documents

• Agent analysis and recommendations

• Form inputs

• Any output from previous steps

Approvers

Define who can approve by selecting from these assignment methods:

User Assign — Route approvals to specific individual users. Select from a searchable list of team members to assign approval responsibilities directly to named individuals.

Role-Based Assignment — Route approvals based on predefined roles within your organization:

• Owner — Assigns approvals to the document or workflow owner

• Requester — Assigns approvals to the person who initiated the workflow

Assign Strategy — Use intelligent assignment algorithms to distribute approval workload:

• Round Robin — Cycles through available approvers in sequence, distributing approvals evenly across the team to ensure balanced workload distribution

From Flow — Dynamically reference approver information from earlier steps in the workflow. This allows the approver to be determined based on form inputs, data processing, or previous workflow decisions.

Approval Groups

Create multiple approval groups for sequential or conditional review processes:

• Use "Add Group" button to create additional approver groups (Approvers 1, Approvers 2, etc.)

• Each group can have different approvers assigned using any of the methods above

• Groups can be configured to require approvals in a specific order using the "Approve by order" toggle

• Add conditional logic to different groups using the "Add condition" option to route approvals based on workflow variables

Delivery Method

Choose how approvers receive requests:

• Slack — Send approval notifications with embedded approval buttons for quick action directly within Slack

• Teams — Deliver approval requests to Microsoft Teams with approval buttons for seamless integration

• Email — Send approval requests via email with links for reviewing and actioning approvals

Additional Configuration

Approve by Order — When enabled, requires approvals to be completed sequentially in the order of your approval groups. Disable to allow parallel approvals from multiple groups simultaneously.

Subject — Customize the subject line of approval notifications. Use @ mentions to pull dynamic content from workflow context.

Message Content — Define the message text that accompanies approval requests. Include instructions, context, or additional details for approvers. Use @ mentions to reference workflow variables.

Conditional Approval — Apply conditional logic to define different approval groups based on flow variables. This allows routing to different approvers or approval paths based on document type, value, or other workflow data.

Example

NDA Approval Workflow

Configuration:

• Content: NDA document generated in previous step

• Approver: VP of Legal (specific user)

• Delivery: Slack notification with "Approve" button

When sent via Slack, the VP receives a notification with the document and approval options.

Notes

• Approval steps create tasks that appear in users' task lists

• Approvers can add comments when approving or rejecting

• Rejection can trigger rework or alternative workflows

• Multiple approvers can be configured for sequential or parallel approval

• Approval is a human checkpoint—it always requires explicit action