Brevo

Email and calendar

Brevo for AI agents. Managed auth, ready-made tools.

Send transactional emails, manage contacts and lists, and review campaigns in Brevo on behalf of each of your users.

About Brevo

With the Brevo connector, your agent works in each user’s own Brevo account. It can send a transactional email, look up or add a contact, add contacts to a list and review email campaigns and their results, using only the tools your project allows.

Brevo is an email, SMS and marketing automation platform, formerly Sendinblue.

Tools

What your agent can do in Brevo.

Each tool is a capability the model can call. You decide which ones a project allows, and every call runs with the end user's own Brevo connection.

  • Send an email

    Write
    brevo_send_email

    Send a transactional email to one or more recipients.

  • Get a contact

    Read
    brevo_get_contact

    Get a contact's details and attributes by email.

  • List contacts

    Read
    brevo_list_contacts

    List contacts, with optional filters.

  • Create a contact

    Write
    brevo_create_contact

    Add a contact with attributes and lists.

  • Add to a list

    Write
    brevo_add_contacts_to_list

    Add existing contacts to a contact list.

  • List lists

    Read
    brevo_list_contact_lists

    List the account's contact lists.

  • List campaigns

    Read
    brevo_list_email_campaigns

    List email campaigns with their status and statistics.

Control

Limits you can set.

You decide what your agent may do in Brevo, and Agent200 runs every call within those limits.

  • Turn single tools on or off

    Let the agent read contacts and campaigns, and switch off brevo_send_email so it can never send an email.

  • Restrict what the agent reaches

    Choose the endpoints and scopes a project may use, for example contacts and lists but not sending email. A call outside them is refused.

Get started

Connect Brevo
in three steps.

  1. 1

    Set up the SDK

    Add the Agent200 SDK to the codebase you already have and authenticate with your API key. The key covers every connector enabled for the project.

    agent.js
    Conceptual example
    Set up the SDK with the Agent200 API key
    // One Agent200 API key covers every connector enabled for the project.
    const agent200 = new Agent200({
      apiKey: process.env.AGENT200_API_KEY,
    });
  2. 2

    Let your user connect Brevo

    Each end user authorizes their own Brevo account once. Agent200 runs the OAuth flow, handles the callback, stores the tokens and refreshes them.

    connect.js
    Conceptual example
    Let an end user connect their account (managed OAuth)
    // Each end user authorizes their own Brevo account, once.
    const connection = await agent200
      .user("user_123")
      .connect("brevo");
    
    if (connection.authorizationUrl) {
      // Show this link to your user; Agent200 handles the rest.
      console.log(connection.authorizationUrl);
    }
  3. 3

    Run with the Brevo tools

    Name the user, the model and the tools. The model decides which Brevo tools to call, and Agent200 executes them with that user's connection.

    run.js
    Conceptual example
    Run a request with the connector's tools
    const result = await agent200
      .user("user_123")
      .run({
        model: "openai/gpt-5.6-sol",
        input: "Add jo@fernway.com to my newsletter list in Brevo",
        tools: ["brevo"],
      });
    
    console.log(result.output);

Access

Sign-in and permissions.

  • Who signs in

    Each of your users, once, by connecting their own Brevo account. Each connection is their own.

  • What access is requested

    The connection acts with that user's access in Brevo, such as managing contacts, sending transactional emails or reading campaigns. Users can revoke it later from their Brevo account settings.

For agents

Instructions for AI agents.

Using a coding agent? Paste this brief into it, or give it the address of this page. It describes the Brevo connector and how to use it.

Agent brief
Connector: Brevo, through Agent200. In code: "brevo".
What it does: Send transactional emails, manage contacts and lists, and review campaigns in Brevo on behalf of each of your users.
Page: https://www.agent200.com/connectors/brevo/

1. Get an Agent200 API key. If the developer has none, send them to https://agent200.com/platform/apikeys/ and ask them to choose "Create an API key". Read the key from the AGENT200_API_KEY environment variable. Never ask for it in chat, and never write it into code, prompts or logs.
2. Sign-in is managed OAuth. Each end user approves access once, on Brevo's own page, through the authorization link Agent200 returns. Never ask a user for a Brevo password or token in chat.
3. Give every request a stable id for the end user. Agent200 uses only that user's own connection.
4. Read tools: brevo_get_contact, brevo_list_contacts, brevo_list_contact_lists, brevo_list_email_campaigns. Write tools: brevo_send_email, brevo_create_contact, brevo_add_contacts_to_list. Name "brevo" in the tools of a request; the model decides which tool to call.
5. Stay within the project's settings. If a tool is turned off or a call is refused, tell the user. Do not work around it.
6. Before a write, confirm with the user, unless they asked for that exact change.
7. For setup with a specific framework, follow its guide:
   https://www.agent200.com/connectors/brevo/framework/claude/
   https://www.agent200.com/connectors/brevo/framework/chatgpt/
   https://www.agent200.com/connectors/brevo/framework/claude-code/
   https://www.agent200.com/connectors/brevo/framework/muse/
   https://www.agent200.com/connectors/brevo/framework/grok-bot/
   https://www.agent200.com/connectors/brevo/framework/openai-dots/
   https://www.agent200.com/connectors/brevo/framework/claude-duet/
   https://www.agent200.com/connectors/brevo/framework/hermes-agent/
   https://www.agent200.com/connectors/brevo/framework/openclaw/

The code on the connector page is a conceptual example of the SDK. SDK reference: https://docs.igpt.ai/

This page is also available as Markdown, for agents and LLMs: /connectors/brevo.md

Guides

Use Brevo with the AI you build on.

Step-by-step setup for Brevo with a specific model, assistant or agent framework.

FAQ

Brevo and Agent200, answered.

Who handles the Brevo OAuth flow and the tokens?

Agent200. It runs the authorization, handles the callback on its own domain, stores the tokens and refreshes them. You do not build or maintain an OAuth integration for Brevo.

Does my agent act as the end user?

Within what that user authorized, yes. Every request names an end user, and Agent200 uses only that user's Brevo connection, never another user's. It cannot reach anything the user or Brevo has not authorized.

Can I limit what my agent can do in Brevo?

Yes. You choose which services, endpoints and authorization scopes are allowed in your Agent200 configuration, and the agent works only within them.

  • Gmail

    Gmail

    Read, search, draft and send email from each user's own Gmail account.

    Managed OAuth Email and calendar
  • Outlook

    Outlook

    Work with mail and calendar in each user's Microsoft Outlook account.

    Managed OAuth Email and calendar
  • Google Calendar

    Google Calendar

    Check availability and create, update or cancel events in your users' calendars.

    Managed OAuth Email and calendar
  • Calendly

    Calendly

    Find open times, share booking links, and book, review or cancel meetings in Calendly on behalf of each of your users.

    Managed OAuth Email and calendar
200 OK

Start with Brevo.
Your agent does the rest.

Your users connect their own Brevo accounts. Agent200 handles the OAuth, the tokens and every tool call.

Book a demo.
See it in action.

Tell us who you are, then pick a time for a 1:1 session with an expert from our team.

We use your details only to email you about Agent200. See the Privacy Policy.

Pick a time. We'll take it from there.

A 1:1 session with an expert from our team, about what you are building.

Open in Calendly (opens in a new tab)