n8n vs Zapier vs an AI agent for your online store: costs compared

In short: n8n and Zapier run a workflow you design in advance, so every new order goes through the same steps. An AI agent (Claude Code, Codex, Gemini CLI) carries out a new task from one sentence in plain English. Zapier starts at $19.99 a month for multi-step Zaps, n8n Cloud at €20 a month billed annually, and connecting an AI agent to a CloudCart store costs nothing.

Below: what each tool does, what it costs and how to connect it to a CloudCart store, whether you sell in one EU country or run a store per country.

What does n8n do?

n8n (pronounced "n-eight-n", short for "nodemation") is a Berlin-built automation platform where you connect apps into a workflow of blocks (nodes) on a visual canvas. A workflow starts with a trigger, runs steps that read and filter data, and ends with an action such as a Google Sheets row or an email.

For a store two nodes matter most: Webhook receives an event from the store, such as "an order was created", and HTTP Request calls the store's API or another service. Between them you add conditions, JavaScript or Python and AI steps; every n8n Cloud plan includes AI agent, MCP and AI model nodes (n8n.io/pricing).

n8n Cloud is hosted by the company and billed by workflow executions. Community Edition runs on your own server with no licence fee, but updates and security are yours. Its "fair-code" Sustainable Use License lets you read the source and use it in your own business, with limits on reselling it as a service. Self-hosting also keeps your customers' order data on a server you choose.

What is Zapier, and what is Make?

Zapier is a hosted automation tool where a workflow is called a Zap: a trigger in one app and actions in others. It lists more than 9,000 apps and bills by tasks, where every action that runs is one task (zapier.com/pricing). The $0 plan gives 100 tasks a month and two-step Zaps only. Multi-step Zaps and the Webhooks trigger start with Professional. Zapier checks for new events every 15 minutes on the $0 plan and every 2 minutes on Professional; webhooks arrive at once.

Make (make.com) does the same with visual scenarios. All three connect to CloudCart through the REST API and webhooks, and all three only do what you have drawn: a new question means a new workflow. That is the main difference from an AI agent.

Zapier vs n8n: the differences in one table

Zapier is easier to start with and has more ready-made connections. n8n is more flexible and cheaper for long workflows, because it bills a whole execution however many steps it has. With no technical person, Zapier is the faster start; with someone who writes code, n8n gives more for the money.

	Zapier	n8n	AI agent with CloudCart
How you set the task	Build a Zap	Build a workflow of nodes	One sentence, in English or your own language
What you pay for	Tasks (every action)	Executions (steps not counted)	The AI assistant subscription
Entry price	$0 for 100 tasks; Professional from $19.99/month	Starter €20, Pro €50 a month (billed annually); self-hosted with no licence fee	CloudCart charges nothing for the connection
Reaction time	15 min ($0), 2 min (Professional); webhooks at once	Webhooks at once, schedules as you set	As soon as you type
Runs on its own, around the clock	Yes	Yes	When you ask, or on a schedule in the assistant
A task you did not plan for	New Zap	New workflow	Straight away
Sees store data	Fields in the Zap	Fields in the workflow	Products, orders, customers, reports, within the key's permissions
Connection to CloudCart	API key and webhooks	API key and webhooks	Personal access token (PAT) and the Admin GraphQL API

n8n Starter includes 2,500 executions a month and Pro 10,000. Zapier's price is the 750-task annual tier.

Is n8n outdated because of AI agents, and is it risky?

No. n8n workflows now call AI models and MCP servers; n8n stays best for repeating events, while new questions go to an AI agent.

On n8n Cloud the server is the company's job; self-hosted, it is yours. If your server goes down, the store's webhook never arrives, and after 6 failed attempts CloudCart switches it off. Keep the store's keys in n8n Credentials, never in the workflow text.

Order webhooks carry names, addresses and emails, so a hosted tool processes personal data for you. Under Article 28 of the GDPR you may only use a processor with sufficient guarantees, under a written contract. Check that Zapier, Make or n8n Cloud offer a data processing agreement before sending them orders.

When you need a workflow and when you need a sentence

A workflow is for the same action every time the same event happens, without you watching. A sentence to an AI agent is for a task that is new, runs through a lot of data or needs judgement. Most stores need both.

Choose Zapier or n8n when

• the event repeats: a new order, a new customer, a stock change;
• the action is always the same: a row in Google Sheets, an email to the warehouse;
• it must happen within the minute, at night and at weekends too.

