Skip to main content

Brevo

Send transactional email and SMS and manage contacts in Brevo.

Connect it with: API key. Brevo's own documentation: https://developers.brevo.com/docs/getting-started.

What agents can do​

Connect Brevo so the agents working your tasks can reach it. With it connected, they can:

  • Send a transactional email, from a Brevo template or with its own HTML.
  • Add, update or tag contacts and manage lists.
  • Send a transactional SMS.
  • Read delivery events and campaign statistics.

Before you start​

  • A Brevo account.
  • A sender address or domain verified under Brevo > Senders, Domains & Dedicated IPs, so mail is delivered.
  • A Jaah account. Anyone can add a personal secret; an organization secret needs an Org Owner or Admin.

Connect with Brevo​

Jaah connects to Brevo with an API key, not with a sign-in button.

Connect with an API key​

Find each value first:

  • API key: Brevo > your profile menu (top right) > SMTP & API > API keys tab > Generate a new API key. Name it, then copy the key, which starts with xkeysib- and is shown only once.

Then add it to Jaah:

  1. In Jaah, open Secrets, select New, and pick the Brevo card.
  2. Name the secret and choose who can use it.
  3. Fill in API key.
  4. Select Save. Jaah tests the secret straight away (see Test the connection).

Jaah encrypts what you type and never shows it again — not to you, and not to an admin.

Use your own OAuth app​

Not used: Jaah connects to Brevo with an API key, not through an OAuth app.

Test the connection​

Select Test on the secret. Jaah calls Brevo's API once (GET https://api.brevo.com/v3/account) with the stored values, and shows who it answered as, or which value Brevo refused and the status it answered. Jaah also tests automatically when you save or reconnect.

The last result and its time stay on the secret's page, so you can see whether it still works without testing again.

Who can use it​

Every secret has an owner, and the owner decides who can use it:

  • Personal — only your own tasks can use it. This is the default.
  • Organization — every task in the organization can use it. Only Org Owners and Admins can choose this.
  • Attached to a project — every task on that project can use it, whoever started the task. See Attach a secret to a project.

More on owners and access: How secrets work.

Use it in an agent session​

An agent asks for the secret with its credential_get tool, by the secret's path, when it needs it, and gets the values for that one call. The path is the owner's prefix and the secret's name:

  • org/<name> for an organization secret,
  • projects/<project>/<name> for one attached to a project,
  • me/<name> for your personal one.

A key connection hands the agent its fields: api_key.

Tell the agent in your task description which secret to use, for example “use the Brevo secret org/brevo”.

Manage, rotate or disconnect​

Everything is on the secret's page under Secrets:

  • Rotate a key: create a new key at the vendor first, then select Replace on the secret and paste it. Revoke the old key at Brevo once the test passes. Steps: Replace or delete a secret.
  • Disconnect: select Delete. The stored values are destroyed and agents lose access on their next call. To end access at Brevo's side too, revoke or delete the key at Brevo.

Limitations​

  • The API key reaches the whole Brevo account; Brevo has no per-key scopes.
  • If Brevo's API key IP restriction is on (Security > Authorised IPs), calls from Jaah's agents are refused until their addresses are allowed or the restriction is turned off.
  • Sending counts against the account's plan limits.
  • Agents can do only what the connected Brevo account allows.

Troubleshooting​

Test says Brevo rejected the API key (401)

Use an API key from the API keys tab, not the SMTP key (an SMTP key starts with xsmtpsib- and works only for SMTP). Generate a new API key and select Replace on the secret.

Calls fail with unrecognised IP address

Brevo blocks keys used from unknown IP addresses. Open Security > Authorised IPs and allow the address in Brevo's email, or deactivate the blocking.

Emails are accepted but land in spam

Authenticate the sending domain with the DKIM and DMARC records Brevo shows under Senders, Domains & Dedicated IPs > Domains.

Still stuck? Select Test and read the result: it names the value Brevo refused and the status it answered.

FAQ​

Is this the same as Sendinblue?

Yes. Sendinblue was renamed Brevo; keys created before the rename keep working.

Can Jaah or an admin see the key or token?

No. Jaah stores it encrypted and never shows it again. Only the tasks allowed to use the secret receive it, at the moment they ask for it.

Can I connect more than one Brevo account?

Yes. Add one secret per account, each with its own name, and tell the agent which one to use.