Add contacts to your Brevo lists with attributes. Connect your native Framer forms to Brevo (Sendinblue) in 30 seconds with zero client-side API key leaks.
Brevo, formerly Sendinblue, handles email and SMS marketing for many small teams, and most of its campaigns and automations start from a contact list. FramerSend turns each Framer form submission into a Brevo contact and adds it to the list whose ID you enter, so the person is ready for your next campaign or a welcome automation tied to that list.
The request runs in Brevo's update mode. A visitor who fills in the form again does not cause an error: the existing contact gets the new first name, last name and phone and is added to the list. Only those attributes are sent, which keeps the setup short, and the API key stays on FramerSend's server instead of in the published site.
What gets created: A Brevo contact, created or updated through POST /v3/contacts with updateEnabled set, and added to the list whose numeric ID you enter.
| Framer form field | Brevo (Sendinblue) |
|---|---|
| email (also Email, E-mail, courriel…) | Contact emailRequired. Spaces are trimmed and common domain typos such as gmail.co or outlook.con are corrected. |
| name or full_name | FIRSTNAMEThe first word of the name. A first name field, or one mapped to FIRSTNAME, is used directly. |
| Rest of the name, or a last name field | LASTNAME |
| phone, mobile, tel, whatsapp | SMSSent as typed, without reformatting. If Brevo rejects the number, its reason is shown on the failed row. |
| List ID on the connection | List membershipMust be a whole number. Anything else stops the submission with a clear error instead of saving the contact without a list. Leave it empty to add contacts without a list. |
| company, message and every other field | Not sentBrevo rejects attribute names that do not exist in your account, so only FIRSTNAME, LASTNAME and SMS are sent. The complete submission stays in Dashboard → 4. Logs. |
Create a v3 API key
In Brevo's API key settings, create a key just for FramerSend so you can revoke it on its own later. It starts with xkeysib-.
Find the list ID
Open your contact lists in Brevo, pick the list the form should feed and note its number. Enter the number only.
Check the contact attributes
FramerSend always writes to attributes called FIRSTNAME, LASTNAME and SMS. Confirm they exist under those names in your Brevo contact attributes.
Connect Brevo in the plugin or dashboard
Search for Brevo in the FramerSend plugin inside Framer, or use Dashboard → 2. Connect CRM. Paste the key and list ID and click Test. Test reads your Brevo account with the key, checks that the list ID is a number and that the list exists, and names the list on success.
Paste the webhook URL into Framer
In Framer, select the form, open Form → Send to → Add… → Webhook, paste the FramerSend webhook URL (https://www.framersend.com/api/submit/ followed by your form ID) and publish the site. Then submit once and open the list in Brevo to confirm the contact joined it.
Missing Brevo API Key
Cause: Shown by Test when the key field is empty.
Fix: Paste the v3 key.
Invalid Brevo API Key.
Cause: Shown by Test when Brevo refuses the key, for example because it was deleted or only partly copied.
Fix: Create a new v3 key and paste it whole.
Email is required
Cause: No field in the submission looked like an email address.
Fix: Add an email input to the form. It is a visitor input issue, so no failure alert email is sent.
Brevo: the List ID must be a number (got "…"). Find it in Brevo → Contacts → Lists, in the ID column.
Cause: The List ID on the connection contains something other than digits, such as #5 or the list name. Test shows the same message.
Fix: Enter the numeric list ID, save, and click Retry on the affected rows.
Brevo list … was not found. Check the List ID.
Cause: Shown by Test when the number is not a list in this Brevo account.
Fix: Copy the ID from your contact lists in Brevo.
Brevo (HTTP …): …
Cause: Brevo refused the contact and its reply follows. Typical reasons are a phone number Brevo will not accept for SMS, a list that has since been deleted, or a key that has been revoked.
Fix: Read the reply on the failed row in Dashboard → 4. Logs, fix the number format, list or key, then click Retry.
Contacts are saved but not added to a list
Cause: The List ID on the connection is empty, so FramerSend sends no list.
Fix: Enter the numeric list ID, save, and retry the affected rows if needed.
Create or update in one call. Zap setups often need a find step before create or update. FramerSend sends one request in Brevo's update mode, so new and returning visitors are both handled.
No tasks to count. Every Zapier action uses a task. FramerSend has no submission limit.
Phone goes to SMS. Phone answers go straight to Brevo's SMS attribute. If Brevo does not accept a number's format, the reason is logged on the submission.
When an automation platform fits better. Custom attributes such as company, several lists per signup, or Brevo's double opt-in flow need other API calls. FramerSend covers email, name, phone and one list.
Full comparison: FramerSend vs Zapier
Zero code or third-party plugins required
Authenticate Brevo (Sendinblue) credentials in the FramerSend dashboard. We encrypt and store them securely.
Map your Framer form fields to Brevo (Sendinblue) properties using our visual dropdown UI.
Paste your webhook URL into your Framer form under Send to → Webhook and publish. Submissions flow automatically.
Every plan includes Brevo (Sendinblue) and 100+ other connectors. Pay monthly, yearly, or once. Try it free for 14 days, no card needed.
For one Framer site
For freelancers and small studios
For agencies with many client sites
14-day free trial of every connector, no card needed. Form fields and FramerSend file uploads stay free forever with a free account.
Start freeEncrypted API vault, real-time delivery, and unlimited submissions
Capture leads from your Framer site and auto-add them to targeted email campaigns.
Convert visitors into subscribers with a seamless form-to-list flow.
Automatically enroll new customers into welcome sequences.
The request runs with update enabled, so the existing contact is updated with the new first name, last name and SMS values and added to the list.
No. It creates or updates the contact directly. Add a consent notice to the Framer form.
Not with this connector. It writes FIRSTNAME, LASTNAME and SMS only.
No. Each connection holds one list ID. Use separate forms and connections for separate lists, or an automation inside Brevo.
FramerSend sends the value as typed and Brevo decides whether it accepts it for SMS. Check Brevo's own guidance for the format your account expects; a refused number shows Brevo's reason in Logs.
Yes. Test confirms the API key, checks that the list ID is a number and reads the list, so a wrong ID is caught before the first submission.
They are not sent to Brevo by this connector. Every answer is stored with the submission in Dashboard → 4. Logs, so nothing the visitor typed is lost, and you can add those values to the contact by hand if needed.
Sign up for a FramerSend account (or log in). Go to Connections → Add Connection → Brevo (Sendinblue) and add your credentials. They are stored server-side and never exposed in your Framer site, which only gets a public form URL.
Yes, all API credentials are encrypted at rest. The client-side code in Framer only exposes a public Form ID, keeping your private keys entirely secure.
No. FramerSend provides unlimited form submissions across all license tiers so your live website forms never get blocked during high-traffic spikes.