Choose an AI agent when

• the task changes each time: "take 15% off the Winter category until Sunday";
• you need sales, stock and channels in one answer;
• the result is text or a decision: descriptions, a segment, a report with conclusions;
• it touches hundreds of products, such as a new supplier price list.

How to connect Zapier, Make and n8n to CloudCart: API key and webhooks

Automation tools connect to a CloudCart store through an API key for the REST API (JSON-API v2) and webhooks, which push store events to the workflow. Zapier is ticked on every plan on the pricing page, but REST API requests start with Starter Pack: 50 a minute, CC Pro 100, CC Master 150; Baby Pack has none.

1. API key. Settings → Api keys → + Add Api key. Give it a unique name, such as "n8n orders".
2. Connection details. Copy the Site ID and the API address (your-store-address/api/v2) from the same screen into the workflow, with the key.
3. Workflow address. In n8n add a Webhook node and copy its URL; in Zapier choose the Webhooks trigger (Professional and up).
4. Webhook in the store. Settings → Webhooks → + Add webhook: paste the address, pick an event such as order.created and the key. The store sends the key in the X-CloudCart-ApiKey header, so the workflow can check the sender.
5. Test. Place a test order and check that the event arrived with the order data.
6. Action. Add the steps: a sheet row, an email, a record in another system.

The store sends 20 event types: created, updated and deleted for categories, brands, products, discounts, customers and subscribers, plus order created and updated. product.* events fire only on saves in the admin, not when stock drops from orders, API writes or imports. So a "stock below 5" alert uses order.created and then reads stock through the API.

Important: the workflow must reply with a 2xx code within 5 seconds. On temporary errors CloudCart tries up to 6 times over about 20 minutes, then switches the webhook off and emails you; on permanent errors (401, 403, 404) it switches it off at once. You switch it back on in Settings → Webhooks. All keys of a store share one request limit.

With a store per country, each store has its own keys, webhooks and limit. Formats are in the developer documentation. For ERP links, check the integrations catalogue first and see how an ERP system connects to an online store.

How to connect an AI agent to CloudCart: a PAT token and one sentence

An AI agent connects with a personal access token (PAT) that only the store owner can create. It works through the Admin GraphQL API, with more than 1,100 operations and 300 requests a minute per store address.

1. Key. Profile menu at the bottom left → PAT Tokens → Create Token. Choose "Read Only", "Custom Permissions" (products, orders, customers, inventory, discounts, blog, settings, webhooks) or "Full Access".
2. Limits. Under Advanced Settings set an expiry date and up to 20 IP addresses. The key starts with cc_pat_ and is shown once.
3. Sentence. Copy it from the "Connect your store to an AI agent" card on the dashboard or the AI integration page into Claude Code, ChatGPT Codex, Gemini CLI, Cursor or VS Code.
4. Sign-in. The agent installs the CloudCart tools, asks for your language, the key and the store address.
5. First task. "Show me sales by source for the last 30 days."

Full guides: Claude Code for an online store and an online store with ChatGPT and Codex. With the CloudCart skills (Claude Code, Cursor, Gemini CLI, VS Code) the agent previews every change to 10 or more products and waits for your yes. A daily report is scheduled in the assistant itself, as in the article on the 8 a.m. sales report.

What each option costs: Zapier, n8n, an AI agent, a hire and an agency

For a small store the cheapest setup that works is an AI agent for daily work plus one or two workflows for events. The hire and agency rows are assumptions; use your own numbers.

Option	Monthly cost	What you get	Hidden cost
Zapier	$0 (100 tasks) or from $19.99	Event-driven workflows	Bill grows with tasks; each new question is a new Zap
n8n Cloud	€20 (2,500 executions) or €50 (10,000), annual	Complex workflows with code and AI	Needs someone who knows APIs
Self-hosted n8n	No licence fee; you pay the server	Full control, no execution limit	Updates, backups, security
AI agent	Connection costs nothing; Claude Pro is $17/month billed annually (claude.com/pricing)	Reports, bulk changes, copy, new tasks	Works when asked or scheduled; big changes wait for your yes
A hire (assumption)	€20 an hour; 19 hours is ~€380	Judgement, customers, packing	Holidays, training, slow on hundreds of rows
An agency (assumption)	Monthly retainer	Strategy, ads, creative	Sees your data only when you send it

