Shopify + Brevo Integration
Illustration · sample data
Sync example
Source
Shopify
Connector status: In progress
Destination
Brevo
Connector status: Live
Field mapping
| Source field | Destination field | Sample value |
|---|---|---|
customer.email | email | [email protected] |
customer.first_name | FIRSTNAME | Alex |
customer.id | SHOPIFY_ID | 1042 |
- 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.
Shopify + Brevo
Tajo has a pilot Shopify connector, app code and proposed Brevo sync templates. Offline tests cover parts of this path, but a fresh store installation, live webhook delivery and production sync have not been verified by this review. The UI, template and MCP steps below describe implemented design requiring live verification, not features assumed available in every workspace. If your store connection is authorized and the consent path passes, two implemented components can move data:
- The Tajo Shopify app contains webhook handlers for customers, orders, checkouts, products, collections and stock. Confirm delivery and destination writes in a controlled live test before relying on immediate updates.
- Sync rules can map selected Shopify records to Brevo in batches. The proposed rule, consent filter, preview and approval must be verified against the authorized store before publishing.
The Shopify integration guide lists every webhook and what it writes to Brevo.
Building a Sync
When the Shopify connector and authorized store binding are available, the rule builder can follow this path. Verify the preview and a controlled live run before treating it as an operational sync.
- In Tajo, open Agents and ask the Brevo Integration Architect, for example: “Send Shopify customers who accepted email marketing to Brevo as contacts.”
- The agent inspects the Shopify connector. It sees field names and types, never customer values.
- It proposes a rule: the Shopify resource, the Brevo action, a field map and a filter. It validates the field map and dry-runs the draft, then saves it.
- Request publish approval runs a preview. It reads at most 10 records from your store, writes nothing to Brevo and records counts only.
- A person approves the exact rule on the Approvals page. Then the rule can be published.
Two templates are defined in code. If exposed in your authorized workspace, find them under Connections > Syncs and mappings > New sync from template:
| Template | What it does |
|---|---|
| Shopify customers -> Brevo contacts | Maps email, first and last name, phone, total spent, order count, the email opt-in, tags, the Shopify ID and the created and updated dates into Brevo contact attributes. Only customers subscribed to email marketing, and not suppressed, are sent. |
| Shopify orders → Brevo orders | Records orders in Brevo for revenue reporting, for buyers who accepted marketing at checkout. It adds nobody to a list. |
The configured runtime schedules contact sync rules every 15 minutes by default. An active, published orders rule uses the same interval while retaining the buyer marketing opt-in filter. Its first scheduled window sends no older orders; later windows use the saved cursor. Past orders need an explicit run, such as Test run (1 batch). Editing a rule returns it to draft for preview and approval. These are configured behaviors, not proof of a live store run: verify timing, cursor recovery and actual Brevo writes in your authorized store.
Shopify and Brevo over MCP
Tajo defines Shopify and Brevo MCP routes for compatible hosts. Verify authenticated host access and the current tool set in your workspace before relying on them:
claude mcp add --transport http tajo-shopify https://alto.tajo.io/mcp/connectors/shopifyclaude mcp add --transport http tajo-brevo https://alto.tajo.io/mcp/connectors/brevoWhen enabled, the host opens Tajo sign-in for early-access accounts. Check read results and approval behavior in your own workspace; tool exposure does not prove a durable Shopify-to-Brevo sync. The Shopify integration guide describes the proposed tools.
Doing It Yourself
Without Tajo, you can connect Brevo’s own MCP server to Claude and work with your Brevo account directly. See Brevo MCP Server. Shopify’s Dev MCP server searches Shopify’s API docs and schemas. It does not read your store’s data.
Next Steps
- Shopify integration guide, configured webhooks, rules and MCP tools
- Shopify permissions explained, every scope and every write
- Understanding data sync, how sync rules behave
- HubSpot + Brevo