Connect Tajo to Shopify - Complete Setup Guide

Tajo connects your Shopify store to Brevo by drafting the integration for you, then waiting for you to review and approve it before anything runs. This guide walks through the full lifecycle: connect both accounts, review the draft, approve it, and let the governed sync take over.

Quick check Tajo is in early access. You need Shopify admin access, a Brevo account, and Owner or Admin access in Tajo. Nothing is published or sent until a person on your team approves it, so plan for a short review step — this is by design, not a delay to work around.

How the Setup Works

Setup is not a single “connect” button. It follows five stages:

Connect your Shopify store and Brevo account.
Draft: Tajo drafts the integration — which records move, how fields map, and what gets filtered out.
Review: you inspect the draft and the preview evidence built for it.
Approve: a person on your team approves the publication with a written rationale.
Run: the approved sync runs on a schedule (or on demand), with every run logged.

Expect the connection steps to take a few minutes each and the review to take as long as you want to spend on it. Data starts moving after approval, not before.

Step 1: Connect Your Shopify Store

In Tajo, open Connectors.
Choose Shopify and authorize access to your store. You will be sent to Shopify to grant permission and returned to Tajo.
Tajo requests read access to customers and orders. See Shopify permissions explained for what each permission is used for.
Once connected, Shopify appears on the Connectors page with its connection status.

Step 2: Connect Your Brevo Account

Still in Connectors, connect Brevo using your Brevo API key. See Brevo API key setup for how to create one with the right scopes.
Once connected, Brevo appears alongside Shopify with its status.

Both connections must be healthy before a sync can be drafted against them.

Step 3: Let Tajo Draft the Integration

Open Connectors > Syncs and create a new sync.
Pick a template for your source — for example, Shopify customers into Brevo contacts. Instantiating a template copies a full field mapping into a draft sync rule you can edit.
Open the draft. You can see and change:
- Field mapping — each source field, the Brevo field it writes to, and any transform applied.
- Filter expression — evaluated per record; records that do not match are skipped.

A draft does nothing on its own. No data moves while a rule is in draft.

Step 4: Request Publish Approval

On the sync rule page, choose Request publish approval.
Tajo builds a preview of what the rule would do, with supporting evidence, and creates an approval request.
The request appears in Approvals, where anyone on your team with the right access can pick it up.

The approval is bound to the exact version of the rule you submitted. If the rule is edited after approval, the approval is invalidated and you must request a new one — an approved “yes” can never be reused for a different configuration.

Step 5: Review and Approve

Open the request from the Approvals page.
Review the rule’s configuration and the preview evidence. Sample data shown for review is redacted — reviewers see the shape of what will be written, not raw personal data.
Approve or reject. Publication approvals require a short written rationale, and they cannot be batch-approved — each one is an individual decision that is recorded.

Every decision, including who made it and why, lands in the audit trail.

Step 6: Publish and Let the Sync Run

Back on the sync rule, choose Publish approved version. The rule becomes active.
The sync now runs on a schedule, or on demand when you trigger a run yourself.
On the rule’s page you can watch:
- Run history — each run with records read, written, and failed, plus duration.
- Cursor — where incremental syncing has progressed to, so runs pick up where the last one left off.

What to expect from sync timing

Tajo syncs in scheduled, governed batches — it is not real-time. A change in Shopify lands in Brevo on the next scheduled run, not within seconds. If you need data moved now, trigger a run manually from the sync rule page.

Safety rails that stay on

Consent fails closed. A rule cannot publish without a consent policy, and records without provable consent are not written. When in doubt, Tajo refuses rather than over-sends.
Budgets are capped. Spend limits are enforced; work stops rather than overrunning a budget.
Failures pause the rule. If several consecutive runs fail, a circuit breaker pauses the rule automatically and shows the last error. Fix the underlying issue, then re-publish to resume.
Everything is audited. Connections, approvals, publications, and runs all leave audit records.

Verify It Worked

Check the sync rule’s Run history — the latest run should show a healthy written count.
In Brevo, open Contacts and confirm your Shopify customers appear with mapped attributes.
If contacts are missing, see contacts missing in Brevo and data not syncing.

Common Questions

Can Tajo publish the integration without a human? No. Publication always requires a human approval with a rationale, and the approval is tied to the exact configuration reviewed. Only narrowly scoped, explicitly flagged routine actions can ever be auto-approved, and only if your workspace also opts in.

Is data synced back to Shopify? No. Sync runs one direction: from your source into Brevo.

Is there a free trial? Tajo is in early access and there is no self-serve free tier. Contact the team to get set up.

Does the review step slow things down? It adds one deliberate human decision before data moves. After that first approval, the sync runs unattended on its schedule until you change the rule — which requires a fresh approval.

Can I disconnect later? Yes. See disconnect or reconnect. Data already written to Brevo stays in Brevo.

Get Help

Live Chat: available in the Tajo dashboard (bottom right)
Email Support: [email protected]
Documentation: docs.tajo.io