Meta Ads Connector
Connector status: Planned Not built yet. Tajo does not run this connector today.
Illustration · sample data
Sync example
Source
Meta Ads
Connector status: Planned
Destination
Your other tool
Connector status: Custom tool
Field mapping
| 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 |
- Draft
- Review one record
- Approve this version
Statuses describe individual connectors; they do not guarantee this sync is ready. Illustrative fields. Review the actual schema and permissions before a sync runs.
Tajo has no Meta Ads connector yet. No code for it exists, so nothing on this page runs today.
Planned, not built
- Contact lists as Custom Audiences
- Conversion events through the Conversions API
- Lead form submissions as contacts
Open-Source Implementation Map
This section is derived from official or public repository material discovered for the Meta Ads connector. Use it as the engineering companion to the setup guide above: it shows where the API surface lives, what implementation assets exist, and how Tajo should translate them into reliable Brevo sync behavior.
Repository Snapshot
| Repository | Commit | Languages / formats | Files |
|---|---|---|---|
| facebook/openapi | 4003386 | Markdown (3), license (1), YAML (1) | 5 |
Integration Shape
graph LR Source["Meta Ads API / repository"] --> Auth["Auth and scopes"] Source --> Objects["Objects, events, and schemas"] Auth --> Tajo["Tajo connector runtime"] Objects --> Tajo Tajo --> Brevo["Brevo contacts, attributes, lists, campaigns"] Tajo --> Ops["Backfill, cursor, retries, logs"]What To Reuse
- Meta OpenAPI Specifications
- Overview
- Composition
- The repository currently contains specifications for:
-
- Business Messaging - WhatsApp API OpenAPI Specification. Visit developer documentation for WhatsApp Business API here.
Tajo Revamp Checklist
- Keep authentication setup aligned with the vendor docs and the public repository’s current API shape.
- Map primary resources into explicit Tajo sync objects with stable external IDs.
- Prefer cursor-based or updated-at incremental sync where the API exposes it; otherwise document the fallback.
- Treat webhook handlers as idempotent and replay-safe, especially for order, contact, ticket, and campaign events.
- Capture pagination, rate limits, retry headers, and partial-failure behavior in connector smoke tests.
- Keep examples small and runnable against sandbox or test-mode accounts.