Offer setup before anything syncs
WordPress receives cleaner data when the offer, product, price, checkout mode, invoice, and automation path are defined first.
App integrations
pages
Connect WordPress to the platforms you already sell with
Use Plandalf to connect WordPress with checkout pages, payment flows, email tools, CRM records, access systems, tax engines, and webhooks.
Popular connections
WordPress 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.
WordPress + PayPal
Score 95
Take payment through PayPal from pages hosted on WordPress.
WordPress + Drip
Score 90
Capture leads on WordPress and follow up through Drip.
WordPress + Kit (ConvertKit)
Score 90
Capture leads on WordPress and follow up through Kit (ConvertKit).
WordPress + Klaviyo
Score 90
Capture leads on WordPress and follow up through Klaviyo.
WordPress + Mailchimp
Score 90
Capture leads on WordPress and follow up through Mailchimp.
WordPress + Stripe
Score 87
Take payment through Stripe from pages hosted on WordPress.
WordPress + HubSpot
Score 84
Capture leads on WordPress and follow up through HubSpot.
WordPress + ActiveCampaign
Score 80
Capture leads on WordPress and follow up through ActiveCampaign.
WordPress + beehiiv
Score 80
Capture leads on WordPress and follow up through beehiiv.
WordPress + Customer.io
Score 80
Capture leads on WordPress and follow up through Customer.io.
WordPress + Flodesk
Score 80
Capture leads on WordPress and follow up through Flodesk.
WordPress + MailerLite
Score 80
Capture leads on WordPress and follow up through MailerLite.
How it works
Plandalf is the commerce layer between apps
WordPress 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.
WordPress sites load the SDK via the theme's `footer.php` (or a header/ footer injection plugin like "Insert Headers and Footers"). Custom HTML blocks in Gutenberg accept arbitrary button markup, so the checkout attribute works anywhere the editor will render HTML.
Search paths
Pages this hub can feed
Product surfaces to check before wiring WordPress
A useful WordPress 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
WordPress can launch a hosted checkout, buy button, embedded flow, or SDK checkout depending on where the buyer starts.
Recipes to keep open while building
WordPress 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. WordPress platform overview See the supported roles, setup patterns, and product surfaces for WordPress.