Connector Catalog

Find A Connector

No connector matches that. Clear the search or pick a different filter.

A tag reads live only when the connector is enabled in the Tajo runtime. Everything else is a research map: the surface tag describes what the vendor publishes, not what Tajo runs. Maps to Brevo means a typed contract records which fields become which Brevo objects.

Applies To Every Connector

These conventions hold for any connector Tajo builds, so they are recorded once here rather than repeated on all 176 pages.

Mapping into Brevo

• Map vendor IDs into stable Tajo external IDs before creating contacts, custom objects, events, or relationship records.
• Normalize emails, phone numbers, timestamps, currencies, locales, and consent fields before sending them to Brevo.
• Decide which records become Brevo contact attributes, which become custom events, and which should only remain in Tajo for operator context.
• Keep list, segment, campaign, and transactional-send names deterministic so backfills and retries do not create duplicate activation targets.
• Preserve the original vendor payload or a compact audit reference for troubleshooting field-level mapping issues.

Sync strategy

• Run historical backfills separately from incremental sync so operators can pause or replay each path independently.
• Prefer updated-at or cursor pagination. If only offset pagination is available, persist page size, ordering, and restart rules.
• Treat webhooks as near-real-time hints, then refetch canonical records from the vendor before writing to Tajo or Brevo.
• Deduplicate by vendor object ID, event ID, webhook delivery ID, or a deterministic hash when the vendor does not expose stable IDs.
• Capture rate-limit headers and retry-after values in connector telemetry, and make batch sizes configurable.

Error handling and operations

• Use idempotent writes for creates, updates, event ingestion, list membership changes, and Brevo activation calls.
• Separate authentication failures, permission failures, validation failures, rate limits, vendor outages, and Brevo mapping errors in logs.
• Send malformed or unmappable records to a dead-letter path with the source object ID, sync job ID, and operator-visible reason.
• Alert on repeated token refresh failures, webhook signature failures, cursor stalls, and sustained Brevo rejection rates.
• Include a runbook entry for credential rotation, webhook re-registration, backfill replay, and partial outage recovery.

Builder checklist

• Does the vendor have a verified authentication path for production workspaces?
• Are primary resources mapped to stable external IDs?
• Is historical backfill separated from real-time webhook ingestion?
• Are retries idempotent for creates, updates, sends, and event ingestion?
• Are Brevo contact attributes, custom events, and campaign triggers named consistently?
• Are failure modes visible enough for an operator to resolve without reading code?

Generated 2026-08-19 from connectors.v2.ts at 6f68e3f.