beehiiv

Integration

beehiiv

Plandalf integrates with beehiiv as a email, marketing, website, sdk platform.

What it does

Product surfaces

Where beehiiv 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 beehiiv receives checkout, payment, tax, or workflow context.

The Numi offer editor showing layout, product, theme, automation, invoice, and settings controls.
The Numi checkout elements palette showing content, interactive, and selling blocks.
The Numi offer editor automation tab showing sequence controls beside the checkout canvas.

Purchase events can start follow-up

beehiiv should fit into the work after checkout: fulfilment, records, CRM updates, support context, webhooks, and sequences.

The Numi offer editor showing hosted checkout mode controls.

Overview

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.

What Plandalf does here

  • Countdown in posts — HTML blocks accept a <img> tag with beehiiv’s {{ email }} merge tag.
  • Automation-driven enrolment — on Scale tier, a native Webhook step POSTs to the promo’s catch URL directly.

Setup templates

Drop-in implementations

Copy-paste setups for the most common ways to wire beehiiv into Plandalf.

promo · email

Drop the Plandalf countdown image into a beehiiv post

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

Enrol beehiiv subscribers via Automations

  1. In beehiiv, go to Automations → Create automation.
  2. Trigger: New subscriber (filtered by a segment or tag if the promo is audience-specific).
  3. Add a step: Webhook (available on beehiiv Scale and above; use the Zapier tab on smaller plans).
  4. URL:
    {{ promo.catch_url }}
    
  5. Method POST, content type application/json, payload:
    {"email": "{{ email }}", "ref": "{{ email }}"}
    
  6. Publish the automation.

Automation graph

Connecting beehiiv

How beehiiv participates in Plandalf sequences: what events it exposes upward, and what actions Plandalf can perform on it.

Triggers from beehiiv

Events Plandalf can subscribe to through webhooks, API work, checkout state, payment context, and connected integrations.

beehiiv.subscriber_added
Fires when a new subscriber is added to beehiiv.
beehiiv.automation_step_reached
Fires when a contact reaches a designated step in a beehiiv automation.
beehiiv.form_submitted
Fires when a form on beehiiv is submitted.
beehiiv.webhook
Fires when beehiiv POSTs to a Plandalf webhook URL — use for anything not covered by a native trigger.

Actions on beehiiv

Things Plandalf sequences can do after checkout, payment, invoice, customer, or deadline events.

beehiiv.add_subscriber
Add a contact to a list or audience in beehiiv.
beehiiv.tag
Apply a tag or segment to an existing beehiiv contact.
beehiiv.send_email
Send a one-off transactional or broadcast email through beehiiv.
beehiiv.start_automation
Enrol a contact into a beehiiv automation.
beehiiv.custom_api_call
Hit any beehiiv REST endpoint with a templated payload.

Embeddable surfaces: Plandalf countdown image and buy button HTML · Per-recipient countdown GIF with merge-tag substitution

Example sequence
trigger: stripe.payment_succeeded
actions:
  - beehiiv.add_subscriber:
      list: paying-customers
      tag: tier-${plan}
  - plandalf.grant_entitlement: ${product_slug}

Integration methods

How beehiiv connects to Plandalf

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.

  1. Method 1

    Embed a Plandalf buy button

    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>
  2. Method 2

    Drop in a per-recipient countdown image

    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"
    />
  3. Method 3

    Trigger a sequence from a form

    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"}'
  4. Method 4

    Enrol from an automation step

    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"
    }
  5. Method 5

    REST API webhook

    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.json
Official beehiiv docs and sign-up: www.beehiiv.com

FAQ

Common questions about the beehiiv integration

Do I need a paid plan to use beehiiv with Plandalf?

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.

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 beehiiv later without losing data?

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.

Does Plandalf store beehiiv data?

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.

What if my email need isn't covered by the actions or triggers listed here?

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.

Is there a usage limit?

Plandalf respects beehiiv'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 beehiiv's own documentation?

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.

Feature detail