---
title: "Custom API + Brevo Integration"
description: "Evaluate a custom source for Brevo. A connector definition is not a live connection; verify authorization, consent, preview, approval, and a controlled run."
url: https://tajo.io/docs/integrations/custom-api-brevo/
markdown: https://tajo.io/docs/integrations/custom-api-brevo.md
lang: en-US
---

# Custom API + Brevo Integration

## Custom API + Brevo

Tajo has source connector definitions and rule-building code, but a definition is not an authorized connection or a live sync. Check the source’s [integration guide](https://tajo.io/docs/integrations) for current evidence and consent requirements. The [HubSpot guide](https://tajo.io/docs/integrations/hubspot-brevo) illustrates a pilot implementation awaiting live verification. If your source is missing, [tell the team](https://tajo.io/contact) which system, API, and consent evidence the workflow needs.

## How a Sync Is Built

This implemented workflow applies only when the source connector and an authorized connection are available. Confirm the exact path with Tajo before relying on it:

1. Ask the **Brevo Integration Architect** for a specific source, destination, field map, and consent rule.
2. Review the proposed rule against the source schema and the consent evidence it can actually read.
3. Validate the map and request publish approval. The bounded preview reads at most 10 source records and writes nothing to Brevo.
4. A person approves the exact rule; only then can it be published. Verify a controlled live run and its failure handling separately.

## What a Sync Needs to Be Published

A rule that writes contacts or events to Brevo must carry Tajo’s consent filter. The source has to record marketing consent, and Tajo has to know how to read it. When it cannot, the rule is refused.

The HubSpot connector has a proposed consent mapping but no verified live production sync. Stripe, WooCommerce and BigCommerce have no verified publishable Tajo contact path here; this is a statement about Tajo’s current evidence, not whether those platforms can store consent. For any source, identify where marketing consent is recorded and ask for a live preview of the proposed rule before relying on it.

## Doing It Yourself

Brevo runs an official MCP server. Connect it to Claude and Claude can create and update contacts, lists and campaigns in your account. See [Brevo MCP Server](https://tajo.io/docs/mcp/brevo-mcp-server) for the token and the client setup.

Each Brevo module also has its own endpoint, such as `https://mcp.brevo.com/v1/brevo_contacts/mcp`. Connect only the modules your task needs. The token behind each still has full access to your account.

For the source side, look for an MCP server for your system in the [MCP Registry](https://registry.modelcontextprotocol.io/), or build one against the [MCP specification](https://modelcontextprotocol.io/). In that setup nothing checks consent for you. Send Brevo only people who agreed to marketing.

## Next Steps

- [Integration Layer Overview](https://tajo.io/docs/integrations), source status and verification checks
- [Shopify + Brevo](https://tajo.io/docs/integrations/shopify-brevo)
- [Brevo MCP Server](https://tajo.io/docs/mcp/brevo-mcp-server), Brevo’s modules and client setup