Webflow stores that sell digital goods
A shop on Webflow sells packs through a Plandalf checkout. Each paid order creates a Placed Order style event in Klaviyo and a flow handles cross-sell emails.

Checkout embed
Webflow hosts the buy button, Plandalf takes payment, and a Send Webhook step can push the buyer or the order into Klaviyo.
No credit card required. No coding required.
Webflow
KlaviyoPlandalf has no native Klaviyo steps and does not read Webflow forms. A Webflow button opens the Plandalf checkout, and after payment a Send Webhook step can call Klaviyo's API. Klaviyo flows can also enrol people in a Plandalf promo through a webhook action, and a countdown image can sit in a flow email.
| Event | From and to | Through | What happens |
|---|---|---|---|
| Buy button clicked | Webflow → Plandalf | A Webflow button with the data-plandalf-present attribute opens the offer after the SDK is added to Footer code. | |
| Checkout completed | Plandalf → Klaviyo | Webhook | A Send Webhook step posts JSON to Klaviyo's profile import endpoint, https://a.klaviyo.com/api/profile-import, with your private API key in the Authorization header. |
| Purchase as a Klaviyo event | Plandalf → Klaviyo | Webhook | The Klaviyo events endpoint takes a metric name, a profile, properties and an optional value. A flow that uses the metric as its trigger can then send the follow-up emails. |
| Flow webhook action | Klaviyo → Plandalf | Webhook | A Klaviyo flow can post to a Plandalf Webhook Trigger URL so the Enroll in Promo step starts a countdown for that profile. |
| Countdown in a flow email | Plandalf → Klaviyo | By hand | A countdown image tag goes into an HTML block, using Klaviyo's person email merge tag in the ref query string. The same promo drives the Webflow countdown. |
Klaviyo's API wants a private key, a revision header and a JSON:API style body, so do the first send in the step's Test tab before turning anything on.
Add the Plandalf SDK to Site settings, Custom code, Footer code, give the Webflow button the data-plandalf-present attribute and publish.
Make a private API key with the write scope for profiles, and for events if you want flows to start from the purchase. Keep it out of Webflow custom code, because the key belongs only in the Plandalf step.
In Automation, My Sequences choose Plandalf and Checkout Completed, pick the Webflow offer and choose a recent checkout as the sample on the Test tab.
Add Plandalf, Send Webhook. Set the URL to Klaviyo's profile import endpoint, method POST, headers for Authorization (Klaviyo-API-Key followed by your key) and revision, and a JSON payload with the type profile and the buyer's email from {{trigger.customer_email}}.
Run the step's test with your own email. If Klaviyo rejects the content type, check the response in the run's Events view and use Zapier's Webhooks as the relay instead.
Turn the sequence on. A refund does not undo anything in Klaviyo by itself, so add a second Send Webhook on Invoice Refunded if you want a profile property or event to change.
A shop on Webflow sells packs through a Plandalf checkout. Each paid order creates a Placed Order style event in Klaviyo and a flow handles cross-sell emails.
A brand running a limited drop uses a Klaviyo list flow that enrols each subscriber in a promo, so the email countdown and the Webflow countdown end together.
revision header and a vnd.api+json content type. If Send Webhook cannot send that, the call fails and a relay such as Zapier is needed.value you send.Checked October 26, 2026 against Plandalf's own setup guides and the vendor documentation: Klaviyo API: create or update profile, Klaviyo API: create event, Klaviyo help: understanding webhooks in flows.