# Sendinblue (Brevo) integration

💳 **Paid plan required:** This integration is available only on **paid plans**.

### 🔑 Step 1: Find or Generate Sendinblue (Brevo) API Key (in Brevo)

Powerful Form connects to Brevo using an **API Key**.

**✅ Where to get your API key**

* Log in to your **Sendinblue** account
* Click on your profile name in the top-right corner and select **SMTP & API** > navigate to the **API Keys** tab
* If you don't have an API key yet, click **Create a New API Key** > copy the generated API key for use in the next step.

For detailed instructions, refer to Sendinblue's official guide: [Getting a Sendinblue API Key](https://help.debounce.io/kb/integrations/getting-a-sendinblue-api-key/)

***

### 🔌 Step 2: Add Brevo API Key to the app settings (in PowerfulForm)

Now paste your Brevo API key into PowerfulForm so the app can send contacts to Brevo.

✅ Steps

1\. Open the app > click **Settings > Third party integration** > hover **Sendinblue** > click **Congig**

2**.** Enter **Sendinblue API key** field created in the **Steps 1** above

3\. Click **Save** to update the changes

<figure><img src="/files/vF0LJuKDZbESAnNYUtWT" alt=""><figcaption></figcaption></figure>

***

### 🧩 Step 3: Connect form data to Brevo (in Form Builder)

This step decides:

* which **Brevo list** gets the contact
* how your **form fields** map to **Brevo contact fields**

**✅ Before you start**

Make sure you already created at least **one list** in Brevo (so you can choose it during setup). Follow this [link](https://help.sendinblue.com/hc/en-us/articles/208771609--BETA-Create-a-new-list-from-segmented-contacts) to know more.&#x20;

**✅ Mapping steps**

1\. Open the app > click **Forms** > open the form you want to deal with

2\. Click **Settings** > click **Integration icon** on the left side bar > enable **Sendinblue** > click on its name&#x20;

<figure><img src="/files/Bpo97LchueKzSssCyV5I" alt=""><figcaption></figcaption></figure>

3. Select the **Brevo List** you want to add subscribers to
4. Map fields

Select the value of the Globo form (on the right) to connect it to the fields in **Sendinblue** (on the left). For example:&#x20;

* 📧 **Email** ← your form’s Email field
* 👤 **Name / First name / Last name** ← your form’s name fields

<figure><img src="/files/OAjxKK2FaMd6wlAXCxTQ" alt=""><figcaption></figcaption></figure>

5\. Click **Save** to update the changes.&#x20;

***

### ✅ Test & Check Your Results (in Brevo)

* Submit the form once using a real email address
* Open **Brevo**
* Go to **Contacts**
* Open the **List** you selected
* Confirm the new contact is there

<figure><img src="/files/WXZLA6ZSnSU1GXW9fsey" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/sJ1CR07tuhuTSGdYoA69" alt=""><figcaption></figcaption></figure>

***

### 🛠️ Troubleshooting

#### 🔒 “Authentication failed” / “Invalid API key”

* Double-check you pasted the Brevo (Sendinblue) API key (not SMTP key, not a different token).
* Make sure there are no extra spaces before/after the key.
* If it still fails, create a new API key in Brevo and update it in Powerful Form. (Old keys may be revoked.)

#### 📭 Contacts are not being added to Brevo

* Confirm the integration is enabled on the correct form (you might be editing a different form).
* Make sure you clicked Save after mapping.
* Verify the form submission includes a valid email address.
* Check you selected the correct Brevo List in the integration settings.

#### 🧩 Some fields are empty in Brevo

Re-check your **field mapping**:

Example: mapping “Full name” into a “First name” field can look “empty” depending on how Brevo displays it.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.powerfulform.com/~/revisions/KRfi0fHdeAFeAhiPrH7G/app-integration/sendinblue-brevo-integration.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.