Yes. Krokul CRM integrates with Postmark. A deal moving to a new stage, a new document or a paid invoice sends a Postmark template e-mail to the contact, and Postmark webhooks report delivery, opens, clicks, bounces and spam complaints back to the same deal. Client replies come in through Postmark inbound processing and land on the deal as activities. The link runs through the Krokul app in Zapier, Make, n8n and Albato or through the Krokul API and webhooks.
Automation platformsZapierMaken8nAlbato
You link a Krokul event to a Postmark template alias. When a deal reaches the stage you picked or an invoice is paid, Krokul calls the Postmark template endpoint with the TemplateModel filled from the deal, a Tag for the event and the deal UUID in Metadata. Postmark returns a MessageID. Krokul keeps it on the deal.
Postmark sends Delivery, Open and Click webhooks with the Metadata of the original message. Krokul reads the deal UUID, adds the event to the deal timeline and deduplicates repeats by MessageID. The manager sees when the client first opened the quote.
A Bounce webhook names the address and the bounce Type, such as HardBounce. Krokul marks the contact, records the type and creates a task to fix the address on a hard bounce. A SpamComplaint or a SubscriptionChange that stops sending marks the contact as well, so Krokul event rules skip it.
Outgoing deal e-mails use a Reply-To address on the Postmark inbound server with the deal number after a plus sign. When the client answers, the Inbound webhook delivers the parsed message, and MailboxHash holds that deal number. Krokul finds the deal and the contact by the From address and saves StrippedTextReply as an activity, with attachments as file links.
| Postmark | Direction | Krokul | When |
|---|---|---|---|
| Template e-mail (TemplateAlias, TemplateModel, Metadata) | Krokul → Postmark | Deal stage, document or paid invoice | The Krokul event fires |
| MessageID | Postmark → Krokul | Comment on the deal | Postmark accepts the message |
| Delivery, Open, Click webhooks | Postmark → Krokul | Activity on the deal | The recipient gets or opens the e-mail |
| Bounce (HardBounce), SpamComplaint | Postmark → Krokul | Mark and task on the contact | Delivery fails or the client complains |
| SubscriptionChange | Postmark → Krokul | Mark on the contact | Sending to the address stops or resumes |
| Inbound message (MailboxHash, StrippedTextReply) | Postmark → Krokul | Activity on the deal | The client replies |
Yes. Krokul integrates with Postmark through the Krokul app in Zapier, Make, n8n and Albato and through its API and webhooks, for template e-mail, delivery events and inbound replies.
The Reply-To address of each deal e-mail carries the deal number after a plus sign. Postmark returns that part as MailboxHash in the Inbound webhook, and Krokul attaches the reply to that deal.
Postmark has no HMAC signature on webhooks. Krokul gives Postmark a URL with Basic authentication credentials and accepts calls only from the Postmark IP ranges.
The default transactional stream, outbound, unless you pick another stream in the event rule. Broadcast streams stay for newsletters sent from Postmark.
Templates, sender signatures, message streams and the Postmark suppression list stay in Postmark. Postmark webhooks carry no HMAC signature, so the receiving URL is protected with Basic authentication and the published Postmark IP ranges.
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.
Postmark is a trademark of ActiveCampaign, LLC. Krokul is not affiliated with Postmark.