Build automations that connect Brevo with Fluent Forms. When something happens in Brevo, Nodest passes the data along and runs the actions you set up in Fluent Forms or the other way around — no coding required.
Pick a ready-made workflow that connects Brevo with Fluent Forms, customise it to fit your needs, and go live in minutes.
When “Payment refunded” fires in Fluent Forms, Nodest will send a transactional email in Brevo.
When “Subscription cancelled” fires in Fluent Forms, Nodest will send a transactional email in Brevo.
When “Form submitted” fires in Fluent Forms, Nodest will send a transactional email in Brevo.
When “Partial submission saved” fires in Fluent Forms, Nodest will send an sms in Brevo.
When “Partial submission saved” fires in Fluent Forms, Nodest will send a transactional email in Brevo.
When “Form submitted” fires in Fluent Forms, Nodest will send prompt in Gemini and send a transactional email in Brevo.
When “Form submitted” fires in Fluent Forms, Nodest will send a prompt in OpenAI and send a transactional email in Brevo.
When “Contact unsubscribed” fires in Brevo, Nodest will update entry status in Fluent Forms.
When “Marketing email clicked” fires in Brevo, Nodest will add a note to an entry in Fluent Forms.
When “Payment status changed” fires in Fluent Forms, Nodest will update a contact in Brevo.
When “Form submitted” fires in Fluent Forms, Nodest will create a deal in Brevo.
When “Subscription cancelled” fires in Fluent Forms, Nodest will create a task in Brevo.
When “Subscription cancelled” fires in Fluent Forms, Nodest will send a transactional email in Brevo.
When “Payment refunded” fires in Fluent Forms, Nodest will send a transactional email in Brevo.
When “Form submitted” fires in Fluent Forms, Nodest will send a double opt-in in Brevo.
When “Form submitted” fires in Fluent Forms, Nodest will add a contact to a list in Brevo.
When “Form submitted” fires in Fluent Forms, Nodest will create a contact in Brevo.
Combine the triggers and actions of Brevo and Fluent Forms to build your automation. Triggers start the automation, and actions are the steps that follow.
TriggerFires when a marketing email is marked as spam.
TriggerFires when a marketing email soft bounces.
TriggerFires when a link in a marketing email is clicked.
TriggerFires when a transactional email is marked as spam.
TriggerFires when a transactional email is blocked.
TriggerFires when a transactional email soft bounces.
TriggerFires when a transactional email hard bounces.
TriggerFires when a link in a transactional email is clicked.
TriggerFires when a transactional email is opened.
TriggerFires when a transactional email is sent.
TriggerFires when a contact is deleted.
TriggerFires when a contact unsubscribes.
TriggerFires when a contact is added to a list.
TriggerFires when a marketing email hard bounces.
TriggerFires when a marketing email is opened.
TriggerFires when a transactional email is delivered.
TriggerFires when a marketing email is sent.
TriggerFires when a marketing email is delivered.
ActionUpdate an existing contact in Brevo.
ActionUpdate an existing deal in the Brevo CRM.
ActionCreate a company in the Brevo CRM.
ActionCreate a deal in the Brevo CRM.
ActionPermanently delete a deal from the Brevo CRM.
ActionAttach a contact to an existing deal.
ActionSend an SMS to a single recipient.
ActionSales pipelines in your Brevo CRM.
ActionVerified senders in your Brevo account.
ActionPermanently delete a contact from Brevo.
ActionTask types configured in your Brevo CRM.
ActionAdd a note to a contact, deal, or company.
ActionEditable custom attributes for Brevo companies.
ActionAdd an existing contact to a list in Brevo.
ActionSend a double opt-in email to a contact.
ActionCreate a contact in your Brevo account.
ActionRemove an existing contact from a Brevo list.
ActionSend a one-off email to a single recipient.
ActionCreate a CRM task in Brevo.
ActionUpdate an existing company in the Brevo CRM.
ActionMarketing lists in your Brevo account.
ActionPipeline stages in your Brevo CRM.
ActionEditable custom attributes for Brevo deals.
ActionEmail templates in your Brevo account.
ActionEditable custom attributes for Brevo contacts.
TriggerFires when a payment in Fluent Forms is refunded.
TriggerFires when the payment status of a Fluent Forms entry changes.
TriggerFires when a subscription in Fluent Forms is renewed.
TriggerFires when a step of a Fluent Forms form is saved.
TriggerFires when a subscription in Fluent Forms is cancelled.
TriggerFires when a note is added to a Fluent Forms entry.
TriggerFires when the status of a Fluent Forms entry changes.
TriggerFires when a Fluent Forms entry is permanently deleted.
TriggerFires when a Fluent Forms entry is submitted.
ActionFluent Forms available on the connected site.
ActionLook up a Fluent Forms entry.
ActionChange the status of a Fluent Forms entry.
ActionAdd a note to a Fluent Forms entry.
Create automations that move data between Brevo and Fluent Forms. Nodest handles the work in between, so you can focus on what matters.
Link your Brevo and Fluent Forms accounts to Nodest in a few clicks, so both tools are ready to use in automations.
Choose the event that starts your automation, such as a new order, form submission, or updated record in Brevo or Fluent Forms.
Add one or more actions, and combine them with filters, branches, and delays to create a workflow that fits your needs.
Find answers to common questions about connecting Brevo with Fluent Forms using Nodest.
In Brevo, open the account menu and go to Settings → SMTP & API → API Keys & MCP, then generate a new key. In Nodest, open Integrations, choose Connect Brevo, and paste the key. Brevo shows a key only at the moment you create it, so copy it before you leave that page.
Learn how to take control of your time with automation tips and productivity insights - weekly to your inbox.
