NewFree course: Learn how to runRun Amazon with Claude
DataDoe inside your Zaps

Zapier MCP for Amazon. Zaps that react to your store.

Zapier already links the apps your team works in. Add DataDoe and an Amazon event can start a Zap, a weekly export can land in Gmail, and Zapier’s MCP Client can call DataDoe tools across Seller Central, Vendor Central and Amazon Ads.

Start free trialPick a route
Zapier pieces:Catch HookWebhooks GETMCP Client
• Which direction?

“Zapier MCP” means two things. This page is about the second.

One lets an AI assistant use your Zapier apps. The other lets a Zap use an outside MCP server, such as DataDoe. Searches for Zapier MCP mix them up all the time.

Zapier as the server

Zapier MCP

An assistant such as Claude calls actions in the apps you connected to Zapier: send the email, create the row.

AI assistantClaude, ChatGPT, CursorZapier MCPserver run by ZapierYour Zapier appsGmail, Sheets, CRM
Zapier as the client

MCP Client by Zapier

A Zap, or a Zapier Agent, calls tools on a remote MCP server. Point it at DataDoe and Amazon data becomes a step.

Your Zaptrigger and stepsMCP Clientapp by Zapier, betaDataDoemcp.datadoe.com

They combine well: an assistant connected to DataDoe for the Amazon side and to Zapier MCP for everything else can read a report and file the follow-up in one conversation.

• Setup

Three routes from a Zap to your Amazon data.

Zapier reaches outside MCP servers through its MCP Client app, which Zapier still marks as beta. For fixed reports and Amazon events, the two plainer routes are sturdier today, so those are the ones we recommend first.

Route 1Zapier beta

MCP Client

For a Zap step, or a Zapier Agent, that calls one DataDoe tool: the Action log, a dry-run Action, your list of connected accounts.

  1. On the Zapier Apps page choose + Add connection and pick MCP Client.
  2. Server URL https://mcp.datadoe.com/mcp/v1, Transport Streamable HTTP, OAuth Yes.
  3. Sign in to DataDoe in the tab that opens and approve access, then rename the connection to DataDoe.
  4. In a Zap, use Run Tool as an action or Run Read-Only Tool as a search.

Know the limit. Each step runs one tool. DataDoe builds data exports in the background, so a full report takes several calls in a row, which suits an agent better than a fixed Zap.

Route 2Our pick for reports

Recurring export + Webhooks by Zapier

For the same table every day, week or month: sales by SKU, ad spend by campaign, stock cover.

  1. Create an export schedule once with the DataDoe REST API (POST /exports/schedules), choosing the period and CSV, JSON or Excel.
  2. Schedule by Zapier fires shortly after the export runs.
  3. Webhooks by Zapier, GET, on the export’s latest-file URL, sending your key in the datadoe-api-key header.
  4. Pass the file on with Gmail, Slack or Google Sheets.

Sometimes no Zap at all. A recurring export can email the file to people you list, or to every member of your organization.

Route 3For alerts

DataDoe webhook + Catch Hook

For reacting when Amazon reports a change: a listing changes status, inventory moves, an offer loses the Featured Offer.

  1. Start a Zap with Webhooks by Zapier → Catch Hook and copy its URL.
  2. In DataDoe open Integrations → Webhooks → New webhook, paste the URL as the Target URL, then pick message types and accounts.
  3. Add a secret header so the Zap can reject anything that did not come from DataDoe.
  4. Filter on messageType, then notify.

Mind the volume. Each delivered message uses AI Tokens. Leave the high-volume types, such as every offer change, off unless you need them.

API keys are made in DataDoe under Integrations → REST API; see how to connect to the API. Webhook setup and payloads are in the DataDoe webhook docs.

• Amazon events

Which Amazon events should start a Zap?

DataDoe turns Amazon notifications into webhooks, and a Catch Hook turns each one into a Zap run. These are the message types we see earn their keep, with an honest note on volume.

