Decision guide

AI agent vs chatbot vs Zapier: which one does your workflow actually need?

A chatbot answers questions. Zapier (or Make, or n8n) moves data between apps when a trigger fires. An AI agent reads a situation, decides which of several actions to take, calls the tools to take them, and checks the result. If your workflow is "answer the same questions", buy a chatbot. If it is "when X happens, copy Y to Z", build a Zap. If it is "look at this, work out what to do, do it, and know when to ask a person", that is an agent, and the other two will break on the first message that does not fit the template.

The three get sold with the same words, which is why so many businesses buy the wrong one. This page puts them side by side on the questions that matter: what each can decide, what it costs, what breaks it, and when you should not use any of them.

Side by side

ChatbotZapier / Make / n8nAI agent
What it doesAnswers questions from a script or a knowledge baseMoves data between apps when a trigger firesReads a situation, decides, acts through tools, checks the result
Handles an unexpected messageFalls back to "I didn’t understand"Never sees it; a Zap has no conversationClassifies it, acts or escalates with context
Multi-step tasksNoYes, if every step is fixed in advanceYes, including deciding the steps
Judgment callsNoneNone (filters and conditions only)Within rules you write; approval step for the rest
Writes to your systemsRarely; mostly links outYes, mechanicallyYes, through named tools with permissions
Typical setupHours to daysHours to a weekTwo to three weeks for a pilot; six to twelve for a full workflow
Typical cost$0–$300 a month SaaS$20–$600 a month SaaS plus setup time$4,500 pilot; $8,000–$42,000 for one workflow in production
Running costSubscriptionSubscription, per taskModel usage, roughly $30–$600 a month at SMB volume
What breaks itA question off the scriptA field renamed in either app; a case the branches did not foreseeRules nobody wrote down; data it cannot reach
Best forFAQs, hours, order statusForm → CRM → Slack plumbingBooking, qualifying, chasing, reconciling, triaging
Costs are what we see quoted in 2026 for small and mid-sized businesses; our own prices are on the pricing page.

Which to pick, and when

Pick a chatbot

When the job is answering the same forty questions and sending people to the right page. It is cheap, it is quick, and it is the right tool more often than vendors of agents admit.

  • Your support inbox is mostly hours, fees, status and "how do I" questions
  • Nothing needs to be booked, changed or written to a system
  • A wrong answer costs a follow-up, not a customer

Pick Zapier, Make or n8n

When the workflow is fully specified and every branch is known. Automations are the plumbing most businesses are missing, and an agent on top of missing plumbing is a waste.

  • Every step is "when A, do B" with no reading involved
  • The apps involved have good connectors and stable fields
  • Volume is under a few thousand runs a month, or you have budgeted for per-task pricing

Pick an AI agent

When the work needs reading and deciding before acting, and the cases vary enough that a template breaks. Agents are also what you build when a chatbot has failed because people kept asking it to do things.

  • The input is a message, a document or a record that has to be understood first
  • The right action depends on the content, not just on the trigger
  • Someone currently does this by hand and would rather not
  • A person can approve the actions that matter

What each one can and cannot decide

A chatbot decides nothing: it matches a question to an answer. That is a feature when the answers are fixed, and the whole problem the moment someone writes "can I move Thursday to Friday and add my son?"

Zapier decides with conditions: if the form says "Enterprise", route to Priya; else, to the queue. It is fast and reliable as long as reality fits the branches. It cannot read a bank statement and tell you which page is missing, and it cannot notice that two of its own branches contradict each other.

An agent decides within a rulebook you write. It reads the message, works out that this is a reschedule with an added patient, checks what the rules allow, calls the booking tool twice, and confirms. When the message is a symptom, the rulebook says escalate, and it does. The rulebook is the product; the model is the engine that applies it to messy input.

Where the costs actually sit

Chatbots and automations are priced as subscriptions, so they look cheap and the cost is the hours your team spends around them: maintaining the script, fixing the Zap when a field is renamed, handling everything that fell through.

