What changed for Zapier Agents?
Zapier's standalone Agents, which ran at agents.zapier.com, now live inside the Zap editor as an "AI by Zapier" step. Existing agents convert automatically into a Zap with a normal trigger and one AI step that keeps the original prompt and tools. Zapier's help article was last updated on 1 October 2026.
The change was first reported from 9 September 2026, which is secondary coverage; Zapier's own help article is the primary source for how it works now. Zapier says it "has not set a date to turn off Agents yet", and users receive email notice before any shutdown.
What can the AI by Zapier step do?
The step adds per-tool approvals, a choice of model tier, structured outputs, and full run history in the normal Zap log. Zapier's help article lists these capabilities for the new step.
- Per-tool approvals. You can switch on "Require approval before running" for any tool, so an action waits for a person.
- Model tiers. The step offers Standard, Advanced and Premium model choices.
- Structured outputs. You define the exact fields the step returns, which lets later steps use them reliably.
- History. Agentic runs appear alongside other automations, so one log covers the whole flow.
How is it billed, and what stops a runaway run?
AI by Zapier uses task-based pricing at standard Zapier rates. A run pauses for review once it reaches its task limit, which is 75 tasks by default and can be raised to 500.
The pause is the safeguard to know about. A run that loops through many records can use tasks quickly, so check the limit before you turn on an AI step for a high-volume flow. Our Zapier pricing guide explains how each action step counts, and the cost calculator compares the same volume on n8n.
What is still not in place?
Knowledge sources for the migrated step are expected in Q4 2026, according to Zapier's help article. Until then, check which sources your agent needs before you migrate it.
Enterprise customers arrange migration with their account representative, and super admins can publish migrated Zaps on behalf of other users. Small teams can migrate their own agents.
What does this mean for a Zapier build?
An AI step is now a normal part of a Zap, so it should follow the same rules as any other step: a named owner, an error alert, and an approval for anything that reaches a customer.
- Review each migrated agent. Confirm the prompt, the tools and the approvals still match what you intend.
- Keep customer messages behind approval. Turn on approvals for any tool that sends a message or changes a record.
- Use fixed steps where you can. A fixed filter and action is easier to test than a prompt, so keep repeated work in plain steps.
Our Zapier automation service builds these flows with approvals, filters and alerts. For AI steps in a wider build, see AI workflow automation and our AI agents service. If you are choosing between Zapier and n8n for AI-heavy flows, n8n vs Zapier compares them, and the n8n Agents launch covers n8n's version. For assistants that reach your apps from outside a Zap, read Zapier's connector in Meta's Muse.
Frequently asked questions
Do I have to rebuild my Zapier Agents?
No. Zapier says existing agents convert automatically into a Zap with a trigger and one AI step, keeping the original prompt and tools.
Has Zapier set a date to turn off standalone Agents?
Not in its help article. Zapier says it has not set a date and that users receive email notice before any shutdown.
Can an AI step send a message without asking me?
Only if you allow it. Each tool has a "Require approval before running" setting, so turn it on for any step that messages a customer or changes a record.
Sources and further reading
- Zapier help: Migrating from Agents to AI by Zapier (primary; last updated 1 October 2026; checked 2026-10-04)
- Collab365: Zapier folds standalone Agents into normal Zaps (secondary; reports the change from 9 September 2026)
Zapier's help article gives no migration deadline. Confirm the current step options and limits in your own Zap editor before you rely on a number here.