DataDoe webhook message types and the Zaps they suit
Message typeFires whenA Zap worth buildingVolume
AMAZON_ORDER_UPDATEAn order is created or changes statusPost orders above a set value to a sales channel; add a row per order to a sheetSteady
AMAZON_LISTINGS_ITEM_STATUS_CHANGEA listing’s status changesMessage whoever owns the catalog, ASIN and SKU includedLow
AMAZON_LISTINGS_ITEM_ISSUES_CHANGEIssues on a listing appear or clearOpen a task in Asana, Trello or ClickUp with the issue textLow
AMAZON_FBA_INVENTORY_AVAILABILITY_CHANGESFBA availability movesUpdate a stock column so the purchasing sheet is never a day oldSteady
AMAZON_PRICING_HEALTHAn offer loses Featured Offer eligibility on priceAlert the pricing owner and log the ASINLow
AMAZON_ACCOUNT_STATUS_CHANGEDThe selling account’s status changesText and email the owner at once, whatever the hourRare
AMAZON_ANY_OFFER_CHANGEDAny offer on an item changesOnly with a tight Filter step; otherwise it floods the ZapHigh

Volume is our rough guide, not a quota. Some types are limited to Brand Registry or particular programs; the full list and payload shapes are in the webhook docs. If your Catch Hook ever fails to answer, DataDoe pauses the subscription and emails your organization.

• Zap blueprints

Six Zaps sellers ask us for, step by step.

The request we hear most in support is ready-made dashboards, and a report that turns up on its own is the closest a Zap gets. These blueprints cover that, plus the alerts nobody wants to discover a day late. Five only read; one changes bids, behind a sign-off.

Big orders to the sales channel

Every order above the value you set shows up in Slack with SKU, quantity and marketplace.

  1. Catch HookDataDoe sends AMAZON_ORDER_UPDATE
  2. Filter by Zapierline item value above $500
  3. SlackSend Channel Message

On Amazon: Nothing

Monday ad spend in the inbox

Last week’s spend and sales by campaign, as a CSV attached to one short email.

  1. Schedule by ZapierEvery Week, Monday 07:00
  2. Webhooks by ZapierGET the recurring export’s latest file
  3. GmailSend Email with attachment

On Amazon: Nothing

Listing issues become tasks

When Amazon flags a problem on a listing, someone gets a task with the details instead of a surprise.

  1. Catch HookAMAZON_LISTINGS_ITEM_ISSUES_CHANGE
  2. Formatter by Zapierpull ASIN, SKU and issue text
  3. Your task toolCreate Task in Asana, Trello or ClickUp

On Amazon: Nothing

Account status, any hour

If the selling account’s status changes, the owner hears about it by text as well as email.

  1. Catch HookAMAZON_ACCOUNT_STATUS_CHANGED
  2. SMS by Zapierto the owner’s verified number
  3. Email by Zapiercopy to the ops inbox

On Amazon: Nothing

Evening digest of changes

A plain list of every DataDoe Action from the day, so nobody has to open the Action log to know what moved.

  1. Schedule by ZapierEvery Day, 18:00
  2. MCP ClientRun Tool actions_list on DataDoe
  3. GmailSend Email

On Amazon: Nothing. It only reads the log

Bid cuts with a sign-off

Over-target keywords get a lower bid, checked as a dry run, then held until a person approves.

  1. Webhooks by ZapierPOST /actions with dryRun
  2. Human in the LoopRequest Approval
  3. Webhooks by ZapierPOST the same Actions live on Approve

On Amazon: Bid changes, only after Approve

• Changes, with a reviewer

A Zap may draft a change. A person sends it.

Nobody is watching when a Zap runs at nine in the morning, so it should never push a change to Amazon on its own. Writes in DataDoe start switched off per Action type, and the Amazon account must be set to read and write first. Then give the Zap a reviewer.

  1. 09:00 · DraftA scheduled Zap asks the DataDoe REST API to run 12 bid cuts with dryRun set. Payloads are validated; Amazon sees nothing.
  2. 09:01 · AskHuman in the Loop sends the list to a reviewer by email or Slack and pauses the Zap.
  3. On ApproveThe same Actions are sent live. On Decline, the Zap only logs the draft.
  4. AfterwardsThe DataDoe Action log shows each change, the request and Amazon’s answer.

