---
title: "Integration Layer"
description: "Explore proposed Tajo source paths into Brevo. Check connector availability, consent requirements, and a live preview before planning a sync."
url: https://tajo.io/docs/integrations/
markdown: https://tajo.io/docs/integrations.md
lang: en-US
---

# Integration Layer

Tajo has an integration builder that can draft a field map and sync rule for a source connector. A usable sync also needs an available connector, an authorized source connection, a valid consent path, and a verified execution route. The guides below describe proposed mappings and current evidence; a guide or connector definition alone does not prove that a live sync is available in your workspace.

## How It Works

*How an integration is built*

Where the connector and authorized connection are available, the implemented rule workflow is:

1. **Describe** the desired source, fields, and consent rule to the Brevo Integration Architect agent.
2. **Review** its proposed field map and rule against the source’s actual data and consent evidence.
3. **Request a preview** of at most 10 source records. The preview writes nothing to Brevo.
4. **Approve** the exact rule before publishing. Then verify a controlled live run separately.

## Source status

| Source | Sync into Brevo | Why |
| --- | --- | --- |
| **Shopify** | Pilot connector and proposed customer/order mappings; live installation and production sync unverified | Verify store authorization, consent fields, and a controlled live run. The separate [Brevo PushOwl route](https://tajo.io/blog/brevo-shopify-integration/) has its own setup. |
| **HubSpot** | Pilot implementation; self-serve connection and live production sync unverified | Marketing subscription and opt-out checks need live verification |
| **Webflow** | Pilot connector and proposed form-to-contact mapping; live installation and production sync unverified | Verify the form’s opt-in evidence and a controlled live run. |
| **Stripe** | No publishable Tajo contact sync verified | Tajo needs a verified marketing-consent path for the selected source records. |
| **WooCommerce** | No publishable Tajo contact sync verified | Tajo needs a verified marketing-consent path for the selected source records. |
| **BigCommerce** | No publishable Tajo contact sync verified | Tajo needs a verified marketing-consent path for the selected source records. |
| **Salesforce Commerce Cloud** | No publishable Tajo contact sync verified | Tajo needs a verified mapping and marketing-consent path. |

## Integration Guides

### [Shopify + Brevo](https://tajo.io/docs/integrations/shopify-brevo)

Proposed customer and order mappings, consent checks, and the live installation still to verify.

### [HubSpot + Brevo](https://tajo.io/docs/integrations/hubspot-brevo)

Proposed contact mapping and consent checks; live connection and production sync remain unverified.

### [Stripe + Brevo](https://tajo.io/docs/integrations/stripe-brevo)

What Tajo reads from Stripe, and why a Stripe sync into Brevo cannot be published today.

### [Webflow + Brevo](https://tajo.io/docs/integrations/webflow-brevo)

Proposed form-to-contact mapping and the opt-in and live connection checks still required.

### [Salesforce Commerce Cloud + Brevo](https://tajo.io/docs/integrations/salesforce-commerce-brevo)

What Tajo reads from SFCC, and what a sync into Brevo still needs.

### [BigCommerce + Brevo](https://tajo.io/docs/integrations/bigcommerce-brevo)

What Tajo reads from BigCommerce, and why a customer sync into Brevo cannot be published yet.

### [WooCommerce + Brevo](https://tajo.io/docs/integrations/woocommerce-brevo)

What Tajo reads from WooCommerce, and why a customer sync into Brevo cannot be published today.

### [Custom API + Brevo](https://tajo.io/docs/integrations/custom-api-brevo)

Another system: check for a Tajo connector, what a sync needs to be published, and how to wire it yourself.

## Doing It Yourself

The guides also describe separate MCP or API routes. The [Brevo MCP Server](https://tajo.io/docs/mcp/brevo-mcp-server) can help with direct account tasks, but using provider tools does not create a durable Tajo sync or enforce this builder’s consent filter. Verify consent before sending contacts to Brevo.

## Next Steps

- [Shopify + Brevo](https://tajo.io/docs/integrations/shopify-brevo), proposed mapping and verification checks
- [Shopify integration guide](https://tajo.io/docs/ecommerce-platforms/shopify/), setup details to verify against a live store
- [Brevo MCP Server Setup](https://tajo.io/docs/mcp/brevo-mcp-server), a separate direct-tool route