AIOps SRE
Search

Zapier · connected-app automation product

Zapier Agents / AI by Zapier

Official documentation

Zapier is moving its standalone Agents product into AI by Zapier steps in the Zap editor. As of October 2, 2026, no Agents shutdown date has been announced. AI by Zapier brings agentic tool use alongside ordinary Zap steps, allowing a workflow to keep predictable actions in explicit logic. Its billing is task-based; legacy Agents use activity allowances. Treat migration as a workflow review, not a reason to publish without testing. Inspect the AI step, test the complete Zap and configure per-tool approvals before activation. Standalone Agents retain their own account, template and embedding limitations; those should not be generalized to the replacement. Agents remains an alias so readers following older instructions can find the current transition.

Product profileDocumentation checked

AutomationAgents

In this profile

When it fits

Useful for

  • Combining an interpretive tool-using step with ordinary connected-app Zap logic
  • Reviewing an existing Agents workflow during the move to AI by Zapier

Limits to consider

  • Assuming migration automatically supplies approval gates for every tool
  • Applying standalone Agents template or embedding rules to AI by Zapier without checking

Capabilities and platforms

  • AI by Zapier combines agentic tool use with ordinary steps in the Zap editor
  • Per-tool approval settings can pause selected tool use before it runs
  • Legacy Agents configure instructions, triggers, actions and knowledge sources; migration requires review in the Zap workflow

Where it runs

  • Zapier cloud and Zap editor
  • Legacy Agents web surface during the transition

Access and setup

Zapier account and authorized app connections; AI by Zapier uses task-based billing, while standalone Agents use activity allowances. No standalone shutdown date was announced as of October 2, 2026.

Current access and pricing
  1. For an existing Agent, follow the official migration link into the Zap editor; for new work use the current AI by Zapier instructions.
  2. Review the AI step instructions and connected tools, preserving predictable actions as ordinary steps where appropriate.
  3. Test the AI step and the complete Zap with sample input, then configure per-tool approvals before publishing or retiring a legacy workflow.

Proposed exercise · not hands-on tested

Review a migrated draft-generation workflow

Input

An existing draft-generation Agent and synthetic sample records for its replacement Zap.

  1. Inspect the migrated AI step and confirm that its instructions and tools match the intended draft task.
  2. Run sample tests, review output and tool activity, and configure approval on any write tool.
  3. Test the complete workflow and record remaining differences before a deliberate publish-and-retire decision.

Artifact to inspect

A reviewed migration candidate with test observations still to be collected by its owner.

What to verify

Confirm the workflow only reaches intended accounts, approvals actually gate selected tools and both versions will not run unintentionally after activation.

Data handling and permissions

Connected-app access defines what a Zapier workflow can read or change and where it sends data. Review each connection and tool rather than treating an instruction as a permission boundary. The standalone Agents documentation says agents run under their owner's account, templates create copies rather than one shared live agent, and Agents cannot be embedded as customer-facing chatbots. Those statements concern the legacy product; the replacement needs its own settings review. AI by Zapier provides per-tool approval controls that must be configured before publishing. The proposed migration exercise uses synthetic records and offers no universal retention or training guarantee for Zapier or its connected providers.

Other options

n8n
Consider it when hosting and technical workflow control are central.
Make AI Agent (New)
Compare for visual cloud scenarios with distinct agent and fixed-logic choices.

Sources and scope

Documentation-based product profile; no hands-on testing. The proposed workflow is an authored exercise, not a verified outcome or a practical guide. Capabilities and policy statements describe vendor documentation checked October 2, 2026; task-fit comparisons are editorial judgments. Plan, region, administrator and interface limits may apply.

Source review: . Product access and terms can change.

Suggest a correction