Zapier AI Agents for beginners: your first agent

Who this is for

You have landed on Zapier, you want to build an agent, and the interface is showing you several things that all sound like the product you came for. By the end of this page you will know which one you actually want, what a free account covers, and what to build first. No code, about half an hour for the build itself.

Agents and Zaps are not the same product

This is the single most useful thing to get straight before you start, because guides for one do not apply to the other.

A Zap is automation with a fixed path. When this happens, do that, then that. You decide every step in advance and it runs the same way every time. Excellent for plumbing between apps. Not an agent.

An agent is given a goal, a set of instructions and some tools, and it works out the steps itself. You do not tell it to search then read then summarise. You tell it what you want and what it is allowed to use, and it decides the order.

They are separate products on separate meters — running an agent does not consume the task allowance your Zaps draw on. For a first agent, you want Zapier Agents, and you can ignore Zaps entirely.

What a free account covers

Enough to build a real agent and keep using it. No card is required to create the account, and Agents on the free plan is a permanent feature of that plan rather than something borrowed from a trial.

That matters because new accounts also get a 14-day Pro trial, which covers different products entirely — so the free tier you are building on is not a countdown running down behind you. The detail of what that trial does and does not cover is worth knowing if you are in your first fortnight.

The full breakdown of what the free plan allows — what counts as an activity, why test runs cost you, when the allowance resets — is worth reading before you start rather than after.

Build this first

A research-and-summary agent. Give it a topic, get back a short structured brief.

It is the right first build for three reasons. The output is something you can immediately judge as good or bad, which most demo agents are not. It uses exactly one tool, so there is one thing to get working rather than four. And the shape — take an input, go and fetch, return a format — is the shape of most agents worth having, so the pattern transfers.

Resist building the ambitious thing first. An agent with five jobs fails in five places and you will not know which one to fix.

The order to do it in

1. Write the job in one sentence before you open anything. If you cannot, the agent cannot either.
2. Create the agent and write its instructions in plain English. Cover what to work on, what to include, what to leave out, and what format to return.
3. Connect the web search tool. Until you do, the agent can only talk about researching. This is the step that takes longest — that is normal.
4. Run it on a topic you know well. You need to be able to mark the homework.
5. Change one instruction and run it again. Compare the two outputs. This is where the actual learning is.

The full block-by-block version goes through each of these properly, with a checklist.

Two things that will confuse you, in advance

"Tool" and "capability" are the same thing. Different parts of the interface and different guides use different words for the thing that lets your agent reach outside itself. Nothing has gone wrong.

A run that stops and asks you a question has not crashed. On the free plan a single run can use up to 10activities — a search, a page read, an action — before it pauses for input instead of finishing. It arrives in exactly the place a result was meant to, which is why it reads as a failure. What to do when that happens is a short read and worth having seen before it happens to you.

Checked on 23 August 2026 against Zapier's usage documentation and its pricing page. Platform limits move, so treat the date as part of the fact — if you are reading this much later, verify before relying on it.

What you should have at the end

An agent on your own account that you can point at any topic and get a usable brief back from, and a working understanding of which part to change when the output is wrong. That second thing is the one that makes the next agent faster.

The instructions for this agent are written out in full here, and Agent in 30 is the guided version of the same build.