brevo

brevo wraps the email marketing api for contacts, lists, transactional sends, campaigns, and templates, with plain endpoint tables an agent can follow. The dependency is explicit: the key is read from a file under the config directory and sent as an api-key header on every request. Nothing here is reversible in the ordinary sense. Deleting a contact and sending a campaign both push outward immediately, and the documented flow offers no staging step, so testing belongs against a small list first. It is a hosted service, so offline use is impossible and data residency follows the vendor.

Use case: syncing webinar signups to a list

This skill covers a transactional and marketing mail service. It manages contacts and lists, sends individual messages and campaigns, and reads saved templates, all through one http interface with a single key. ## What it does - Creates, reads, updates and deletes contacts. - Lists contacts with paging and filters, including suppressed addresses. - Groups contacts into lists and moves them in and out. - Sends transactional mail and full campaigns. - Reads saved templates. ## When it is the wrong choice It sends real mail. There is no dry run among the described endpoints, so a test against a live list reaches actual inboxes, and a campaign cannot be recalled once it has gone. The credential is a bare key sent in its own header rather than a bearer token kept in a file, which makes file permissions matter more than they would otherwise. Contact attributes are defined per account, so a payload built around one account's field names will not fit another without checking, and the example in the skill uses attribute names in a language the account happens to speak. The whole surface is a marketing tool rather than a mail server, so delivery behaviour belongs to the provider. Templates and campaigns are also separate surfaces with their own payload shapes, so a body built for one is not accepted by the other. ```bash curl -s "$brevo_base/contacts" -H "api-key: $brevo_key" ``` ## Working notes - The key travels in its own header rather than as a bearer token. - List reads support paging and a suppressed address filter. - Contact attributes are defined per account.