Skip to content
Tejobit

Marketing

Brevo integration

Transactional email, SMS and marketing lists in Brevo, driven by events from the shop, the CRM and the back-office.

Request this integration See all integrations

Overview

Brevo

Brevo, formerly Sendinblue, combines email marketing, transactional email, SMS and WhatsApp in one account, with contacts, lists, attributes and automations. Many small companies pick it for volume-based pricing and a straightforward transactional API.

Tejobit uses Brevo in two roles. For transactional messages, the connection calls the API with Brevo templates when something happens in the client's system: order shipped, invoice ready, booking confirmed. For marketing, it keeps contacts and attributes current from WooCommerce or HubSpot. Brevo webhooks (delivered, opened, click, bounce, unsubscribe) go back to the source system for the record.

Use cases

What it is for

  • A WooCommerce shop sending the shipping email with tracking code from a Brevo template.
  • A service company emailing the invoice PDF as soon as the document is issued.
  • A clinic confirming bookings by Brevo SMS and falling back to Twilio for international numbers.
  • A HubSpot user running newsletters on Brevo that needs customer attributes in sync.
  • A back-office logging whether each email was delivered, opened or bounced.
IN

What the connection listens to

  • Source system events: order paid or shipped, document issued, booking created.
  • Brevo transactional webhooks: delivered, opened, click, hardBounce, softBounce, unsubscribed.
  • Contact changes in HubSpot or WooCommerce.
OUT

What the connection does

  • Sends transactional email through the API with Brevo templates and parameters.
  • Sends transactional SMS triggered by back-office events.
  • Creates and updates contacts, lists and attributes for marketing.
  • Stores each message's delivery status in the source system.

How it works

From the request to a working connection

  1. 01

    Request

    The form names the integration, the tools involved and what should happen in each case.

  2. 02

    Review and proposal

    Tejobit confirms what the API allows and sends a proposal with the flow, the price and the timeline.

  3. 03

    Setup and testing

    The connection is set up with the business's own accounts and tested with real cases before it goes live.

  4. 04

    Maintenance and monitoring

    Tejobit hosts the connection, follows up on errors and adapts it when the API changes.

The connection runs on Tejobit's infrastructure. The monthly fee covers hosting, monitoring and API changes.

What to prepare

  • A Brevo account with an API key and an authenticated sending domain (SPF, DKIM, DMARC).
  • Transactional templates in Brevo with the agreed variables.
  • A registered SMS sender and SMS credits, if texts are sent.
  • Access to WooCommerce, HubSpot or whichever system emits the events.

For security, do not send passwords, API keys or tokens through the form. Credentials are requested through a secure channel when the setup starts.

Limits

  • Sending volume and API rate limits depend on the Brevo plan.
  • Without an authenticated domain, transactional email is more likely to land in spam.
  • SMS is billed in credits, and alphanumeric sender names depend on the destination country.

Frequently asked questions

Before you start

Can Brevo be used for transactional email only?

Yes. Plenty of companies use Brevo purely as the back-office sending service, with no marketing campaigns.

Why is Twilio listed next to Brevo?

Brevo sends SMS, but for some cases (international numbers, voice, verification) Twilio fits better. The connection picks the channel by rule.

Can staff still edit the templates?

Yes. Templates live in Brevo and are edited there; the connection only supplies the variables.

Related integrations

See all integrations

Set up the Brevo integration?

Describe what should pass between the tools. The reply confirms feasibility, price and timeline.

Talk about your project geral@tejobit.com