Start with the offer record
Website platforms should receive context from the offer, checkout, product, price, invoice, and automation path instead of a disconnected form submission.
Role · website
Website platforms
Drop Plandalf into the site builder you already use.
ActiveCampaign
Sends email · Runs automations · Custom HTML blocks
beehiiv
Sends email · Runs automations · Custom HTML blocks
Kit (ConvertKit)
Sends email · Runs automations · Custom HTML blocks
HTML
Hosts pages · Custom HTML blocks · Embed-script support
Customer.io
Sends email · Runs automations · Custom HTML blocks
Drip
Sends email · Runs automations · Custom HTML blocks
Flodesk
Sends email · Runs automations · Custom HTML blocks
Klaviyo
Sends email · Runs automations · Custom HTML blocks
Mailchimp
Sends email · Runs automations · Custom HTML blocks
MailerLite
Sends email · Runs automations · Plandalf Automation Integration
Next.js
Hosts pages · Custom HTML blocks · Embed-script support
Postmark
Sends email · Custom HTML blocks · Per-recipient timer images
React
Hosts pages · Custom HTML blocks · Embed-script support
SendGrid
Sends email · Custom HTML blocks · Per-recipient timer images
Shopify
Hosts pages · Hosts Checkout · Custom HTML blocks
S
Substack
Publishes posts · Hosts newsletter pages · Supports links and buttons
Vue
Hosts pages · Custom HTML blocks · Embed-script support
Webflow
Hosts pages · Custom HTML blocks · Embed-script support
WordPress
Hosts pages · Custom HTML blocks · Embed-script support
Where this role touches the Plandalf workflow
A useful Website platforms page should show how the role connects to Offers, checkout, integrations, invoices, API work, webhooks, and post-purchase automation.
Keep integration settings visible
Operators should be able to inspect Stripe, PayPal, TaxJar, Avalara, test mode, payment options, and connected tools before launch.
Use documented API paths
Developer and agent-built workflows should use API authentication, SDK checkout, and webhooks rather than hidden scripts or untracked credentials.
Setup paths to keep open
Use these internal paths while deciding how Website platforms should receive checkout, payment, invoice, buyer, and event context.
Checkout sourceUse Offers to define the product, price, checkout, invoice, and payment context before Website platforms receive anything.Event deliveryUse webhooks, API handlers, and sequences when the purchase event needs to update another tool.Integration catalogCompare Website platforms with payment, site, CRM, email, tax, SDK, and automation platforms.Operational recordsKeep invoices, records, buyer context, product lines, payment state, and fulfilment handoffs inspectable.
Related implementation resources
These resources help connect platform choice to checkout implementation, API work, webhook delivery, security review, and post-purchase operations.
All integrationsBrowse platform records, generated app-pair guides, and stack paths.API-first stackSDK checkout, API keys, integrations, invoices, and webhooks together.Checkout fulfilment sequenceRoute purchase context into fulfilment, records, alerts, and access.Security overviewReview API, webhook, payment, invoice, and integration control paths.