Klaviyo

Integration

Klaviyo

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

What it does

Product surfaces

Where Klaviyo 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 Klaviyo 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

Klaviyo 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.

Builder paths

Stack guides that use Klaviyo

Use these stack guides when a builder needs the whole path: sales surface, Plandalf offer, payment handoff, automation, fulfilment, records, and downstream integrations.

Overview

Klaviyo is an ecommerce-focused email and SMS platform with a powerful Flow builder that supports webhook actions natively. For promos, the standard pattern is embedding a countdown GIF into a flow email and enrolling subscribers from a List-triggered or Metric-triggered flow.

What Plandalf does here

  • Per-recipient countdown — Klaviyo’s {{ person.email }} merge tag passes straight into the <img src> query string, so each subscriber sees their own deadline.
  • Flow-driven enrolment — Flows include a native Webhook action, allowing direct POSTs to the promo’s catch URL without middleware.

Setup templates

Drop-in implementations

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

promo · email

Drop the Plandalf countdown image into a Klaviyo flow

Paste this <img> tag into a Text block (in source mode) or an HTML block in your Klaviyo campaign or flow email. {{ person.email }} is Klaviyo's merge tag for the recipient — Klaviyo substitutes it at send time.

<img
  src="{{ promo.countdown_url }}?ref={{ person.email }}"
  alt="Time remaining on this offer"
/>

promo · automation

Enrol Klaviyo profiles via a Flow

  1. In Klaviyo, go to Flows → Create Flow.
  2. Pick a trigger — List Triggered on the list that represents your promo audience, or Metric Triggered on an event like Placed Order or Subscribed to List.
  3. Drag in a Webhook action.
  4. Destination URL:
    {{ promo.catch_url }}
    
  5. Method POST, content type application/json, body:
    {"email": "{{ person.email }}", "ref": "{{ person.email }}"}
    
  6. Turn the flow live.

Automation graph

Connecting Klaviyo

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

Triggers from Klaviyo

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

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

Actions on Klaviyo

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

klaviyo.add_subscriber
Add a contact to a list or audience in Klaviyo.
klaviyo.tag
Apply a tag or segment to an existing Klaviyo contact.
klaviyo.send_email
Send a one-off transactional or broadcast email through Klaviyo.
klaviyo.start_automation
Enrol a contact into a Klaviyo automation.
klaviyo.custom_api_call
Hit any Klaviyo 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:
  - klaviyo.add_subscriber:
      list: paying-customers
      tag: tier-${plan}
  - plandalf.grant_entitlement: ${product_slug}

Integration methods

How Klaviyo connects to Plandalf

Each method below is the minimum viable setup. Pick the one closest to how you already use Klaviyo 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 Klaviyo 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 Klaviyo email and paste the Plandalf countdown URL. Klaviyo's merge tag `{{ person.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={{ person.email }}"
      alt="Time remaining on this offer"
      width="600"
      height="120"
    />
  3. Method 3

    Trigger a sequence from a form

    Point a Klaviyo 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/klaviyo \
      -H "Content-Type: application/json" \
      -d '{"email": "{{ form.email }}", "source": "klaviyo"}'
  4. Method 4

    Enrol from an automation step

    Inside Klaviyo's automation builder, add a Webhook step that POSTs the contact to a Plandalf sequence catch URL. Use this to mirror Klaviyo journey logic into Plandalf without re-building the segmentation.

    {
      "email": "{{ contact.email }}",
      "sequence": "post-signup-onboarding",
      "source": "klaviyo"
    }
  5. Method 5

    REST API webhook

    For anything not covered by a native trigger, configure a Klaviyo webhook to POST to Plandalf. The payload is forwarded into the sequence as `${event}`.

    curl -X POST https://api.plandalf.com/v1/webhooks/klaviyo \
      -H "Authorization: Bearer $PLANDALF_API_KEY" \
      -H "Content-Type: application/json" \
      -d @event.json
Official Klaviyo docs and sign-up: www.klaviyo.com

FAQ

Common questions about the Klaviyo integration

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

Plandalf itself is free to connect. Klaviyo'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 Klaviyo later without losing data?

Yes. Disconnecting only revokes the credentials — historical events Plandalf fired stay in your sequence logs, and Klaviyo's own records are untouched. You can reconnect any time and resume from the last seen event.

Does Plandalf store Klaviyo data?

Plandalf stores the Klaviyo contact ID and the events Plandalf fired against that contact. Email content stays in Klaviyo; 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 `klaviyo.custom_api_call` action or the inbound `klaviyo.webhook` trigger. Anything Klaviyo's REST API can do, a Plandalf sequence can drive.

Is there a usage limit?

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

Klaviyo's homepage at https://www.klaviyo.com links to their developer docs. For Plandalf-side questions about the Klaviyo integration, see the Plandalf docs.

Feature detail