# lemlist + Krokul CRM

Yes. Krokul CRM integrates with lemlist. A contact enters the lemlist campaign tied to a deal stage, a won deal pauses that person in every campaign, and lemlist replies, interest marks, bounces and unsubscribes come back to the Krokul contact as comments, tasks or a new deal. The path is the Krokul app in Zapier, Make, n8n or Albato, or the Krokul API with its webhooks.

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

## What your team gets

### A deal stage starts a lemlist campaign

In the lemlist card you link a deal stage to a lemlist campaign. When a deal moves into that stage, Krokul adds the deal contact to the campaign with the e-mail, first name and company, and stores the lemlist ID as an external key of the contact. A manager no longer copies addresses between tabs.

### A reply interrupts the outbox

The connector registers a lemlist webhook of the type `emailsReplied`, and `linkedinReplied` for LinkedIn steps. A reply becomes a comment on the Krokul contact and a task for the deal owner, so the conversation moves from automation to a person on the same day.

### An interested recipient opens a deal

When someone in a campaign is marked interested, lemlist sends `emailsInterested`. Krokul creates a deal in the funnel and source you chose, keyed by the lemlist activity, so a repeated webhook returns the same deal.

### A won deal pauses the campaign

Once a deal is won, Krokul pauses the contact in all lemlist campaigns. A new customer does not receive the next cold step a day after signing.

### Bounces and unsubscribes are visible on the contact

The webhook types `emailsBounced` and `emailsUnsubscribed` add a mark to the Krokul contact. For a bounce, Krokul also creates a task to check the e-mail address before anyone writes to it again.

## What moves between lemlist and Krokul

| lemlist | Krokul | Direction | When |
|---|---|---|---|
| Campaign (add a person) | Contact of a deal | Krokul → lemlist | The deal enters a stage linked to the campaign |
| Campaign (pause a person) | Won deal | Krokul → lemlist | The deal is won |
| Webhook `emailsReplied`, `linkedinReplied` | Comment and task on the contact | lemlist → Krokul | A reply arrives |
| Webhook `emailsInterested` | Deal | lemlist → Krokul | The recipient is marked interested |
| Webhook `emailsBounced` | Mark and task on the contact | lemlist → Krokul | An e-mail bounces |
| Webhook `emailsUnsubscribed` | Mark on the contact | lemlist → Krokul | The recipient unsubscribes |

## How to connect today

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

1. Sign in to the Krokul app on the platform with a Krokul API key.
2. Start from a Krokul trigger such as Deal Stage Changed and use the lemlist action that adds a person to a campaign.
3. For the other direction, start from the lemlist trigger New Activity or Unsubscribed Recipient and use the Krokul actions Find Contact, Add Comment or Create Task.

### Custom flow through the Krokul API and webhooks

1. Make a Krokul API key that can read deals and write contacts, tasks and activities.
2. Subscribe a Krokul webhook to card.statusChanged and card.won. Your receiver checks x-crm-signature, then adds the person to the lemlist campaign or pauses them.
3. Register lemlist hooks with POST /api/hooks that point at the same receiver, one type per hook.
4. On a reply or bounce, find the person with contact/api-find, write a comment with activity/api-create and keep the lemlist ID on the contact through externalRef/api-upsert.

**Triggers:** New Activity; Unsubscribed Recipient.

**Actions:** Add Lead to Campaign; Update Lead From Campaign; Remove Lead From Campaign; Pause Lead From All or Specific Campaigns; Add Recipient to Unsubscribe List; Find or Create Lead.

### For integrators

lemlist webhooks are registered with `POST https://api.lemlist.com/api/hooks`, one `type` per hook, up to 200 hooks per workspace, and a `secret` echoed in each callback. The lemlist API uses HTTP Basic auth with an empty user name and the API key as the password. On the Krokul side, idempotent keys on deal creation and external keys make every retry safe.

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

## Questions and answers

### Does Krokul integrate with lemlist?

Yes. Krokul integrates with lemlist through the Krokul app in Zapier, Make, n8n and Albato, and through its API and webhooks.

### Which lemlist events reach Krokul?

Replies by e-mail and LinkedIn, interested marks, bounces and unsubscribes. Each one lands on the contact as a comment, a mark, a task or a new deal.

### Will a repeated webhook create two deals?

No. Krokul keys the deal by the lemlist activity, and a repeated call with the same key returns the existing deal.

### Does a won customer keep getting cold e-mails?

No. When the deal is won, Krokul pauses the contact in all lemlist campaigns.

## Limits

lemlist writes and sends the campaign steps; Krokul decides who enters a campaign and records what happened after. The lemlist API allows 20 requests per 2 seconds per key, so Krokul spreads large enrollments over time.

## Related services

- [Mailchimp](https://krokul.com/en/integrations/mailchimp/index.md)
- [Brevo](https://krokul.com/en/integrations/brevo/index.md)
- [Apollo.io](https://krokul.com/en/integrations/apollo-io/index.md)
- [Clay](https://krokul.com/en/integrations/clay/index.md)

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

lemlist is a trademark of its owner. Krokul is not affiliated with lemlist.

Updated: 2026-10-12

---

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