Skip to main content

Send and Wait for Response

The Send and Wait for Response node asks people in the workspace something and pauses the run until they answer. Each person it asks gets an in-app notification, and the request is listed in the Approvals inbox. The answer becomes the node's output and picks the branch the run continues on.

Gmail and Slack offer the same thing as their own Send and Wait for Response operation, which asks by email or in a Slack channel and is answered from the link in that message.

Outputs​

The node has three outputs; only one of them runs:

OutputWhen
ApprovedThe approval was approved, or a free-text or form answer came back
DeclinedThe approval was declined
Timed outNobody answered before the wait limit (see Wait limit)

Settings​

FieldWhat it does
Ask (user IDs)The people to ask. Pick workspace members from the list; they are the only ones who can answer. Leave it empty, and set no roles, to let any workspace member answer from the Approvals inbox.
Ask RolesApproval only. Workspace roles, comma separated (for example Finance, Workspace Owner). Everyone who holds one of them when the node runs is asked too.
TitleThe heading of the request.
MessageWhat you are asking. Supports ${...} expressions, for example Refund ${output.amount} to ${output.customer}?.
Response TypeApproval (Approve and Decline buttons), Free Text (a text box) or Custom Form (the fields in Form Fields (JSON)).
Approval OptionsApprove and Decline, or Approve Only.
Approvals NeededApproval only: Any one (the first answer decides), All of them, or A number of them. See Approvals with several approvers.
Number of ApprovalsWith A number of them: how many approvers must approve.
Approve / Decline / Submit Button LabelThe button texts.
Limit Wait TimeStop waiting after Wait At Most minutes, hours or days and continue down Timed out.

Approvals with several approvers​

With Response Type set to Approval, the node can ask several approvers and wait until enough of them agree:

  • Any one (the first answer decides) — the default. The first approver to answer decides, whether they approve or decline.
  • All of them — every approver must approve. The first decline declines the request, because it can no longer be approved by everyone.
  • A number of them — Number of Approvals of the approvers must approve. The request is declined as soon as that many approvals can no longer be reached: with two of three needed, two declines decline it.

Approvers are the people in Ask (user IDs) plus everyone holding one of the Ask Roles when the node runs. A person named both ways is asked once. The list is fixed when the request is made: someone who gets the role later is not added, and someone who loses it stays on the request.

Each approver answers once, from the Approvals inbox, and can add a Comment with their answer. With All of them or A number of them, every answer counts, so the request cannot be answered from a link: the notification opens the Approvals inbox instead.

The node checks its settings before it pauses and fails with a readable message when the approval could never be met, for example when Number of Approvals is higher than the number of approvers, a role does not exist in the workspace, or nobody holds it.

Example: payment approval​

A payment over a threshold needs two approvals from the Finance team:

  1. Add a Send and Wait for Response node after the step that prepares the payment.
  2. Set Response Type to Approval, Ask Roles to Finance, Approvals Needed to A number of them and Number of Approvals to 2.
  3. Write the Message, for example Pay ${output.amount} to ${output.supplier}?.
  4. Connect Approved to the payment step and Declined to a notification for the requester.

Every Finance member gets a notification. When the second of them approves, the run continues down Approved; the request on the run lists who approved, who declined and their comments.

What the node outputs​

On an approval, data.approved is true or false, and decision is approved, declined or timedOut. A free-text answer is in data.text; a custom form adds one key per field to data. respondedBy is the person whose answer decided the request, and respondedVia says how it came in (in_app, link or timer).

An approval answered in-app also carries approval:

{
"quorum": "count",
"requiredApprovals": 2,
"approvedCount": 2,
"rejectedCount": 0,
"approvers": [
{ "approverId": "…", "decision": "approved", "comment": "Budget checked", "answeredAt": "2026-11-11T10:00:00.000Z" },
{ "approverId": "…", "decision": "approved", "comment": null, "answeredAt": "2026-11-11T10:04:00.000Z" },
{ "approverId": "…", "decision": "pending", "comment": null, "answeredAt": null }
]
}

An approver who did not answer before the request was decided stays pending.

On the run​

The run page lists every request the run made, under Waiting on people while one is open: who was asked, through which channel, until when, and the outcome. For an approval it also lists each approver, how they were asked (by name or asked as a role), what they answered and when, and their comment.

Wait limit​

With Limit Wait Time on, a request nobody answered in time continues down Timed out. Answers given before then still count: a two-of-three approval with one approval at the deadline times out. A run that is cancelled, or retried from this node, withdraws its open requests.

Who can answer​

Only the people a request names can answer it in-app; a request that names nobody can be answered by any workspace member. Approvers see the requests addressed to them in the Approvals inbox even on runs they cannot otherwise open. See Approvals and Roles and Permissions.