Our advice: run new Zaps read-only for a few weeks, add the approval step, and only then switch on the single Action type the Zap needs.

• Before it runs every day

Six checks before the Zap goes live.

None of these is hard. All of them are cheaper to settle now than after the first busy week.

Premium apps

Webhooks by Zapier and Human in the Loop are premium apps. Check that your Zapier plan includes them before you build on them.

Zapier tasks

Each action step a Zap completes counts as a task on your Zapier plan. A filter early in the Zap keeps quiet events from using tasks up.

AI Tokens

Webhook deliveries and MCP calls are paid for in AI Tokens from your DataDoe plan. Subscribe only to the message types a Zap really uses.

Rate limits

DataDoe limits calls per organization. If a reply comes back as 429, wait and retry.

A secret header

Set one on the DataDoe webhook and check it in the Zap, so a stranger who finds the Catch Hook URL cannot trigger your workflow.

A webhook that answers

When the endpoint stops returning a 2xx, DataDoe pauses the subscription and emails your team. Resume it under Integrations → Webhooks.

• Elsewhere

One DataDoe login, many front doors.

Zaps are best at moving a known answer to the right person. To find the question in the first place, or to run the workflow on your own servers, start from one of these.

Prefer n8n? n8n MCP for AmazonSelf-hosted workflows with an AI AgentClaude with your Amazon numbersAsk first, automate laterAmazon data in ChatGPTChat with Seller Central and AdsMCP setup for any AI clientOne endpoint, whichever assistant you use
FAQ

Zapier and DataDoe, question by question.

Yes, through the MCP Client app, which Zapier labels beta. Add a connection with the server URL https://mcp.datadoe.com/mcp/v1, choose Streamable HTTP, set OAuth to Yes and sign in to DataDoe. DataDoe tools then appear in Zaps as the Run Tool action and the Run Read-Only Tool search.

No. Zapier MCP runs the other way: it lets an assistant such as Claude or ChatGPT use the apps connected to your Zapier account. MCP Client lets a Zap call a server outside Zapier. You can use both at once.

Usually not. A DataDoe recurring export builds the same table on a schedule, and Webhooks by Zapier can download the newest file using your datadoe-api-key header. DataDoe can also email the export without any Zap.

Create a Catch Hook in Zapier, then add its URL as the Target URL of a webhook in DataDoe under Integrations, Webhooks. Pick the message types and accounts, add a secret header, and DataDoe posts each event to the Zap as JSON.

Only through DataDoe Actions that you have switched on, on an Amazon account set to read and write. Put a dry run first, then a Human in the Loop approval, then the live request. DataDoe keeps a record of each Action and what it sent.

Anything in DataDoe: Seller Central, Vendor Central and Amazon Ads in 100+ tables, from orders and settlements to inventory, listings, Vendor retail analytics and campaign performance, with roughly 24 months of order history backfilled after you connect.

MCP Client is listed as a beta app. Webhooks by Zapier and Human in the Loop are premium apps, so the export and webhook routes need a plan that includes them. DataDoe bills on its own: $97 a month after a free 14-day trial.

DataDoe treats any non-2xx answer or failed delivery as an error, pauses that webhook subscription and emails your organization. Turn the Zap back on, then select Resume under Integrations, Webhooks.

Want a hand with the first Zap?

Every month you get a free 30-minute slot with the Deltologic team behind DataDoe. Bring the alert you keep checking for by hand.

Book a demo
• Get started

Let Amazon events start your Zaps.

Connect Seller Central, Vendor Central and Amazon Ads to DataDoe once, then route reports and alerts through Zapier with every change held for a reviewer.

Start your free trial Webhook docs
  • Webhooks, exports and MCP
  • Seller, Vendor and Ads
  • A reviewer before writes
  • $97 a month, 14 days free