# Brevo + Krokul CRM

Yes. Krokul CRM integrates with Brevo for contacts, lists and e-mail. Krokul contacts are kept on the Brevo lists you choose, and a won deal or a paid invoice sends a Brevo template e-mail. Delivery, unsubscribes and hard bounces come back to the person in Krokul through Brevo webhooks. The Krokul app in Zapier, Make, n8n and Albato builds these flows, and so do the Krokul API and webhooks.

**Status:** Via API and webhooks. **Automation platforms:** Zapier, Make, n8n, Albato.

## What your team gets

### Krokul contacts on a Brevo list

When someone is added in Krokul, the connector creates or updates the Brevo contact with the e-mail, name attributes and the list you mapped. The Krokul contact ID travels as `ext_id`, so both records point at each other and a renamed e-mail does not break the link.

### A won deal sends a welcome e-mail

In the Brevo card you link this event to a Brevo template. Krokul fills its `params` with the title, amount and manager name of the deal and sends it to the contact. Brevo answers with a `messageId`, and a comment on the deal shows which e-mail left and when.

### A paid invoice sends the receipt

Krokul marks an invoice paid once payments cover it in full. At that moment the connector sends the receipt template to the contact, and the transactional event `delivered` confirms delivery on the same deal.

### Unsubscribes and bounces land on the contact

The connector registers a Brevo marketing webhook for `unsubscribe` and `hard_bounce` and a transactional webhook for `hard_bounce` and `unsubscribed`. Each event puts a mark on the Krokul contact, and a bounce adds a task to fix the address.

## What moves between Brevo and Krokul

| Brevo | Krokul | Direction | When |
|---|---|---|---|
| Contact and list (`ext_id`) | Contact | Krokul → Brevo | A contact is created or changed |
| Transactional e-mail (template, `params`) | Won deal | Krokul → Brevo | A deal is won |
| Transactional e-mail (template, `params`) | Paid invoice | Krokul → Brevo | Payments cover the invoice |
| Transactional webhook `delivered` | Comment on the deal | Brevo → Krokul | Brevo delivers the e-mail |
| Marketing webhook `unsubscribe` | Mark on the contact | Brevo → Krokul | The contact unsubscribes from a campaign |
| Webhook `hard_bounce` | Mark and task on the contact | Brevo → Krokul | A campaign or transactional e-mail bounces |

## How to connect today

### Krokul app in Zapier, Make, n8n or Albato

1. Connect the Krokul app with a Krokul API key and the Brevo app with a Brevo API key.
2. Use a Krokul trigger such as Contact Created or Invoice Paid with the Brevo action Contact Create or Update or Send Transactional Email.
3. For the other direction, start from Contact Unsubscribed or Transactional Email Hard Bounced and use the Krokul actions Find Contact and Add Comment.

### Custom flow through the Krokul API and webhooks

1. Create a Krokul API key with scopes for contacts, deals and activities.
2. Subscribe a webhook to contact.created, card.won and invoice.paid. Validate the x-crm-signature header with your secret before you call Brevo.
3. Create or update the Brevo contact with the Krokul contact ID as `ext_id`, or send the template e-mail with values from the deal in `params`.
4. Register Brevo webhooks for `unsubscribe` and `hard_bounce`, find the person with contact/api-find, and leave a note on the contact through activity/api-create.

**Triggers:** Contact Added; Contact Updated; Contact Subscribed to Specific List(s); Contact Unsubscribed; Marketing Email Hard Bounced; Transactional Email Delivered; Transactional Email Hard Bounced.

**Actions:** Contact Create or Update; Search Contact; Unsubscribe Contact; Send Transactional Email; Send Transactional SMS.

### For integrators

Brevo event names differ between products. Marketing webhooks use `unsubscribe`, `hard_bounce` and `list_addition`, and transactional ones use `request`, `delivered`, `hard_bounce` and `unsubscribed`. The Brevo API takes the `api-key` header at `https://api.brevo.com/v3`. On the Krokul side, `invoice.paid` fires once per full payment, and the delivery log with replay covers a step that failed.

[API documentation](https://app.krokul.com/api/v1/docs)

## Questions and answers

### Does Krokul integrate with Brevo?

Yes. Krokul integrates with Brevo through the Krokul app in Zapier, Make, n8n and Albato, and through its API and webhooks. Contacts, lists, transactional e-mail and Brevo events are all covered.

### Can Krokul send Brevo transactional e-mails?

Yes. You link a Krokul event, such as a won deal or a paid invoice, to a Brevo template, and Krokul fills the template parameters from the deal.

### How does a Brevo unsubscribe show up in Krokul?

Brevo sends the webhook event, and Krokul marks the contact. The manager sees the mark on the card before writing to the person.

### Which side owns the templates?

Brevo. Templates and their design live in Brevo, and Krokul passes only the template ID and the values for its parameters.

## Limits

Templates, campaigns and sending domains are set up in Brevo. Krokul decides who receives which template and when, and keeps the result on the deal and the contact.

## Related services

- [Mailchimp](https://krokul.com/en/integrations/mailchimp/index.md)
- [lemlist](https://krokul.com/en/integrations/lemlist/index.md)
- [Apollo.io](https://krokul.com/en/integrations/apollo-io/index.md)
- [Typeform](https://krokul.com/en/integrations/typeform/index.md)
- [Twilio](https://krokul.com/en/integrations/twilio/index.md)

[Email marketing](https://krokul.com/en/integrations/category/email-marketing/index.md)

Brevo is a trademark of Sendinblue SAS. Krokul is not affiliated with Brevo.

Updated: 2026-10-12

---

App: https://app.krokul.com/ · API: https://app.krokul.com/api/v1/docs