Approval Workflows

Approval workflows give you control over what scheduled agents do. When enabled, the agent runs its prompt and plans actions, but waits for your approval before executing anything with real-world side effects.

How approvals work

When a schedule with approval enabled fires:

1. The agent processes the prompt and determines what actions to take.
2. If the agent proposes actions with side effects (e.g., sending an email, posting a Slack message), those actions are held as pending.
3. The execution moves to a Pending Approval status.
4. You review the proposed actions and either approve or reject them.

If the agent completes its run without proposing any side-effect actions (e.g., it only generated a text response), the execution completes automatically even with approval enabled.

Reviewing pending approvals

Pending approvals are prominently displayed at the top of the Scheduled Agents page. Each pending approval shows:

• Schedule name — Which schedule triggered the execution.
• Agent name — Which agent ran the prompt.
• Start time — When the execution began.
• Pending actions — A list of proposed actions, each showing:
  • The tool being used (e.g., Gmail, Slack, Calendar)
  • A summary of the action (e.g., "Send email to team@company.com")
  • Relevant details (recipients, message content, etc.)

Approving an execution

Click Approve & Execute on a pending execution. This:

1. Executes all pending actions in order.
2. Marks the execution as Approved.
3. Records who approved it and when.

If any action fails during execution, the remaining actions stop and the execution is marked with the error details.

Rejecting an execution

Click Reject on a pending execution. This:

1. Discards all pending actions without executing them.
2. Marks the execution as Rejected.

The agent does not retry rejected executions. The schedule continues to fire at its next configured time.

Viewing execution details

For a more detailed view of a pending or completed execution, click View to navigate to the execution detail page. This shows:

• The rendered prompt that was sent to the agent
• The agent's full response
• Details of each proposed or executed action
• Any error messages

When to use approvals

Approval workflows are recommended when:

• The agent has access to tools that can send messages or modify external systems.
• You want to verify the agent's output quality before it reaches other people.
• You are still fine-tuning the agent's prompt or skills and want to catch mistakes.

You can safely disable approvals when:

• The agent only generates text reports without taking external actions.
• You have thoroughly tested the agent and trust its behavior.
• The schedule runs frequently (e.g., hourly) and manual review would be impractical.