Help Centre › Building Processes
Request approval from a user before continuing execution.
Add it to a process
In the process designer, open the Add step tab. Find Request approval under Action Center, or type its name in the search box, and drag it onto the canvas.
Fields
| Field | Required | What it does |
|---|---|---|
| Approval title | Yes | Title of the approval request. Supports variables. |
| Description | No | Details for the approver to review. Supports variables. |
| Context data (JSON) | No | JSON data to show the approver, e.g. {"po_number":"{po}","total":"{amount}"} |
| Priority | No | Approval priority level Choices: Critical, High, Medium, Low. |
| Approver | No | User ID of the approver, or a variable like {approver_id}. |
| Variable | Yes | Name of the variable where the result will be stored |
| Due date | No | Approval deadline (YYYY-MM-DD HH:MM:SS). Supports variables. |
| Suggestion | No | Answers to suggest to the approver, who can correct them before approving. Shape: {"fields": [{"name", "label", "value"}], "remember": {"lookup", "sourceField", "targetField"}}. `value` supports variables and formulas. Once approved, each corrected answer is saved into the variable called `name`; a rejection keeps the run's own values. The values are sent only when the company has switched on "suggested answers for approval", and a sensitive value is never sent. `remember` is used by the web only: once approved, it adds a row to that lookup table. |
What it gives back
{approval}– True if approved, False if rejected, None if the answer could not be read{approval_note}– the approver's optional reason, "" if none given
See all Action Center steps.