Skip to content
usenadiadocs

Brevo

Where: Integrations in the sidebar

When a comment → DM automation asks someone for their email in a DM, UseNadia keeps the address. Connecting your own Brevo account lets the Forward the email step also write it to Brevo: the contact goes into one of your lists and, if you want, receives a transactional email with the resource. Brevo serves both purposes, which is what its card says: Add to a list · Transactional email.

Get a v3 API key in Brevo

Section titled “Get a v3 API key in Brevo”

  1. Open SMTP & API

    In Brevo, open the menu under your account name (top right), then SMTP & API.

  2. Open the API keys tab

    Not the SMTP tab: UseNadia needs an API key, which starts with xkeysib-. An SMTP key (xsmtpsib-) is refused.

  3. Generate a new key

    Name it after what uses it (for example UseNadia) so you can revoke this one alone later. Brevo shows the key once: copy it now.

Connect it in UseNadia

Section titled “Connect it in UseNadia”

  1. Open Integrations

    The Brevo card shows a single field, API key.

  2. Paste the key and click Connect

    UseNadia checks the key against your Brevo account before saving it. A wrong or revoked key is refused on the spot and nothing is stored.

  3. Check the account name

    The card now reads Connected: followed by your company name in Brevo (or your own name when the account has none). That is the account your automations will write to.

The key is stored encrypted and is never shown again. Disconnect removes it; connecting again with a key from the same Brevo account picks up where you left off. One Brevo account per organization.

What UseNadia writes to Brevo

Section titled “What UseNadia writes to Brevo”

Once an automation uses the connection:

  • The contact, created or updated in the list you pick. Nothing already on the contact is erased: a person who answers two of your automations stays one contact with both touches.
  • Attributes: SOURCE (the first channel, written once), SOURCES and KEYWORDS (appended, never rewritten), REQUESTS (a counter), and IG_USERNAME, IG_ID, KEYWORD and RULE (the latest Instagram username, their id, the latest keyword and the latest automation’s name). To see them on the contact’s record, create these attributes among the contact attributes of your Brevo account.
  • An email, optionally: a transactional template of yours, filled with the link and the resource name of the automation.

Prepare the list and the template in Brevo

Section titled “Prepare the list and the template in Brevo”
  • A contact list: it is the destination the step offers in its List menu. One list per resource, or a single one for everything: your call.
  • A transactional template, if you want to send the resource by email. It carries its own sender, subject and text: UseNadia adds nothing to it. Only active templates are offered. UseNadia fills it with these parameters:
Parameter Value In the template
LINK the automation’s {lien} {{ params.LINK }}
RESOURCE the {ressource} {{ params.RESOURCE }}
KEYWORD the word the person sent {{ params.KEYWORD }}
USERNAME their Instagram username {{ params.USERNAME }}

Use it in an automation

Section titled “Use it in an automation”

Add an Action step, Forward the email, after the one that collects the email. If Brevo is your only connected tool, the step picks it for you; then choose the List and, if you want, tick And send them an email and pick the Email template. Preview email and Send me a test show the template before anyone receives it. The step in detail: Forward the email.

Brevo has no preview rendering: the preview fills the parameters above and leaves visible the placeholders Brevo fills at send time (conditions, contact fields). The test is the real email.

Brevo is best effort: if Brevo refuses or is down, the email stays in UseNadia, the person still gets their link in the DM, and the run notes the error (brevo: …).