Tool approvals and action parameters

Home Tools Platforms Zapier Tool approvals and action parameters

Enable a pause before an agent calls a sensitive app action and verify the inputs it proposes.

Workflow & automation · Documented · Documentation checked 2026-10-04

Zaps, AI by Zapier, Tables, and connected app actions; standalone Agents is migrating.

Supported tool-capable model tier and connected app account required. Require approval before running is off by default.

The worked example is illustrative and has not been tested in a signed-in product account.

What it does and how it connects

Enable a pause before an agent calls a sensitive app action and verify the inputs it proposes.

Tool approval pauses a supported AI by Zapier run before a selected tool executes. Require approval before running is off by default. Pinning destinations and requiring review serve different purposes: one narrows parameters, the other checks a proposed operation before it happens.

Walkthrough

Use the product named in the access panel. The steps below combine documented controls with the editorial example.

  1. Add the intended sensitive tool in a supported Tools and Knowledge configuration.
  2. Set critical fields such as destination from controlled values.
  3. Enable Require approval before running for the action tool.
  4. Test approval and denial on a sandbox destination and inspect whether the action ran.

Worked example

A workshop invitation should pause with the exact recipient and content visible. A denial should stop that action. Do not let another ungated email tool perform the same send after rejection.

Draft the invitation for the verified workshop and pinned test recipient. Use the configured send tool only through its approval gate. If approval is denied, the recipient is ambiguous, or the content changes after review, stop. Do not use another service to send it.

Inspect and verify the result

Observe the pause before execution. Deny a sample call and check that no outbound message appears. For an approved sandbox call, compare the tool input with the actual destination result.

Limits and troubleshooting

Approval support depends on the eligible tool configuration. A verbal ask me first instruction is not an enforced pause. Inspect behavior for timeout, missing reviewer, and an edited proposal before using live recipients.

Data, permissions, and actions

Review requests disclose proposed action details to reviewers. Restrict those recipients and connected credentials. An approval authorizes the reviewed operation, not arbitrary future actions or a change to account permissions.

Tables, product boundaries, and operating cost

Separate stored business records from conversation memory and account for repeated AI tool calls.

Explore Tables, product boundaries, and operating cost

A fixed question-to-draft Zap

Turn a synthetic question into declared fields and a private response draft.

Explore A fixed question-to-draft Zap

A tool agent and a reviewed action

Use a supported AI by Zapier tool configuration with an actual pause before a sensitive action.

Explore A tool agent and a reviewed action

Permissions and meaningful approvals

Decide what a system may read, what it may change, and when someone needs to authorize a concrete action.

Explore Permissions and meaningful approvals

Sources and verification

Documentation checked 2026-10-04. Examples are illustrative unless described otherwise.

AI by Zapier tools and approvals · Zapier

Share this page