Skip to main content

​
Overview

The Review step creates a human-in-the-loop approval gate in your workflow. When it executes, a message is created in the target project and appears in the organization’s Messages inbox. Team members can view the review data, discuss it via replies, and approve it to resume the workflow. This is useful when you need manual sign-off before continuing — for example, verifying extracted contract data, approving a batch of notifications before they’re sent, or reviewing transformed data before it’s written to a database.

​
How It Works

1

Review Step Executes

The automation reaches the Review step and creates a message in the target project.
2

Message Appears in Inbox

The message shows up in the organization Messages page and the project’s Inbox, with the configured title, description, and review data.
3

Team Reviews

A team member opens the message, reviews the key-value data, and can add replies or assign it to someone.
4

Approval (Wait Mode)

If the review mode is Wait, the workflow is paused. The team member clicks Approve on the review data to resume the workflow. In Continue mode, the workflow proceeds immediately — the message is created for visibility only.

​
Configuration

FieldDescription
Target ProjectThe project where the review message is created
Review ModeWait or Continue (see below)
TitleMessage title (supports template variables)
DescriptionMessage description (supports template variables)
Review DataKey-value pairs of data to display to the reviewer (supports template variables)

​
Review Modes

ModeWorkflow BehaviorApproval Required
WaitPauses at this step until a team member approvesYes — click Approve on the message to resume
ContinueProceeds immediately, message created for visibilityNo

​
Review Data

The review data field lets you attach key-value pairs to the message. Use template variables to pull in data from previous steps — for example, showing the contract title and extracted royalty rate for a reviewer to verify. The data is displayed as a structured card on the message detail page. When used inside a Loop step, each iteration creates its own review data entry with an iteration index badge and its own Approve button.
In a loop, each iteration is independent — approving one entry immediately resumes that iteration’s workflow without waiting for the rest of the batch. You can approve items one by one as you review them.

​
Output

FieldTypeDescription
dataobjectThe resolved review data
message_idstringID of the created message

Messages

Where review messages appear in the organization.

Project Inbox

Project-level inbox where review messages also appear.