The hours come from the worked example for the AI agent: a cosmetics store with 400 products spends about 23 hours a month on routine tasks by hand and about 4 with the agent. Nineteen hours at €20 is about €380, against $17 for the assistant. Eurostat puts the average EU hourly labour cost at €34.9 (from €12.0 to €56.8 by country), so in most of Europe the saving is larger.

10 online store tasks: which tool does each one better

Workflows win on events; the agent wins on data and copy. Some tasks are built into CloudCart.

Task	Better choice	How
Every new order as a Google Sheets row	Zapier or n8n	order.created webhook and a Sheets action
Alert when stock falls below 5	n8n	order.created, a stock check via API, a filter
Supplier price list for 400 products	AI agent	"Update prices by SKU and show me which are missing."
Weekly report with conclusions	AI agent	"Sales, AOV and channels this week vs last. What changed?"
Abandoned cart email	Built into CloudCart	The automatic email and report in the admin
Email campaign to a segment	AI agent and Marketing Suite	The agent builds segment and draft; you send
Descriptions and SEO titles	AI agent	"Write descriptions for the 40 new products; show me before saving."
Meta, Google Ads, TikTok vs sales	AI agent	Ad export compared with sales by source
Search Console pages with few clicks	AI agent	New SEO titles, saved after your yes
Share of mobile visits	AI agent	"Visits by device, last 90 days vs the 90 before."

Abandoned carts need no outside tool: see abandoned carts in CloudCart.

Email, ads, Search Console and metrics: what an agent gives you that a workflow does not

A workflow moves data. An agent reads it, compares it and tells you what to do.

• Email through Marketing Suite. CloudCart's Marketing Suite covers email, SMS, Viber and web push, with segments and automated sequences. The agent builds a segment ("2+ orders, none in 90 days") and a draft; you send it. Send marketing only to people who opted in, as the GDPR requires. More in email marketing for an online store and email campaigns in CloudCart step by step.
• Ads. From a CSV export the agent compares spend with sales by source. See Meta Ads, Google Ads and TikTok ads.
• Search Console. It finds pages with many impressions and few clicks and suggests titles. See Google Search Console for an online store.
• Metrics. Sales, AOV, conversion rate, abandoned carts, sales by source and returning customers, read with a "Read Only" key. See ecommerce KPIs and the mobile version of an online store.

Ready-made sentences are in 30 prompts for your AI agent.

Can an AI agent replace an employee?

It replaces routine admin hours, not the person who decides, talks to customers and packs parcels. In the sample store that is about 19 hours a month, which your team can spend on service, photos and shipping.

A good split: an agency does strategy and creative, and you check results weekly with the agent. Shoppers' questions are a separate job for AURA with Aura Chat in the storefront.

Why run your store through an AI agent: 7 reasons

1. Unplanned questions. A workflow knows only what you drew; the agent answers this morning's question.
2. One answer from several reports. "Which of my 10 best sellers run out within 10 days?" is three screens or one sentence.
3. No task meter. The assistant is a fixed subscription (with usage limits), and the CloudCart connection costs nothing.
4. Copy from real data, in each store's language.
5. It knows the platform from the CloudCart wiki and skills.
6. Same-day promotions, and sold-out products hidden at once.
7. You stay in control: read only, selected areas or full access, with expiry and IP limits, switched off in one click under "PAT Tokens".

The best setup: an AI agent plus one or two workflows

Most stores do best with two or three workflows for round-the-clock events and an AI agent for the rest.

1. List repeating events: new order, low stock, new B2B customer, one action each.
2. Check what is built in: abandoned cart emails, ERP and courier links.
3. Workflow the rest, with a separate API key per tool.
4. Agent for "how many", "which" and "do": reports, bulk changes, copy, segments.
5. Weekly review: what you keep repeating by hand becomes a workflow.

n8n (through its MCP nodes) and Zapier (through Zapier MCP) both support MCP, the standard AI agents use to call outside tools, so your agent can also trigger a ready-made workflow.

Common ecommerce automation mistakes

• A workflow for every report. Ten Zaps cost tasks every month; reports suit the agent.
• One key for everything. One API key per workflow and one PAT per agent.
• Full access on day one. Start the agent on "Read Only".
• No data processing agreement with a hosted tool that receives orders.
• Bulk changes with no preview. API changes have no undo; ask "show me first".
• Baby Pack for API workflows. API requests start with Starter Pack.

Frequently asked questions

Create a store for €1 and try the AI agent and workflows in a real store. Questions go to support@cloudcart.com.