BusyBot

Reference · Credentials

Brevo credentials

Used by 2 BusyBot nodes.

Type brevoApi 1 field

The Brevo credential holds a v3 API key from your Brevo account (formerly Sendinblue), used by the Brevo node and its trigger for email, contacts and campaigns.

Fields

FieldTypeRequiredNotes
API Key
apiKey		 password Yes Your Brevo API key.

Getting your credentials

  1. Sign in to Brevo.
  2. Open the SMTP & API section of your account settings.
  3. Create a new API key (v3) and name it for where it will be used.
  4. Copy the key immediately and paste it into the credential’s API Key field.

Permissions and scopes

Brevo keys act on the account that issued them. If your plan supports restricting a key’s capabilities, grant only what the workflow needs.

Troubleshooting

  • 401 Unauthorized — the key is wrong, revoked, or is an older key format. Create a fresh v3 key.
  • Sender not allowed — the sending address or domain has not been verified in Brevo. Verify it there before sending.
  • Contacts not updating — confirm the list or attribute names match what exists in the account.

Frequently asked questions

Is Brevo the same as Sendinblue?

Yes — Brevo is the current name. Keys created under the old branding may still work, but create a current v3 key if authentication fails.

Why are my sends rejected even though the key works?

The sending address or domain must be verified in Brevo. Authentication and sender verification are separate checks.

Does one key cover both the node and the trigger?

Yes, both use the same credential type.

Nodes that use Brevo

One credential works across every node below — create it once and reuse it.

Last updated . Spotted something wrong? Tell us.