A connected workflow platform whose AI steps, tool agents, approvals, and stored records should remain distinguishable.
Workflow & automation · Changing · Documentation checked 2026-10-04
Zaps, AI by Zapier, Tables, and connected app actions; standalone Agents is migrating.
Paid plan and model tier affect AI features. Tools and knowledge require supported Advanced / Premium models.
What the platform is for
Zapier connects a trigger to arranged actions. AI by Zapier can transform data, and supported tool configurations can add agentic selection. Tables stores records used by processes. Begin with a fixed sample Zap and inspect mapped fields before enabling model decisions or external actions.
Know the product boundary
Standalone Agents is migrating into AI by Zapier. Older Agents and Interfaces terminology can lag current product naming. Prompt-only AI steps differ from tool-capable steps and optional browsing. Current help has transitional differences about Free / paid access, so the available plan and model tier must be confirmed in the account.
How the components connect
Triggers provide input. Fixed actions carry out a known route. AI output fields provide a draft interpretation. Tools and Knowledge let an eligible agent retrieve or act. The documented per-tool approval control pauses selected actions and is off by default. Tables should store controlled business state separately from a model’s suggestion.
A beginner starting point
Start with a synthetic input and private draft output. Add a structured AI transformation and test uncertainty. Then introduce one read-only tool. Enable and test tool approval before a write, and preserve human ownership of approval state and action reconciliation.
Limits and data choices
Action tests can create real effects. Repeated triggers or uncertain retries can duplicate messages or records. Tools, browsing, tiers, and naming are changing; this edition documents the transition and does not claim every account has the same menu. Every connector and enterprise option is not covered here.
The technical path
Use official Zapier help for exact trigger / action fields, current AI model tiers, tools, Tables, MCP, and administration. For a known route, prefer a fixed Zap; for variable retrieval, keep agent tools narrow and output reviewable. Publish a Zap only after testing rejection and missing-input paths.
Feature map
Zaps, triggers, actions, and mapped fields
Build a fixed process and inspect what its connected accounts can read or change.
AI by Zapier prompts and structured output
Use an AI step to transform text into declared fields before routing it onward.
Tools, knowledge, browsing, and Agents migration
Understand when AI by Zapier chooses tools rather than simply transforming an input.
Tool approvals and action parameters
Enable a pause before an agent calls a sensitive app action and verify the inputs it proposes.
Tables, product boundaries, and operating cost
Separate stored business records from conversation memory and account for repeated AI tool calls.
Complete workflows
A fixed question-to-draft Zap
Turn a synthetic question into declared fields and a private response draft.
A tool agent and a reviewed action
Use a supported AI by Zapier tool configuration with an actual pause before a sensitive action.
Coverage and availability
Models, modes & conversation
Covered: Model tiers and prompt-only versus tool-capable steps.
Search, research & sources
Covered: New tool docs include optional browsing and knowledge; older prompt guidance differs.
Files, analysis & code
Covered: Mapped fields, structured output, Tables, and validation.
Images, video, audio & voice
Covered: Media operations are connector / provider dependent; not a native universal media suite.
Projects, instructions & memory
Changing: Tables records are distinct from model memory; run context must be explicit.
Editing surfaces & deliverables
Covered: Draft fields / records; Forms / interface detail outside this edition.
Agents, skills, plugins & MCP
Covered: Agents migration into AI by Zapier; tools, Knowledge, and optional MCP boundaries.
Orchestration & scheduling
Changing: Zaps and per-tool approvals; approval is off by default.
APIs, SDKs, deployment & evaluation
Separate product: Developer / MCP documentation is a technical path; deployment means tested Zap activation.
Sharing, privacy & governance
Covered: Connected identity, action tests, approvals, and stored-data owners.
Plans, devices & accessibility
Not established: Plan / tier transitions noted; Free access documentation differs and full quotas / accessibility not established.
Sources and verification
Documentation checked 2026-10-04. Examples are illustrative unless described otherwise.
What is a Zap? · Zapier
Zapier product families · Zapier
AI by Zapier: prompts and output fields · Zapier
AI by Zapier tools and approvals · Zapier
Agent knowledge: legacy migration context · Zapier
Key concepts in Zapier Tables · Zapier
Tables, Interfaces, and MCP plan changes · Zapier
Zapier developer documentation: MCP, SDK, integrations · Zapier