Decisions & approvals
Many requests exist to get a yes, a no, or a request for changes. The Decision question records that verdict so you and your workflow can act on it.
Why a special question
Every author words “yes” differently, which makes a plain choice question hard for a workflow to act on. The Decision
question always records one of three fixed values, approve, decline or changes, whatever its labels
say and in any language. When the recipient picks one, the request ends with that outcome.
Add one to your form
- 1
Add the question
In the editor, click Decision in the Blocks tab, or press / and pick it.
- 2
Reword the labels
The question reads "Do you approve?" with Approve, Decline, and Request changes. Reword them as you like, for example "Sign off" or "Send back for edits".
- 3
Ask why, if you need to
Add a long-text question after it, and use conditional logic to show it only for decline and changes.
- 4
Publish
Requests sent after you publish end with an outcome.
Keep the three keys
Reword the labels freely, but keep all three options and their keys. Publishing warns you if one is missing. A Decision question inside a repeating group gives no outcome.
The three values
| Value | Default label | Means |
|---|---|---|
| approve | Approve | The recipient agreed. |
| decline | Decline | They said no. The request still completes, with decline as its outcome. |
| changes | Request changes | They want something changed before they agree. Usually the cue to send a new request. |
If you add a fourth option, picking it is an ordinary answer: the request completes with no outcome.
Where the outcome shows up
On the Requests page: Approved, Declined or Changes requested on the request, and an Outcome filter.
- In the form’s submissions, as an ordinary answer to the Decision question.
In what a waiting workflow receives, so Zapier, Make or n8n can take a different path for each verdict. Expired and canceled requests have no outcome.
An AI agent can add a Decision question and read the outcome too. Developers: see Request callbacks.