Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Brevo

Formerly Sendinblue, is a SaaS solution for relationship marketing

CategoryMarketing
Authenticationcustom
Version0.4.0
Published scopes0 published scopes
Last updatedSeptember 21, 2026

Overview

Connect Brevo with Flows360

Formerly Sendinblue, is a SaaS solution for relationship marketing

Use the Brevo connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 7 actions and 8 triggers.

Available actions

  • Create or Update Contact
  • Find Contact
  • Unsubscribe Contact
  • Send Transactional Email
  • Send Transactional SMS
  • Create Event
  • Custom API Call

Available triggers

  • Contact Added to List
  • Contact Updated
  • Contact Deleted
  • Contact Unsubscribed
  • Transactional Email Delivered
  • Transactional Email Opened
  • Plus 2 additional declared triggers.

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: Brevo
  • Package: @activepieces/piece-sendinblue@0.4.0
  • Exact artifact digest: sha256:29ea406e7b7648ea8e3e4f31f69acde67a75e5c4490f24f9ec4b3aa30fd580d7
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

SECRET TEXT. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Create or Update Contact (create_or_update_contact), Create or update an existing contact Classification: read.
  • Find Contact (find_contact), Check whether a contact exists in Brevo and fetch its details. Classification: read.
  • Unsubscribe Contact (unsubscribe_contact), Blacklist a contact so it stops receiving email or SMS. Classification: read.
  • Send Transactional Email (send_transactional_email), Send an email from your Brevo account with HTML or plain text content. Classification: read.
  • Send Transactional SMS (send_transactional_sms), Send a transactional SMS from your Brevo account. Classification: read.
  • Create Event (create_event), Track a custom event for a contact. Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

  • Contact Added to List, webhook.
  • Contact Updated, webhook.
  • Contact Deleted, webhook.
  • Contact Unsubscribed, webhook.
  • Transactional Email Delivered, webhook.
  • Transactional Email Opened, webhook.
  • Transactional Email Link Clicked, webhook.
  • Transactional Email Bounced, webhook.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Capability summary

Authenticationcustom
Supported objects15
Supported actionsNot published
Triggers8

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • Project API key Required · protected credential

Supported objects

ObjectReadWriteNotes
Create or Update Contact Yes No Create or update an existing contact
Find Contact Yes No Check whether a contact exists in Brevo and fetch its details.
Unsubscribe Contact Yes No Blacklist a contact so it stops receiving email or SMS.
Send Transactional Email Yes No Send an email from your Brevo account with HTML or plain text content.
Send Transactional SMS Yes No Send a transactional SMS from your Brevo account.
Create Event Yes No Track a custom event for a contact.
Custom API Call Yes No Make a custom API call to a specific endpoint
Contact Added to List Yes No webhook trigger declared by the pinned package.
Contact Updated Yes No webhook trigger declared by the pinned package.
Contact Deleted Yes No webhook trigger declared by the pinned package.
Contact Unsubscribed Yes No webhook trigger declared by the pinned package.
Transactional Email Delivered Yes No webhook trigger declared by the pinned package.
Transactional Email Opened Yes No webhook trigger declared by the pinned package.
Transactional Email Link Clicked Yes No webhook trigger declared by the pinned package.
Transactional Email Bounced Yes No webhook trigger declared by the pinned package.

Triggers

Contact Added to List · Webhook

Triggers when a contact is added to one of your lists.

Contact Updated · Webhook

Triggers when the attributes of a contact are updated.

Contact Deleted · Webhook

Triggers when a contact is deleted.

Contact Unsubscribed · Webhook

Triggers when a contact unsubscribes from a campaign.

Transactional Email Delivered · Webhook

Triggers when a transactional email is delivered to the recipient.

Transactional Email Opened · Webhook

Triggers when a recipient opens a transactional email.

Transactional Email Link Clicked · Webhook

Triggers when a recipient clicks a link in a transactional email.

Transactional Email Bounced · Webhook

Triggers when a transactional email hard or soft bounces.

Setup

Setup

  1. Add the Brevo connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • No provider credential fields are declared by the pinned package.
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-sendinblue@0.4.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 7 actions and 8 triggers declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required Brevo connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-sendinblue@0.4.0 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com