Zapier Connector
Connector implementation
Build the Zapier integration
Automation platform, MCP gateway, Platform CLI, and Brevo endpoint-manifest surface for building publishable integrations with triggers, searches, actions, and Zap templates.
Implementation Overview
Implement a Zapier connector that authenticates to the vendor surface, normalizes source records in Tajo, and activates eligible data in Brevo.
Treat this as an implementation guide. Build and validate the auth, mapping, sync, and operations paths before production use.
mcp.zapier.com
| Property | Value |
|---|---|
| Integration surface | MCP |
| Implementation status | Implementation required |
| Category | Automation & Integration Platform |
| Setup complexity | medium |
| Vendor documentation | docs.zapier.com/llms.txt |
| Allowed host | Not recorded |
| Base URL | Not recorded |
| OpenAPI schema | Not recorded |
| MCP server | mcp.zapier.com |
| Last researched | 2026-05-13 |
Zapier documents MCP server creation at mcp.zapier.com plus Platform CLI workflows via zapier-platform-cli. Tajo wires Zapier as a local planning/runtime surface and generates a Brevo API manifest from Brevo’s OpenAPI spec so every documented Brevo endpoint stays reachable.
Authentication
-
Validate the MCP server endpoint at mcp.zapier.com and document required headers, auth grants, and tool availability.
-
Keep docs.zapier.com/llms.txt linked from the connector runbook so operators can confirm vendor behavior during incidents.
-
Store credentials per Tajo workspace and keep tenant-specific secrets out of connector configuration files.
-
Add a credential smoke test that verifies read access to a harmless resource before running backfills or enabling webhooks.
Data To Sync
Start with these inferred data domains, then confirm exact vendor resources and permissions from the source documentation:
- Custom objects and operational metadata
The connector should make source records idempotent by keeping a stable key such as a vendor object ID, email address, event ID, ticket ID, order ID, or campaign ID. If the vendor only exposes list APIs, Tajo should store the cursor strategy and replay policy explicitly.
Sync Shape
No typed contract exists for Zapier, so the direction of each resource and its conflict handling are not recorded. Direction is declared per resource on a connector contract; see the connector catalog for how contracts are promoted.
Mapping To Tajo/Brevo
No Brevo projection is recorded for Zapier. A projection is declared on a typed connector contract, and Zapier does not have one yet, so this page will not state a mapping it cannot source.
The conventions that apply to every connector — stable external IDs, normalization, backfill and sync strategy, error handling, and the builder checklist — are documented once under “Applies to every connector” on the connector catalog.