Integration

HTML

Plandalf integrates with HTML as a website, sdk platform.

website sdk

Visit HTML →

What it does

Hosts pagesHosted checkout pages Buy button
Custom HTML blocksTotally custom checkout layouts Buy button
Embed-script supportBuy button SDK

Product surfaces

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

The Numi offer editor showing layout, product, theme, automation, invoice, and settings controls.

Offer configuration stays visible

Use Offers to decide what HTML receives: product, price, buyer, checkout mode, invoice, and automation context.

Offers Products Prices Checkout templates

The Numi checkout elements palette showing content, interactive, and selling blocks.

Checkout layout and selling blocks stay editable

Before HTML enters the stack, operators still need checkout templates, products, prices, coupons, order bumps, upsells, and branded offer content they can inspect.

Checkout templates Order bumps Upsells Coupons

The Numi offer editor automation tab showing sequence controls beside the checkout canvas.

Purchase events can start follow-up

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

Purchase automations Automations Sequences Webhooks

The Numi offer editor showing hosted checkout mode controls.

The buying surface can live where the buyer is

HTML can start the sale through a hosted checkout, embedded checkout, modal, inline flow, or buy button depending on the stack.

Hosted checkout Buy button SDK checkout API-first stack

Builder paths

Stack guides that use HTML

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

Substack ShopSell a template, report, workshop, membership, or paid download from a Substack post while Plandalf owns the offer, checkout, invoice, and purchase event.

HTML stack recipes

Find full stack guides that pair HTML 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 HTML should hand the buyer to a branded Plandalf checkout page.

SDK checkout

Use SDK checkout when HTML 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

Plain HTML — the escape hatch for any stack we don’t have a dedicated catalog entry for yet. Drop the Plandalf SDK <script> tag before the closing </body> tag of whichever page serves your storefront, and promo / checkout embeds work identically to the named platforms.

Pair it with

Connect HTML with…

Platforms whose roles complement HTML inside a Plandalf sequence.

HTML + ActiveCampaign

Capture form leads on HTML straight into ActiveCampaign.

HTML + beehiiv

Capture form leads on HTML straight into beehiiv.

HTML + Kit (ConvertKit)

Capture form leads on HTML straight into Kit (ConvertKit).

HTML + Customer.io

Capture form leads on HTML straight into Customer.io.

HTML + Drip

Capture form leads on HTML straight into Drip.

HTML + Flodesk

Capture form leads on HTML straight into Flodesk.

See all integrations →

Integration methods

How HTML connects to Plandalf

Each method below is the minimum viable setup. Pick the one closest to how you already use HTML 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 HTML 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>
```

Official HTML docs and sign-up: developer.mozilla.org/en-US/docs/Web/HTML

FAQ

Common questions about the HTML integration

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

Plandalf itself is free to connect to HTML. You only need a HTML account that allows API access, which is almost every paid plan.

How long does setup take?

Under 10 minutes — paste a webhook URL into HTML, point it at the Plandalf endpoint, and trigger a test event to confirm.

Can I disconnect HTML later without losing data?

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

Does Plandalf store HTML data?

Plandalf stores the minimum IDs needed to address a record in HTML plus a log of events Plandalf fired. Source-of-truth data stays in HTML.

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

Drop into the Plandalf REST API and call HTML directly from your sequence's HTTP action. Anything HTML's public surface exposes is reachable.

Is there a usage limit?

There's no Plandalf-side limit. HTML's own plan limits apply.

Where do I find HTML's own documentation?

HTML's homepage at https://developer.mozilla.org/en-US/docs/Web/HTML links to their developer docs. For Plandalf-side questions about the HTML integration, see the Plandalf docs.