Brevo sits at the intersection of email campaigns, SMS sends, transactional email, contact lists, and lifecycle automations, which makes it useful but also easy for the real story to get buried across campaign views and send logs. A Brevo AI assistant is most useful when it helps marketing, lifecycle, and ops teams compare email and SMS performance, monitor list health, inspect transactional sending, and turn send movement into clear Slack updates without living inside Brevo all day. If you are running OpenClaw yourself, Brevo is still a workable integration to wire up, but Cody is the faster path if you want the assistant experience instead of the API glue.
How OpenClaw Integrations Work
OpenClaw is a self-hosted AI assistant that runs on your own server — typically an EC2 instance — and connects to Slack. It uses Claude under the hood to process requests. Out of the box, OpenClaw doesn't ship with pre-built connections to third-party tools. Instead, integrations are built using the skills system: markdown files in ~/.openclaw/skills/ that give Claude instructions for a particular domain, combined with HTTP tool calls to any API you expose to it.
In practice, adding a real integration means: getting API credentials from the third-party service, building or configuring a small proxy/endpoint that OpenClaw can call, and writing a skill file that tells Claude how to use it. For some tools this is an afternoon of work. For others — like Brevo — it's considerably more involved.
Connecting OpenClaw with Brevo: Step by Step
Step 1: Get Your Brevo API Key
Log into Brevo and go to Account → SMTP & API → API Keys. Generate a key. The Brevo API v3 base URL is https://api.brevo.com/v3/ and uses the key as the api-key request header. The API is REST-based and well-documented.
Step 2: Explore the Key Endpoints
For campaign monitoring: /emailCampaigns and /smsCampaigns for marketing sends, /contacts and contact-list endpoints for audience health, and /smtp/statistics or related transactional endpoints for delivery visibility. Brevo keeps marketing and transactional activity within one API family, which makes it easier to build one assistant surface than with tools that split email products across separate systems.
Step 3: Build the Proxy and Skill File
Build your proxy around campaign stats and contact list endpoints. Write ~/.openclaw/skills/brevo.md with your list names and IDs, the campaign types you use (email vs SMS), and the KPIs your team tracks.
Challenges and Caveats
SMS and Email Stats Are in Different Endpoints
If you use both email and SMS campaigns, they live in different Brevo resource paths and have different KPIs. Your skill file needs to make clear whether the question is about email, SMS, contacts, or transactional sending so Claude does not mix those views together.
Rate Limits Vary by Plan
Brevo's API rate limits are tied to your plan tier. Free plans have strict limits; Starter and higher give more headroom. Check your plan's limit before building real-time queries.
Skip All of This — Use Cody Instead
Cody gives your team a Brevo AI assistant in Slack, so people can review email and SMS campaign results, spot list-health or deliverability issues, inspect transactional sending, and share lifecycle updates without wiring API keys or building reporting glue.
Related Guides
- Connecting OpenClaw with Mailchimp: A Practical Guide
- Connecting OpenClaw with Sendgrid: A Practical Guide
- Connecting OpenClaw with Instantly: A Practical Guide
Need the model-flexible version? See: How to Connect Brevo to OpenClaw: Setup, Models, and Workflow Guide.