Yes. Krokul CRM integrates with Mailgun. A won deal, a new document or a paid invoice sends a Mailgun template e-mail to the contact, and Mailgun webhooks report deliveries, opens, clicks, failures, complaints and unsubscribes back to the same deal. Client replies arrive through a Mailgun route and appear as comments on the deal. The link runs through the Krokul app in Zapier, Make and n8n or through the Krokul API and webhooks.
Automation platformsZapierMaken8n
You map a Krokul event to a Mailgun template, for example a paid invoice to a receipt. Krokul calls the Messages API with the template name, fills t:variables with the deal title, amount and document number, and adds the deal UUID as the v:deal_uuid parameter. The deal feed records which template went out and to which address.
Mailgun posts a webhook for delivered, opened and clicked events, and each one carries the user-variables of the original message. Krokul reads the deal UUID from them and adds the event to the deal. The manager sees the opened offer before the follow-up call.
A permanent_fail event tells Krokul that the address cannot receive mail. Krokul marks the contact with the reason from the event and opens a task to check the address. Complained and unsubscribed events mark the contact too, and later event rules skip it.
A route with match_recipient on your reply address forwards each incoming message to Krokul. The forward carries the sender, the subject, stripped-text without the quoted history and the message-headers. Krokul finds the contact by the sender address, follows In-Reply-To to the message it sent and adds the reply as a comment on that deal.
| Mailgun | Direction | Krokul | When |
|---|---|---|---|
| Messages API with template and t:variables | Krokul → Mailgun | Won deal, document or paid invoice | The Krokul event fires |
| v:deal_uuid parameter | Krokul → Mailgun → Krokul | Deal reference | Every send |
| Webhook delivered, opened, clicked | Mailgun → Krokul | Activity on the deal | Mailgun processes the message |
| Webhook permanent_fail | Mailgun → Krokul | Mark and task on the contact | The address rejects the message |
| Webhook complained, unsubscribed | Mailgun → Krokul | Mark on the contact | The recipient opts out |
| Route forward() with stripped-text | Mailgun → Krokul | Comment on the deal | The client replies |
| Mailing list member | Krokul → Mailgun | Contact | A contact is created |
Yes. Krokul integrates with Mailgun through the Krokul app in Zapier, Make and n8n and through its API and webhooks, for template sends, delivery events and client replies.
Krokul attaches the deal UUID as the v:deal_uuid parameter of every message. Mailgun returns it in user-variables with each webhook, so the event lands on the deal that sent the e-mail.
Yes. A Mailgun route forwards replies to Krokul with stripped-text, so the comment on the deal holds the new answer without the quoted thread.
Mailgun does not retry a permanent_fail. Krokul marks the contact, opens a task to fix the address and skips the contact in later sends from the same rule.
Sending domains, DNS records, templates and IP reputation are managed in Mailgun. Mailgun shows custom variables to the recipient in a message header and cuts them above 4 KB in events, so Krokul passes only record IDs there.
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.
Mailgun is a trademark of Mailgun Technologies, Inc. Krokul is not affiliated with Mailgun.