Offer setup before anything syncs
HTML receives cleaner data when the offer, product, price, checkout mode, invoice, and automation path are defined first.
App integrations
pages
Connect HTML to the platforms you already sell with
Use Plandalf to connect HTML with checkout pages, payment flows, email tools, CRM records, access systems, tax engines, and webhooks.
Popular connections
HTML works with…
Use these as practical recipes, not just directory entries. Each one should explain the checkout, automation, payment, email, CRM, tax, or API handoff that matters.
HTML + PayPal
Score 85
Take payment through PayPal from pages hosted on HTML.
HTML + Drip
Score 80
Capture leads on HTML and follow up through Drip.
HTML + Kit (ConvertKit)
Score 80
Capture leads on HTML and follow up through Kit (ConvertKit).
HTML + Klaviyo
Score 80
Capture leads on HTML and follow up through Klaviyo.
HTML + Mailchimp
Score 80
Capture leads on HTML and follow up through Mailchimp.
HTML + Stripe
Score 77
Take payment through Stripe from pages hosted on HTML.
HTML + HubSpot
Score 74
Capture leads on HTML and follow up through HubSpot.
HTML + ActiveCampaign
Score 70
Capture leads on HTML and follow up through ActiveCampaign.
HTML + beehiiv
Score 70
Capture leads on HTML and follow up through beehiiv.
HTML + Customer.io
Score 70
Capture leads on HTML and follow up through Customer.io.
HTML + Flodesk
Score 70
Capture leads on HTML and follow up through Flodesk.
HTML + MailerLite
Score 70
Capture leads on HTML and follow up through MailerLite.
How it works
Plandalf is the commerce layer between apps
HTML keeps doing what it is best at. Plandalf handles the offer, checkout, buyer fields, payment context, invoice data, and post-purchase events that every other app needs.
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.
Search paths
Pages this hub can feed
Product surfaces to check before wiring HTML
A useful HTML integration page should show where the operator configures Offers, payment options, invoices, Automations, integrations, and API settings before a developer ships the flow.
Checkout can live on the site or app
HTML can launch a hosted checkout, buy button, embedded flow, or SDK checkout depending on where the buyer starts.
Recipes to keep open while building
HTML can be part of a payment stack, a site stack, a marketing stack, or an automation stack. These Plandalf resources keep the implementation tied to real checkout and purchase events.
Checkout completed fulfilment Route product, buyer, invoice, and payment state after purchase. Purchase event webhook fanout Send one purchase event into multiple downstream tools. API-first commerce stack Use SDK checkout, API keys, webhooks, and operator-visible settings together. HTML platform overview See the supported roles, setup patterns, and product surfaces for HTML.