---
title: "Zapier Connector | Tajo"
description: "Tajo does not run a Zapier connector today. Early code exists; this page lists what it does and what is planned."
url: https://tajo.io/docs/connectors/custom/zapier/
markdown: https://tajo.io/docs/connectors/custom/zapier.md
lang: en-US
author: "Set Noa"
author_url: https://tajo.io/set-noa/
robots: noindex
---

# Zapier Connector

[Set Noa](https://tajo.io/set-noa/)

Connector status: Planned Not built yet. Tajo does not run this connector today.

| Source field | Destination field | Sample value |
| --- | --- | --- |
| `record.id` | `source_id` | `record_1042` |
| `record.updated_at` | `updated_at` | `2026-10-18T08:00:00Z` |
| `record.value` | `value` | `sample_value` |

Tajo does not run a Zapier connector today. Early code exists, but it has not been run against a live Zapier account and syncs nothing yet.

## What exists so far

- Drafts Zapier integration plans, release checklists and Zap templates, and lists Brevo API endpoints for a Zapier app. It moves no data.

## Planned, not built

- Contacts and events from apps connected to Zapier
- Webhook triggers

## Open-Source Implementation Map

No official open-source repository was found in the current Tajo connector catalog for Zapier. Keep this page focused on the verified public API contract and vendor documentation until an official schema, SDK, MCP server, or public integration repository is available.

### Tajo Revamp Checklist

- Verify authentication and scope requirements against the vendor documentation before each connector release.
- Document primary sync objects, external IDs, pagination strategy, and rate limits explicitly.
- Add smoke tests from public API examples rather than undocumented behavior.
- Capture webhook signature verification and replay protection when the vendor supports webhooks.
- Record gaps where no official public repository or schema exists so future maintainers know what still needs source-backed validation.