Skip to main content

Approvals and human questions

Ask Question creates a question in the Task backlog and keeps the workflow waiting for its outcome. The run stays active; creating the Task alone does not complete the step.

Configure a questionโ€‹

Set the question title, optional assignee and optional triggering-record link. Configure 2โ€“50 answer choices and connect every choice to its next step. Renaming or reordering a choice preserves its identity and connection. Removing a choice leaves its downstream steps on the canvas; reconnect or remove them before publishing.

Use Wait up to to set the response deadline, from one second to 30 days, defaulting to seven days. Connect No answer in time to the path that should run when the deadline passes. Connect alternatives through Join when they should share subsequent steps. Incomplete questions can be saved, but every required answer path must be valid before publication.

The step returns the interaction ID, Task ID, status and selected option ID for later mappings. The option is null on expiry, so a receiving field must allow that. Private answer comments are not downstream output.

Approval presetโ€‹

Choose Approval preset in the step picker to start a question with Approve and Reject choices. It uses the same configuration, outputs and answer paths as any other question. You can rename, reorder, add or remove choices.

For example, connect Approve to a preparation Task, Reject to End, and No answer in time to a reminder. Rejection and expiry are business outcomes, not automatically workflow failures.

A question using the Approval preset routes Approve to preparation, Reject to End, and No answer in time to a reminder.

Answering from Tasksโ€‹

Open the question Task, review its prompt and choices, and submit the answer using its interaction controls. Answering requires an active human user with Task write permission. Service accounts cannot answer. Assignment does not grant access and does not restrict answering to the assignee; workflow authoring permission is not required.

Submitting the answer also completes the Task. Workflow continuation is asynchronous, so the run may briefly still show a wait. Conflicting answers or an expired question cannot overwrite an accepted decision.

Question Tasks cannot be completed, reopened or deleted through ordinary Task controls. Their question and record context are fixed, although assignment can change.

Expiry, cancellation and Agent questionsโ€‹

Expiry selects the configured No answer in time path. Cancelling the run closes unanswered questions and prevents further effects, while retaining previous results and decisions.

An Agent can also ask bounded choice or free-text clarification questions if its published configuration permits them. An answer returns to that Agent; it does not itself complete the Agent step. Its budget remains cumulative across questions.

Preview creates no question Task. Select an assumed answer or No answer in time to preview that path. Without an assumed answer, preview stops at the question; it cannot predict a real response or produce execution outputs. See the human-question API reference for the answer contract.