Braze Connector
Connector status: Planned Not built yet. Tajo does not run this connector today.
Illustration · sample data
Sync example
Source
Braze
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 does not run a Braze connector today. Early code exists, but it has not been run against a live Braze account and syncs nothing yet.
What exists so far
- Exports users by external ID, and lists campaigns, segments and Canvases.
Planned, not built
- Two-way profile sync
- Campaign and Canvas engagement events
- Segments as contact lists
Open-Source Implementation Map
This section is derived from official or public repository material discovered for the Braze 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 |
|---|---|---|---|
| braze-community/braze-specification | 0b0856e | TypeScript (22), JSON (9), YAML (6), Markdown (3), github/codeowners (1), gitignore (1) | 47 |
Integration Shape
graph LR Source["Braze 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
- braze-specification
- Braze API specification:
-
- OpenAPI spec
-
- Postman collection
- See the original Postman collection.
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.