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.
Automation platformsZapierAlbato
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.
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.
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.
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.
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.
| eSputnik | Direction | Krokul | When |
|---|---|---|---|
| Contact (/api/v1/contact, externalCustomerId) | Krokul → eSputnik | Contact with email or phone | A contact is created or changed |
| Segment (groups) | Krokul → eSputnik | Pipeline of the contact | A contact is created |
| Generate event (eventTypeKey, params) | Krokul → eSputnik | Deal stage | A deal moves to a mapped stage |
| Order (Orders, externalOrderId) | Krokul → eSputnik | Won or cancelled deal with line items | A deal is won or cancelled |
| UNSUBSCRIBED, SPAM | eSputnik → Krokul | Mailing opt-out mark | The person unsubscribed or complained |
| UNDELIVERED with hardBounce | eSputnik → Krokul | Task to check the address | The address does not accept email |
| CLICKED (clickEventLink) | eSputnik → Krokul | Line in the contact and deal feed | The client followed a link |
| Webhook block in a workflow | eSputnik → Krokul | Task for the manager | The workflow reaches the block |
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.
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.
From the activity webhook with the UNSUBSCRIBED status. It carries the address and externalCustomerId, so Krokul finds the exact contact.
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.
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.
Tell us which service you use and what should move between it and Krokul. We reply with the way to do it and when it will be ready.
Request received. We reply to your email.
eSputnik is a trademark of its owner. Krokul is not affiliated with eSputnik.