EN
See the demo

SendPulse + Krokul CRM

Yes. Krokul CRM integrates with SendPulse. Contacts with an email address land in a SendPulse mailing list with variables for personalization, and unsubscribes, spam complaints and bounces come back to the contact card. A won or lost deal sends an event to Automation 360 and starts the right flow of emails, SMS or Viber messages.

  • Via API and webhooksYou connect it with the Krokul app in an automation platform, the public API and signed webhooks. The page lists the steps for this service.

Automation platformsZapierMakeAlbato

What your team gets

A new client goes straight into the right mailing list

When a contact with an email address appears in Krokul, Krokul adds it to a SendPulse mailing list with the /addressbooks/{id}/emails method. Name, company and phone go as variables, so the email greets the person by name. The list is picked by the pipeline the contact came from.

The manager sees an unsubscribe before writing

SendPulse sends an unsubscribe event with the address and the from_all flag when a person opts out of all mailings. Krokul finds the contact by email, marks the opt-out and writes a line to the feed. The manager sees it on the card.

Interest in an email becomes a sales signal

The open and redirect events say that the client opened the email and followed a link, and the link_url field names which one. Krokul writes them to the feed of the contact and the open deal. The manager notices a click on the pricing page or the proposal the same day.

A won deal starts an onboarding flow

The Krokul card.won event sends a POST to the address of an Automation 360 event with the client email and phone. SendPulse starts the flow for new clients, and automation_id names the exact one. A lost deal can start a separate win-back flow the same way.

An invalid address does not stay in the database

The hard_bounces event means the address does not accept mail. Krokul gives the contact manager a task to check it, and the corrected address returns to the same SendPulse list.

What moves between SendPulse and Krokul

SendPulseDirectionKrokulWhen
Mailing list, /addressbooks/{id}/emails with variablesKrokul → SendPulseContact with an email addressA contact is created or changed
unsubscribe event (email, book_id, from_all)SendPulse → KrokulMailing opt-out mark, line in the feedThe person unsubscribed
spam eventSendPulse → KrokulMailing opt-out markThe email was marked as spam
open and redirect events (link_url)SendPulse → KrokulLine in the contact feed and the deal feedThe email was opened, a link was clicked
hard_bounces eventSendPulse → KrokulTask to check the addressThe address does not accept email
Automation 360 event (email, phone, automation_id)Krokul → SendPulseDeal won or lostThe deal result changes
Unsubscribe, /addressbooks/{id}/emails/unsubscribeKrokul → SendPulseContact asks not to be emailedThe manager marked the opt-out on the card

How to connect today

Krokul app in Zapier, Make or Albato

  1. Connect the Krokul app with a Krokul API key, and SendPulse with the keys from the API tab of the account settings.
  2. Link the Krokul trigger New Contact to the SendPulse action Add Subscriber in Zapier or Create/Update a Contact in Make.
  3. Link the SendPulse trigger New Unsubscriber (Zapier) or User unsubscribed (Albato) to a Krokul contact search by email and a contact update action.
  4. For opens and clicks, take the Albato triggers Open email and Click on link, or Watch Events in Make, and add an activity in Krokul.

Custom flow through the Krokul API and webhooks

  1. Issue a Krokul API key with scopes for contacts, activities and tasks.
  2. In SendPulse, open the account settings, API tab, and create webhooks for the unsubscribe, spam, open, redirect and hard_bounces events with the address of your handler.
  3. The handler parses the event array, finds the person with contact/api-find, updates it with contact/api-update and logs a line with activity/api-create.
  4. Subscribe a Krokul webhook to contact.created and card.won, check x-crm-signature and call /addressbooks/{id}/emails or the Automation 360 event address.

Triggers

  • New Subscriber
  • New Unsubscriber
  • Updated Subscriber
  • Watch Events
  • User unsubscribed
  • Open email
  • Click on link
  • Marked as spam

Actions

  • Add Subscriber
  • Update Subscriber
  • Change Variable for Subscriber
  • Unsubscribe User
  • Create/Update a Contact

Questions and answers

Does Krokul work with SendPulse?

Yes. Krokul contacts reach SendPulse mailing lists, unsubscribes and email opens come back to the contact card, and deal events start Automation 360 flows.

How does Krokul learn about an unsubscribe in SendPulse?

From the unsubscribe webhook. It carries the email, the mailing list ID and the from_all flag, so Krokul can tell an opt-out from one list from an opt-out from all mailings.

Can a deal stage start a SendPulse flow?

Yes. A deal event in Krokul sends a POST to the Automation 360 event address with the client email or phone, and SendPulse starts the flow linked to that event.

Why does an email open not show up in Krokul instantly?

SendPulse sends campaign events in batches, once a minute or per hundred events. Krokul keeps the time of each event.

Limits

Email templates, campaigns, Automation 360 flows and campaign statistics live in SendPulse. SendPulse sends campaign events in batches once a minute or every hundred events, so they appear in Krokul with that delay.

Missing something?

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.

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

See the demo