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 automation 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 the latest Instagram username, keyword and automation name.
  • An email, optionally: a transactional template of yours, filled with the link and the resource name of the automation.

Use it in an automation

Section titled “Use it in an automation”

In the automation editor, add an Action step and choose Add to a Brevo list. Put it after the step that collects the email: without an email in the conversation, the step does nothing.

  1. Pick the list

    The List menu shows the lists of the connected Brevo account, by name. The contact is added to it, or updated if already there. Without a list, the step only keeps the email in UseNadia (the editor says so).

  2. Send the email too, if you want

    Tick Also send the email with the resource, then pick one of your transactional templates in Email template. Brevo sends it right away, with these parameters: LINK (the automation’s {lien}), RESOURCE ({ressource}), KEYWORD (the word the person sent) and USERNAME (their Instagram username). Use them in the template as {{ params.LINK }}.

  3. Look before anyone receives it

    Preview email shows the template filled with the automation’s values (or example values where a post fills them). Send me a test makes Brevo send the real thing to your own address: the only exact rendering.

The diagram and the test then read list followed by the list name, and + email followed by the template name.

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. Without a Brevo connection, the editor shows Connect Brevo in Integrations instead of the menus.