Brevo - Atako

Let your agents manage contacts, lists, send transactional emails, create and manage email campaigns, and list senders via the Brevo API.

Connection

Authentication: API key.

Log in at brevo.com → SMTP & API → API Keys tab → Generate a new API key. Name it, choose the desired access level (at minimum “Access to Contacts” for contact management, plus “Transactional Email” for sending emails), and copy the key. The key is only shown once.See Brevo’s documentation.

Read actions (9)

Action	Description
`get_account`	Get account details (email, name, company, plan, credits).
`get_campaign`	Get an email campaign by ID, including content, recipients, and statistics.
`get_contact`	Get a contact by email, phone, numeric ID, ext_id, whatsapp, or landline_number. Optional query param identifierType: “email_id”, “phone_id”, “contact_id”, “ext_id”, “whatsapp_id”, “landline_number_id” (defaults to auto-detect from identifier format).
`get_list`	Get a list by ID, including name, folder, and subscriber counts.
`list_campaigns`	List email campaigns. Optional filters: type (“classic” or “trigger”), status (“draft”, “sent”, “queued”, etc.), statistics (“globalStats”), limit (default 50), offset, sort (“asc” or “desc”).
`list_contacts`	List contacts with pagination (default 50, max 1000). Optional filters: limit (1–1000), offset, sort (“asc” or “desc”), segmentId, listIds (array of integers), createdSince, modifiedSince (ISO 8601). Either listIds or segmentId, not both.
`list_folders`	List contact folders (their ids are required by create_list). Optional: limit (default 10, max 50), offset, sort (“asc” or “desc”).
`list_lists`	List all contact lists. Optional: limit (default 10), offset, sort (“asc” or “desc”).
`list_senders`	List all email senders. Optional: domain (string) to filter by domain.

Write actions (8)

Action	Description
`add_contacts_to_list`	Add existing contacts to a list. Pass exactly one of: emails (array of email strings), ids (array of numeric contact IDs), or extIds (array of external IDs string).
`create_campaign`	Create an email campaign draft. Required: name (string). Sender: sender object with email or id + optional name (only one of email or id). Content: exactly one of htmlContent (string, min 10 chars), htmlUrl (string, remote URL), or templateId (long). Also: subject (string, mandatory when abTesting is false), replyTo (string), scheduledAt (ISO 8601), recipients ({listIds?, segmentIds?, exclusionListIds?, exclusionSegmentIds?}).
`create_contact`	Create a new contact. Exactly one of email, SMS attribute in attributes, or ext_id is required. Attributes map uses uppercase keys (e.g. {“FNAME”:“John”,“LNAME”:“Doe”}). Optional: listIds (array of long), updateEnabled (boolean, default false to fail on duplicate), emailBlacklisted, smsBlacklisted.
`create_list`	Create a contact list. Required: folderId (numeric id of the parent folder, from list_folders), name (string).
`remove_contacts_from_list`	Remove contacts from a list. Pass exactly one of: emails (array of email strings), ids (array of numeric contact IDs), extIds (array of external IDs string), or all (boolean true to remove all).
`send_email`	Send a transactional email. Required when no templateId: sender (object: email string + optional name string), subject (string), to (array of {email, name?}). Required: htmlContent (string) or textContent (string) or templateId (long integer). Optional: cc, bcc (arrays of {email, name?}), replyTo ({email, name?}), scheduledAt (ISO 8601), attachment (array of {url?, content? base64, name?}).
`send_test_email`	Send a test email for an email campaign. Required: emailTo (array of email strings). Optional: language (“en”, “fr”, “de”, “es”, “it”, “pt-BR”, “nl”, “pl”, “sv”, “da”, “tr”, “ja”, “ko”).
`update_contact`	Update a contact by email (URL-encoded), numeric ID, or ext_id. Pass identifierType query param as “email_id”, “contact_id”, or “ext_id” when identifier is ambiguous. Body: attributes (uppercase keys), emailBlacklisted, smsBlacklisted, listIds, unlinkListIds, smtpBlacklistSender, ext_id.

Permissions

Every action above must be explicitly granted to an agent before it can be used. See Permissions for the grant model and Security for how credentials are protected.