Zapier folds standalone Agents into normal Zaps
Reviewed by Helen Jones
Zapier is moving Agents from the separate agents.zapier.com product into AI by Zapier steps inside the main Zap editor. Existing agents convert into a Zap with a native trigger and one AI step that keeps the original prompt, tools, and reasoning. The change went generally available for looping tool calls on 15 July 2026. Enterprise trial migrations ran through 15 August 2026, after which trials expired and converted to free Agents accounts. Zapier’s help guide was updated again on 7 September 2026. What you gain is the rest of Zapier: filters, branching, history, model tier choice, per-tool approvals, structured inputs and outputs, task-based billing, a 75-task run pause, and admin controls over AI Zaps. What you do not get yet is automatic splitting of tools into native steps, a direct match for on-demand chat-triggered agents, or knowledge sources from apps such as HubSpot, Asana, Zendesk, Zoom, and Jira. Those knowledge sources are expected later in Q3 2026.
Before this, many teams treated agents as a separate experiment: a prompt box with tools, floating outside the automations that already run the business. That made one-off wins easy and repeatable team systems hard. You could not cleanly mix AI reasoning with ordinary steps, shared history, or the same approval path used for everything else. After the move, agent-style work lives on the same rails as the rest of your Zaps. That is useful because filters, branching, and human approval can sit beside the AI step instead of living only in someone’s head. It is also a trap if you assume migration equals readiness. A converted agent can still be a black box prompt with missing knowledge sources, no chat trigger, and tools that never became clear native steps. Reliability now depends less on the agent brand and more on whether you redesign the handoff, review, and pause rules around it.
Analysis
Treat this as a workflow audit, not an automatic upgrade. List every live Agent, open the converted Zap, and rewrite it so the AI step has fixed inputs, a human review or approval gate, and a clear stop if tools or knowledge sources are missing before anyone on the team runs it.
Source note
Pulse published by Collab365 Spaces, reviewed by Helen Jones on . Cite as "Zapier folds standalone Agents into normal Zaps", Collab365 Spaces. 1 source referenced.