Offer configuration stays visible
Use Offers to decide what beehiiv receives: product, price, buyer, checkout mode, invoice, and automation context.
Product surfaces
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 beehiiv receives checkout, payment, tax, or workflow context.
Use Offers to decide what beehiiv receives: product, price, buyer, checkout mode, invoice, and automation context.
Before beehiiv enters the stack, operators still need checkout templates, products, prices, coupons, order bumps, upsells, and branded offer content they can inspect.
beehiiv should fit into the work after checkout: fulfilment, records, CRM updates, support context, webhooks, and sequences.
beehiiv can start the sale through a hosted checkout, embedded checkout, modal, inline flow, or buy button depending on the stack.
beehiiv is a newsletter platform with a built-in Automations product on Scale and above. Its webhook step — combined with the New Subscriber trigger — makes for a direct Plandalf enrolment bridge; smaller plans route through Zapier.
<img> tag with
beehiiv’s {{ email }} merge tag.Setup templates
Copy-paste setups for the most common ways to wire beehiiv into Plandalf.
promo · email
In the beehiiv post editor, add an HTML block and paste this
snippet. {{ email }} is beehiiv's Liquid merge tag for the
recipient.
<img
src="{{ promo.countdown_url }}?ref={{ email }}"
alt="Time remaining on this offer"
/>
promo · automation
{{ promo.catch_url }}
POST, content type application/json, payload:
{"email": "{{ email }}", "ref": "{{ email }}"}
Automation graph
How beehiiv participates in Plandalf sequences: what events it exposes upward, and what actions Plandalf can perform on it.
Events Plandalf can subscribe to through webhooks, API work, checkout state, payment context, and connected integrations.
beehiiv.subscriber_addedbeehiiv.automation_step_reachedbeehiiv.form_submittedThings Plandalf sequences can do after checkout, payment, invoice, customer, or deadline events.
beehiiv.add_subscriberbeehiiv.tagbeehiiv.send_emailbeehiiv.start_automationbeehiiv.custom_api_callEmbeddable surfaces: Plandalf countdown image and buy button HTML · Per-recipient countdown GIF with merge-tag substitution
trigger: stripe.payment_succeeded
actions:
- beehiiv.add_subscriber:
list: paying-customers
tag: tier-${plan}
- plandalf.grant_entitlement: ${product_slug}Pair it with
Platforms whose roles complement beehiiv inside a Plandalf sequence.
beehiiv + ActiveCampaign
Capture a lead on ActiveCampaign, nurture it through beehiiv.
beehiiv + Kit (ConvertKit)
Capture a lead on Kit (ConvertKit), nurture it through beehiiv.
beehiiv + Customer.io
Capture a lead on Customer.io, nurture it through beehiiv.
beehiiv + Drip
Capture a lead on Drip, nurture it through beehiiv.
beehiiv + Flodesk
Capture a lead on Flodesk, nurture it through beehiiv.
beehiiv + Klaviyo
Capture a lead on Klaviyo, nurture it through beehiiv.
Integration methods
Each method below is the minimum viable setup. Pick the one closest to how you already use beehiiv with checkout, payments, invoices, webhooks, API work, SDK checkout, and integrations.
Drop the Plandalf embed script into a beehiiv 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>Add an HTML block to any beehiiv email and paste the Plandalf countdown URL. beehiiv'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"
/>Point a beehiiv form's webhook / POST URL at Plandalf's intake endpoint and every submission starts whatever sequence you've mapped to it.
curl -X POST https://api.plandalf.com/v1/intake/beehiiv \
-H "Content-Type: application/json" \
-d '{"email": "{{ form.email }}", "source": "beehiiv"}'Inside beehiiv's automation builder, add a Webhook step that POSTs the contact to a Plandalf sequence catch URL. Use this to mirror beehiiv journey logic into Plandalf without re-building the segmentation.
{
"email": "{{ contact.email }}",
"sequence": "post-signup-onboarding",
"source": "beehiiv"
}For anything not covered by a native trigger, configure a beehiiv webhook to POST to Plandalf. The payload is forwarded into the sequence as `${event}`.
curl -X POST https://api.plandalf.com/v1/webhooks/beehiiv \
-H "Authorization: Bearer $PLANDALF_API_KEY" \
-H "Content-Type: application/json" \
-d @event.jsonFAQ
Plandalf itself is free to connect. beehiiv's native webhook step is on its paid tiers — on the free plan, route the trigger through Zapier instead, which still works end-to-end.
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.
Yes. Disconnecting only revokes the credentials — historical events Plandalf fired stay in your sequence logs, and beehiiv's own records are untouched. You can reconnect any time and resume from the last seen event.
Plandalf stores the beehiiv contact ID and the events Plandalf fired against that contact. Email content stays in beehiiv; Plandalf doesn't mirror your audience or newsletter archive.
Use the generic `beehiiv.custom_api_call` action or the inbound `beehiiv.webhook` trigger. Anything beehiiv's REST API can do, a Plandalf sequence can drive.
Plandalf respects beehiiv's API rate limits and backs off on 429s. For very high-volume use cases, ask about a dedicated worker pool.
beehiiv's homepage at https://www.beehiiv.com links to their developer docs. For Plandalf-side questions about the beehiiv integration, see the Plandalf docs.