Modes & Approvals

Modes control how actions execute. Choose based on risk and frequency.

The three modes

Autonomous mode

The workflow executes all actions immediately without asking for approval.

{
  "defaultMode": "autonomous"
}

Behavior:

• Read actions execute immediately
• Write actions execute immediately
• No approval requests sent
• Fastest execution

Best for:

• Well-tested, trusted workflows
• Low-risk actions (labeling, archiving)
• High-frequency triggers (incoming email)
• Workflows that only report to you

Approval-required mode

The workflow proposes write actions but waits for your approval before executing.

{
  "defaultMode": "hitl"
}

Behavior:

• Read actions execute immediately
• Write actions create approval requests
• You receive notifications with approve/reject links
• Actions execute only after approval

Best for:

• New or untested workflows
• Workflows that send emails
• High-stakes automations
• Workflows with access to sensitive tools

Approval flow:

Read-only mode

The workflow can only read and analyze — it cannot modify anything.

{
  "defaultMode": "read-only"
}

Behavior:

• Read actions execute normally
• Write actions are blocked entirely
• Cannot label, archive, or send
• Can still send reports to you via send_email_to_user

Best for:

• Analytics and reporting workflows
• Research workflows
• Testing new configurations
• Workflows that only gather information

Which actions require approval?

In approval-required mode, write actions require approval:

Approval notifications

When a workflow in approval-required mode wants to take a write action:

1. Email notification — You receive an email with the proposed action
2. In-app notification — Visible in the Approvals page
3. Action links — One-click approve or reject

Approvals include:

• Which workflow is requesting
• What action it wants to take
• Why (the workflow’s reasoning)
• Links to approve or reject

Progressive rollout

A common pattern is to start restrictive and loosen over time:

1. Start with Read-Only — Workflow can analyze but not act
2. Move to Approval-Required — Workflow can propose actions for review
3. Autonomous — When behavior is stable and low-risk

Mode selection guide

Per-tool mode override

You can set different modes for specific tools:

{
  "defaultMode": "autonomous",
  "tools": [
    { "toolId": "read_email" },
    { "toolId": "archive_email" },
    { "toolId": "send_email_to_user", "mode": "hitl" }
  ]
}

This workflow is autonomous for most actions, but sending emails still requires approval.

Best practices