# eSputnik + Krokul CRM

Yes. Krokul CRM integrates with eSputnik. Krokul contacts reach eSputnik with their own ID and a segment picked by pipeline, a deal stage change sends an event that starts a workflow of emails, SMS or Viber messages, and unsubscribes, spam complaints, bounces and clicks come back to the contact card. The Krokul app in Zapier or Albato runs the link, and custom flows use the Krokul API and webhooks.

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

## What your team gets

### A contact reaches eSputnik under the same ID

When a contact with an email or phone appears in Krokul, Krokul sends it with the /api/v1/contact method and puts the contact UUID in externalCustomerId. eSputnik looks for duplicates by that ID first, so a repeated send updates the same person. The segment follows the pipeline the contact came from.

### A deal stage starts a workflow

The Krokul event card.statusChanged becomes a Generate event call with the eventTypeKey you mapped to the stage and the deal fields in params. The eSputnik workflow listening for that event sends the client an email, SMS or Viber message. A proposal stage gets its own reminder chain.

### A won deal becomes an order

After card.won, Krokul sends the deal to the Orders method as an order with the DELIVERED status, the total, the currency and the line items. The deal number goes into externalOrderId, so a later change overwrites the same order. A cancelled deal sends CANCELLED.

### Opt-outs and bounces show on the card

The eSputnik webhook brings activityStatus UNSUBSCRIBED or SPAM with the address and externalCustomerId. Krokul finds the contact and marks the mailing opt-out. UNDELIVERED with hardBounce means the address does not exist, and the contact manager gets a task to check it.

### A click in an email alerts the manager

The CLICKED status carries clickEventLink, the link the client followed. Krokul writes a line to the feed of the contact and the open deal. A workflow with a Webhook block can call Krokul directly and create a call task when the client opens the pricing page.

## What moves between eSputnik and Krokul

| eSputnik | Krokul | Direction | When |
|---|---|---|---|
| Contact (/api/v1/contact, externalCustomerId) | Contact with email or phone | Krokul → eSputnik | A contact is created or changed |
| Segment (groups) | Pipeline of the contact | Krokul → eSputnik | A contact is created |
| Generate event (eventTypeKey, params) | Deal stage | Krokul → eSputnik | A deal moves to a mapped stage |
| Order (Orders, externalOrderId) | Won or cancelled deal with line items | Krokul → eSputnik | A deal is won or cancelled |
| UNSUBSCRIBED, SPAM | Mailing opt-out mark | eSputnik → Krokul | The person unsubscribed or complained |
| UNDELIVERED with hardBounce | Task to check the address | eSputnik → Krokul | The address does not accept email |
| CLICKED (clickEventLink) | Line in the contact and deal feed | eSputnik → Krokul | The client followed a link |
| Webhook block in a workflow | Task for the manager | eSputnik → Krokul | The workflow reaches the block |

## How to connect today

### Krokul app in Zapier or Albato

1. Connect the Krokul app with a Krokul API key, and eSputnik with an API key from Settings, API in the eSputnik profile.
2. Link the Krokul trigger New Contact to the eSputnik action Add/Update Contact in Zapier or New contact in Albato.
3. Link the Krokul trigger Deal Stage Changed to the Zapier action Send Event, so a deal stage starts an eSputnik workflow.

### Custom flow through the Krokul API and webhooks

1. Issue a Krokul API key with scopes for contacts, deals, activities and tasks.
2. Subscribe a Krokul webhook to contact.created and card.statusChanged, check x-crm-signature, and call /api/v1/contact or Generate event with Basic authentication by the eSputnik key.
3. In eSputnik, open Data export, create a Webhook with the address of your handler and select UNSUBSCRIBED, SPAM, UNDELIVERED and CLICKED.
4. The handler parses the event array, finds the contact with externalRef/api-resolve or contact/api-find, updates it and logs a line with activity/api-create.

**Triggers:** New Contact; New Contact in Segment.

**Actions:** Add/Update Contact; Subscribe Contact; Send Event; Send Email; Send SMS; New contact; Subscribe contact.

### For integrators

The eSputnik REST API takes Basic authentication with the API key in the password field. The activity webhook posts a JSON array and can carry a receiver login and password and up to five custom headers. eSputnik documents no body signature. Generate event accepts a body of up to 20 KB, and a repeat with the same eventTypeKey and keyValue overwrites the parameters. On the Krokul side, the contact UUID sits in externalCustomerId, and Krokul webhooks are signed with HMAC and keep a delivery log.

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

## Questions and answers

### Does Krokul work with eSputnik?

Yes. Krokul integrates with eSputnik through the Krokul app in Zapier and Albato, and through its API and webhooks. Contacts, deal stages and orders go to eSputnik, and opt-outs, bounces and clicks come back to Krokul.

### How does a deal stage start an eSputnik workflow?

Krokul sends Generate event with the eventTypeKey mapped to the stage. The eSputnik workflow that starts on that event reads the deal fields from params and sends the message.

### How does Krokul learn about an unsubscribe in eSputnik?

From the activity webhook with the UNSUBSCRIBED status. It carries the address and externalCustomerId, so Krokul finds the exact contact.

### Does Krokul see old opens and clicks?

No. The eSputnik webhook sends events from the moment it is set up. eSputnik returns 90 days of history through a separate contact activity method that support turns on.

## Limits

Message templates, workflows, segments and campaign statistics live in eSputnik. eSputnik webhooks carry only activity that happens after they are set up, so older history stays out of Krokul.

## Related services

- [SendPulse](https://krokul.com/en/integrations/sendpulse/index.md)
- [Mailchimp](https://krokul.com/en/integrations/mailchimp/index.md)
- [Brevo](https://krokul.com/en/integrations/brevo/index.md)
- [ActiveCampaign](https://krokul.com/en/integrations/activecampaign/index.md)
- [TurboSMS](https://krokul.com/en/integrations/turbosms/index.md)
- [Viber](https://krokul.com/en/integrations/viber/index.md)

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

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

Updated: 2026-10-15

---

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