An agent is priced as a build plus model usage. The build is the larger number and it buys the rulebook, the integrations, the approval step and the console. Usage is small at SMB volumes and scales with messages. The pricing page has our bands; the cost estimator gives you a range for your case in two minutes.

VolumeTypical agent running cost per month (USD)
Under 500 runs a month$30–$120
500–5,000 runs a month$120–$600
5,000+ runs a month$600–$2,500
Model usage plus hosting for a Supabase and Vercel setup. Messaging (WhatsApp templates, SMS) is billed by the carrier on top.

Combine them: the pattern that usually wins

The best setups we see are not one of the three. A Zap moves the form submission into the CRM. The agent reads it, qualifies the lead, books the slot and writes the summary. A chatbot on the website answers the hours question before anyone needs the agent. Each does the part it is good at, and the agent is reserved for the part that needs reading.

That also keeps the agent small, which is what keeps it trustworthy: five tools, a rulebook and an approval step are easy to audit. An agent asked to do everything is not.

When you need none of them

  • The process does not exist yet. Automating a process nobody has agreed on produces disagreement faster.
  • Volume is a handful a week. A person with a checklist is cheaper and better.
  • The decision legally belongs to a professional: diagnosis, legal advice, lending approval. Build tools that prepare, not agents that decide.
  • The data is not reachable. Fix access first; an agent cannot read what it cannot see.

Decide in 5 questions

Answer them in order. Most people are done by the third.

  1. 1

    Does the input have to be read and understood before anything can happen?

    Yes: Chatbot or agent. Continue.

    No: Zapier, Make or n8n. You are done.

  2. 2

    Does something have to be booked, changed, written or sent as a result?

    Yes: Agent. Continue.

    No: A chatbot with a good knowledge base.

  3. 3

    Does the right action depend on the content, not just on which form was filled?

    Yes: Agent. Continue.

    No: Zapier with conditions, possibly with a chatbot in front.

  4. 4

    Can a person approve the actions that matter, at least at first?

    Yes: Agent, with an approval step. Start with a pilot.

    No: Not yet. Decide who approves, then come back.

  5. 5

    Does it happen at least a few dozen times a week?

    Yes: Worth building. Scope it.

    No: A person with a checklist, until it does.

FAQ

Common questions

Is an AI agent just a chatbot with extra steps?

No. A chatbot has one tool: reply. An agent has several (check availability, book, escalate, update the CRM) and decides which to use. The conversation is one input among others; a scheduled report-assembly agent never talks to anyone.

Can Zapier call an AI model? Doesn’t that make it an agent?

Zapier can insert an AI step that summarises or classifies, and that is useful. It is still a fixed pipeline: the model produces text, the next step does the one thing it was wired to do. An agent chooses its next step based on what it found, and can loop, retry and ask.

Which is safest?

The one with the smallest permission list for the job. A chatbot that can only reply is very safe and very limited. An agent is as safe as its tool list and its approval step, which is why we publish both on every case study.

How much does an AI agent cost compared with a chatbot subscription?

A chatbot runs $0–$300 a month. An agent pilot is $4,500 fixed for one workflow in two to three weeks, and one workflow in production is $8,000–$42,000, plus model usage. The comparison only makes sense against the hours the workflow currently costs, which is what the savings calculator is for.

Is an AI agent better than a chatbot?

Not better, different. A chatbot answers questions from a script or a knowledge base and is the right, cheap tool when that is the whole job. An AI agent reads a message, decides which of several actions applies, does it through your systems and asks a person when the rules say so. If customers only ask things, buy a chatbot; if they ask you to do things, you need an agent.

What is the difference between an AI agent and automation?

Who decides the steps. An automation (Zapier, Make, n8n) runs steps you fixed in advance when a trigger fires, and it never reads anything. An agent reads the input, works out which steps apply this time, and can loop, retry and escalate. Automation is the plumbing most businesses are missing; the agent is for the part that needs reading and judgment.

What is an AI agent in simple terms?

Software that reads a situation, picks an action from a short list it is allowed to take, does it through your tools, checks the result, and hands over to a person when the rules say so. The list of tools is what it can do and the rulebook is what it may do; everything else on this site follows from those two.