Sending WordPress contact form entries to Brevo

Two Brevo rules that break integrations

• Authorised IPs. Brevo can restrict API keys to a list of IP addresses. If that's on and your host's address isn't listed — or your host changes it — every call is refused.
• Unused keys. Brevo deactivates an API key that hasn't been used for 90 days. A form on a quiet site can lose its connection without anyone touching it.

Both look the same from WordPress: Brevo answers “unauthorised”. Neither announces itself to the site owner.

How Formsafe Pro sends to Brevo

With the paid add-on Formsafe Pro, you paste an API key from your own Brevo account, choose the list for each form and which form fields fill Brevo's FIRSTNAME and LASTNAME attributes. Contacts are created or updated by email address. When Brevo refuses the key, Pro marks the connection as failing, keeps the entries, and emails you — and the alert mentions Authorised IPs, the likeliest cause. Once you fix it, the kept entries are sent.

An address Brevo rejects as invalid is a permanent answer: it isn't retried, and the reason is shown on the entry.

Coming from Contact Form 7's Brevo integration

Contact Form 7 has a built-in Brevo integration. When you import CF7 forms into the free Formsafe Contact Form, the import report tells you which forms were sending contacts to a Brevo list. The free plugin saves every entry; Formsafe Pro is what sends them on to Brevo, so nothing changes for your list after the switch. See switching from CF7.

Formsafe Pro isn't on sale yet; the pricing page says what it will cost.