AI by Zapier puts AI interpretation and tool use inside the Zap editor, alongside familiar triggers and ordinary automation steps. It is also the destination for standalone Zapier Agents. Migration creates a trigger and a single AI step containing the original instructions and connected tools; it does not automatically turn those tools into separate, more tightly controlled steps. That distinction matters when reviewing an existing agent. You can keep flexible interpretation inside the AI step and move predictable actions into native Zap steps as needed. AI by Zapier uses task-based billing rather than legacy Agents activity allowances. The linked migration guide has not announced an Agents shutdown date.
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 model interpretation and tool calls with ordinary trigger, filter and action steps in the Zap editor.
- Per-tool approval settings can pause a run before a selected tool executes; they need to be configured explicitly.
- Standalone Agents migrate as a trigger plus one AI step containing their instructions and tools, with full workflow testing needed before activation.
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- For an existing Agent, follow the official migration link into the Zap editor; for new work use the current AI by Zapier instructions.
- Review the AI step instructions and connected tools, preserving predictable actions as ordinary steps where appropriate.
- 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.
- Open the migrated Zap and compare its trigger, instructions and connected tools with the original draft-generation Agent. Identify any predictable action that would be clearer as a separate native step.
- Preview the AI step using a synthetic request. Inspect its draft, tool calls and task usage, and enable Require approval before running on any tool whose write action needs review.
- Test the complete Zap, including downstream steps. Record differences from the old workflow, then decide whether it is ready to publish and retire the original so both do not run the same job.
Artifact to inspect
A reviewed migration candidate with test observations still to be collected by its owner.
What to verify
Check that each tool uses the intended account, selected approval gates actually pause the relevant action, and the complete Zap produces the expected draft. Confirm the original Agent and replacement will not both respond to the same trigger.
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.
- 01October 1 migration guidancehelp.zapier.com
- 02Standalone Agents setup and limitshelp.zapier.com
- 03Official plan and pricing informationzapier.com