Offer configuration stays visible
Use Offers to decide what Postmark receives: product, price, buyer, checkout mode, invoice, and automation context.
What it does
- Sends emailEmail GIF promoNotifications
- Custom HTML blocksTotally custom checkout layoutsBuy button
- Per-recipient timer imagesEmail GIF promoDeadline campaigns
- Open APIAPISDK
Product surfaces
Where Postmark fits in the buying workflow
Integrations work best when the checkout surface, payment state, invoice record, and post-purchase automation all point at the same commercial object. These product screens show the Plandalf controls that should be configured before Postmark receives checkout, payment, tax, or workflow context.
Checkout layout and selling blocks stay editable
Before Postmark enters the stack, operators still need checkout templates, products, prices, coupons, order bumps, upsells, and branded offer content they can inspect.
Purchase events can start follow-up
Postmark should fit into the work after checkout: fulfilment, records, CRM updates, support context, webhooks, and sequences.
The buying surface can live where the buyer is
Postmark can start the sale through a hosted checkout, embedded checkout, modal, inline flow, or buy button depending on the stack.
Builder paths
Stack guides that use Postmark
Use these stack guides when a builder needs the whole path: sales surface, Plandalf offer, payment handoff, automation, fulfilment, records, and downstream integrations.
The API-First ProductSplit transactional email from lifecycle email so each tool does what it's good at.The Developer Webhook StackGive developers a concrete stack for API-led checkout, entitlements, fulfillment, analytics, and custom automations.The Invoice Records Ops StackKeep invoices, receipts, customer identity, team notifications, and CRM records in sync after purchase.
Postmark stack recipes
Find full stack guides that pair Postmark with checkout, payment, automation, fulfilment, records, and downstream integrations.
Offers overview
Use Offers to package products, prices, checkout pages, invoices, coupons, payment options, and follow-up context.
Hosted checkout
Use hosted checkout when Postmark should hand the buyer to a branded Plandalf checkout page.
SDK checkout
Use SDK checkout when Postmark belongs inside an app, custom site, or API-first stack.
Webhooks
Route checkout events, purchase events, payment state, invoices, and customer context into another tool.
Checkout completed fulfilment
Turn a completed checkout into access, receipts, CRM updates, support context, and records.
Overview
Postmark is a transactional email provider. There’s no built-in workflow builder for promo enrolment; that flow runs through Zapier or a Custom API call from the backend that triggers each Postmark send.
What Plandalf does here
- Countdown in templates — Mustachio
{{email}}resolves against the template model your backend passes on the Email Send API call.
Setup templates
Drop-in implementations
Copy-paste setups for the most common ways to wire Postmark into Plandalf.
promo · email
Drop the Plandalf countdown image into a Postmark template
In your Postmark template (Mustachio syntax), paste this <img>
tag into the HTML editor. {{email}} resolves against whatever
model you pass when calling the Email Send API.
<img
src="{{ promo.countdown_url }}?ref={{email}}"
alt="Time remaining on this offer"
/>
Ensure the template-model payload on your send call includes the
recipient's address under email — or substitute whichever field
name you use (to, recipient, etc.).
Automation graph
Connecting Postmark
How Postmark participates in Plandalf sequences: what events it exposes upward, and what actions Plandalf can perform on it.
Triggers from Postmark
Events Plandalf can subscribe to through webhooks, API work, checkout state, payment context, and connected integrations.
postmark.subscriber_added- Fires when a new subscriber is added to Postmark.
Actions on Postmark
Things Plandalf sequences can do after checkout, payment, invoice, customer, or deadline events.
postmark.add_subscriber- Add a contact to a list or audience in Postmark.
postmark.tag- Apply a tag or segment to an existing Postmark contact.
postmark.send_email- Send a one-off transactional or broadcast email through Postmark.
postmark.custom_api_call- Hit any Postmark REST endpoint with a templated payload.
Embeddable surfaces: Plandalf countdown image and buy button HTML · Per-recipient countdown GIF with merge-tag substitution
trigger: stripe.payment_succeeded
actions:
- postmark.add_subscriber:
list: paying-customers
tag: tier-${plan}
- plandalf.grant_entitlement: ${product_slug}Pair it with
Connect Postmark with…
Platforms whose roles complement Postmark inside a Plandalf sequence.
Postmark + ActiveCampaign
Capture a lead on ActiveCampaign, nurture it through Postmark.
Postmark + beehiiv
Capture a lead on beehiiv, nurture it through Postmark.
Postmark + Kit (ConvertKit)
Capture a lead on Kit (ConvertKit), nurture it through Postmark.
Postmark + Customer.io
Capture a lead on Customer.io, nurture it through Postmark.
Postmark + Drip
Capture a lead on Drip, nurture it through Postmark.
Postmark + Flodesk
Capture a lead on Flodesk, nurture it through Postmark.
Integration methods
How Postmark connects to Plandalf
Each method below is the minimum viable setup. Pick the one closest to how you already use Postmark with checkout, payments, invoices, webhooks, API work, SDK checkout, and integrations.
- Method 1
Embed a Plandalf buy button
Drop the Plandalf embed script into a Postmark HTML block and tag any element with `data-plandalf-present` to open the configured flow on click.
<script src="https://cdn.plandalf.com/embed.js" async></script> <button data-plandalf-present="offer_abc123"> Buy now </button> - Method 2
Drop in a per-recipient countdown image
Add an HTML block to any Postmark email and paste the Plandalf countdown URL. Postmark's merge tag `{{ email }}` substitutes per recipient so each subscriber sees a timer pegged to their own deadline.
<img src="https://cdn.plandalf.com/timers/{TIMER_ID}.gif?ref={{ email }}" alt="Time remaining on this offer" width="600" height="120" /> - Method 3
REST API webhook
For anything not covered by a native trigger, configure a Postmark webhook to POST to Plandalf. The payload is forwarded into the sequence as `${event}`.
curl -X POST https://api.plandalf.com/v1/webhooks/postmark \ -H "Authorization: Bearer $PLANDALF_API_KEY" \ -H "Content-Type: application/json" \ -d @event.json
FAQ
Common questions about the Postmark integration
Do I need a paid plan to use Postmark with Plandalf?
Plandalf itself is free to connect to Postmark. You only need a Postmark account that allows API access, which is almost every paid plan.
How long does setup take?
Under 10 minutes. OAuth (or paste an API key), pick the lists/segments you care about, and you're live. No code unless you want it.
Can I disconnect Postmark later without losing data?
Yes. Disconnecting only revokes the credentials — historical events Plandalf fired stay in your sequence logs, and Postmark's own records are untouched. You can reconnect any time and resume from the last seen event.
Does Plandalf store Postmark data?
Plandalf stores the Postmark contact ID and the events Plandalf fired against that contact. Email content stays in Postmark; Plandalf doesn't mirror your audience or newsletter archive.
What if my email need isn't covered by the actions or triggers listed here?
Use the generic `postmark.custom_api_call` action or the inbound `postmark.webhook` trigger. Anything Postmark's REST API can do, a Plandalf sequence can drive.
Is there a usage limit?
Plandalf respects Postmark's API rate limits and backs off on 429s. For very high-volume use cases, ask about a dedicated worker pool.
Where do I find Postmark's own documentation?
Postmark's homepage at https://postmarkapp.com links to their developer docs. For Plandalf-side questions about the Postmark integration, see the Plandalf docs.