Human Tasks

A Human Task pauses an Action and waits for a person to review, fill in, or approve something before the Action continues. Use Human Tasks when a step needs human judgment — approving a payment, correcting extracted data, choosing between options, or signing off before an automated action is taken.

While a Human Task is pending, the Action's run is paused. When the person submits their response, the Action resumes and the rest of the steps run with that input.

Where to Find Human Tasks

When the feature is enabled for your tenant, Tasks appears in the left navigation. The Human Tasks page lists the tasks created by your Actions, with a status filter for Pending, Completed, Cancelled, Rejected, or All, and card or list views. The list refreshes automatically so new tasks appear as Actions create them.

How Human Tasks Are Created

Human Tasks are produced by Agent steps, not configured as a separate step type. When you want an Agent step to hand off to a person, instruct it (in its prompt) to create a human task. The Agent decides what to ask for and builds the form, then the run pauses until the person responds. The agent can read the response and continue, ask a follow-up, or close the task.

The form a person sees is generated for the task — it can include text fields, dropdowns, and file uploads, along with a submit button whose label the Agent can set.

Completing a Task

1. Open Tasks and select a Pending task.
2. Fill in the requested fields. Required fields must be completed before the form can be submitted.
3. Select the submit button (for example Submit task).

After you submit, the Agent processes your response and the run continues. The task moves to Completed, and you can follow the link to the related run to see what happened next.

Sharing a Task With Someone Outside Studio

Each Human Task can be opened through an isolated access link that does not require a Studio login. This is useful when the person who needs to act — an approver, a vendor, a colleague in another team — is not a Studio user.

When someone opens the link, they verify their identity with a one-time code sent to the task's assigned email address (or, if they are already signed in to Studio with the matching email, they are let straight through). They then see only that one task's form, complete it, and submit. They get no other access to the tenant.

Good Practice

• Make the Agent's request specific about what it needs, so the generated form asks for exactly the right fields.
• Use Human Tasks for genuine decision or correction points, not for steps automation can handle reliably.
• Set an assignee email so the task can be routed and, if needed, shared through an isolated link.
• Review completed tasks and their runs to confirm the human input produced the outcome you expected.

Related Pages

• Agent Steps — the step type that creates Human Tasks.
• Runs — where paused and resumed runs appear.

---