Request Approval
Pause until someone approves or rejects. Rejected uses a separate outlet.
Type
chat.request-approvalFolder
chatChannels
Any
Pipe
Value
Scope
Any
Human-in-the-loop
Yes
Request Approval pauses until a person approves or rejects (including revoke). Assignees see the request on Approvals. Full product rules are on Approval Flow.
On a chat workflow you can choose current user or roles. On other channels, only role approval is available.
Configure
| Setting | Description |
|---|---|
| Message | What the approver reads (required) |
| Approval mode | On chat only: Require role approval or Require current user approval |
| Roles | Who can decide. Required in role mode — pick at least one role |
Handles
| Handle | Role |
|---|---|
| In (target) | Incoming connection |
| Out (source) | Continues when the request is approved |
| Rejected | Continues when the request is rejected or revoked |
Connect both outlets if you need different follow-up for yes vs no.
Pipe schema
The next block reads this on the data pipe (pipe.value).
| Field | Type | Description |
|---|---|---|
decision | text | Outcome of the request |
decidedBy | text | Who decided (may be empty) |
note | text | Optional note from the approver (may be empty) |
approvalId | text | Request id (may be empty) |
Use case
- Gate a refund or send-email step until a manager approves.
- On chat, ask the person in the session to confirm before a destructive action.