Offer configuration stays visible
Use Offers to decide what Webflow receives: product, price, buyer, checkout mode, invoice, and automation context.
What it does
- Hosts pagesHosted checkout pagesBuy button
- Custom HTML blocksTotally custom checkout layoutsBuy button
- Embed-script supportBuy buttonSDK
Product surfaces
Where Webflow 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 Webflow receives checkout, payment, tax, or workflow context.
Checkout layout and selling blocks stay editable
Before Webflow 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
Webflow 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
Webflow 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 Webflow
Use these stack guides when a builder needs the whole path: sales surface, Plandalf offer, payment handoff, automation, fulfilment, records, and downstream integrations.
The Checkout Optimization LabTest checkout layouts, sessions, mobile flow, and recovery without turning the sales page into a custom app.The Coupon Deadline FunnelRun a deadline offer with coupon rules and follow-up paths that stay attached to the checkout.The Course CreatorEnrol each buyer into the right cohort sequence the moment they pay.The Drop ShopRun a time-boxed drop with a real countdown, a bundle upsell, and segmented re-engagement.The Template ShopSell digital download products with license-tier upsells and post-purchase delivery.
Webflow stack recipes
Find full stack guides that pair Webflow 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 Webflow should hand the buyer to a branded Plandalf checkout page.
SDK checkout
Use SDK checkout when Webflow 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
Webflow sites load third-party scripts via Site Settings → Custom
Code → Footer Code. Buttons pick up SDK behaviour through Webflow’s
Custom Attributes feature — attach data-plandalf-present to any
element and it opens the configured flow.
Pair it with
Connect Webflow with…
Platforms whose roles complement Webflow inside a Plandalf sequence.
Webflow + ActiveCampaign
Capture form leads on Webflow straight into ActiveCampaign.
Webflow + beehiiv
Capture form leads on Webflow straight into beehiiv.
Webflow + Kit (ConvertKit)
Capture form leads on Webflow straight into Kit (ConvertKit).
Webflow + Customer.io
Capture form leads on Webflow straight into Customer.io.
Webflow + Drip
Capture form leads on Webflow straight into Drip.
Webflow + Flodesk
Capture form leads on Webflow straight into Flodesk.
Integration methods
How Webflow connects to Plandalf
Each method below is the minimum viable setup. Pick the one closest to how you already use Webflow 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 Webflow 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>
FAQ
Common questions about the Webflow integration
Do I need a paid plan to use Webflow with Plandalf?
Plandalf itself is free to connect to Webflow. You only need a Webflow account that allows API access, which is almost every paid plan.
How long does setup take?
Under 10 minutes — paste a webhook URL into Webflow, point it at the Plandalf endpoint, and trigger a test event to confirm.
Can I disconnect Webflow later without losing data?
Yes. Disconnecting only revokes the credentials — historical events Plandalf fired stay in your sequence logs, and Webflow's own records are untouched. You can reconnect any time and resume from the last seen event.
Does Plandalf store Webflow data?
Plandalf stores the minimum IDs needed to address a record in Webflow plus a log of events Plandalf fired. Source-of-truth data stays in Webflow.
What if my website need isn't covered by the actions or triggers listed here?
Drop into the Plandalf REST API and call Webflow directly from your sequence's HTTP action. Anything Webflow's public surface exposes is reachable.
Is there a usage limit?
There's no Plandalf-side limit. Webflow's own plan limits apply.
Where do I find Webflow's own documentation?
Webflow's homepage at https://webflow.com links to their developer docs. For Plandalf-side questions about the Webflow integration, see the Plandalf docs.