Offer configuration stays visible
Use Offers to decide what WordPress 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 WordPress 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 WordPress receives checkout, payment, tax, or workflow context.
Checkout layout and selling blocks stay editable
Before WordPress 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
WordPress 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
WordPress 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 WordPress
Use these stack guides when a builder needs the whole path: sales surface, Plandalf offer, payment handoff, automation, fulfilment, records, and downstream integrations.
The CoachTake deposits and recurring retainers without re-platforming your existing site.The Invoice Records Ops StackKeep invoices, receipts, customer identity, team notifications, and CRM records in sync after purchase.The Membership SiteConvert one-time buyers into renewed members and keep the CRM in sync.The Newsletter CreatorMonetise an existing newsletter audience by selling one-off products from inside the same list tool.The StudioClose international clients who insist on PayPal, then drop the signed deal straight into the project tracker.
WordPress stack recipes
Find full stack guides that pair WordPress 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 WordPress should hand the buyer to a branded Plandalf checkout page.
SDK checkout
Use SDK checkout when WordPress 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
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.
Pair it with
Connect WordPress with…
Platforms whose roles complement WordPress inside a Plandalf sequence.
WordPress + ActiveCampaign
Capture form leads on WordPress straight into ActiveCampaign.
WordPress + beehiiv
Capture form leads on WordPress straight into beehiiv.
WordPress + Kit (ConvertKit)
Capture form leads on WordPress straight into Kit (ConvertKit).
WordPress + Customer.io
Capture form leads on WordPress straight into Customer.io.
WordPress + Drip
Capture form leads on WordPress straight into Drip.
WordPress + Flodesk
Capture form leads on WordPress straight into Flodesk.
Integration methods
How WordPress connects to Plandalf
Each method below is the minimum viable setup. Pick the one closest to how you already use WordPress 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 WordPress 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 WordPress integration
Do I need a paid plan to use WordPress with Plandalf?
Plandalf itself is free to connect to WordPress. You only need a WordPress account that allows API access, which is almost every paid plan.
How long does setup take?
Under 10 minutes — paste a webhook URL into WordPress, point it at the Plandalf endpoint, and trigger a test event to confirm.
Can I disconnect WordPress later without losing data?
Yes. Disconnecting only revokes the credentials — historical events Plandalf fired stay in your sequence logs, and WordPress's own records are untouched. You can reconnect any time and resume from the last seen event.
Does Plandalf store WordPress data?
Plandalf stores the minimum IDs needed to address a record in WordPress plus a log of events Plandalf fired. Source-of-truth data stays in WordPress.
What if my website need isn't covered by the actions or triggers listed here?
Drop into the Plandalf REST API and call WordPress directly from your sequence's HTTP action. Anything WordPress's public surface exposes is reachable.
Is there a usage limit?
There's no Plandalf-side limit. WordPress's own plan limits apply.
Where do I find WordPress's own documentation?
WordPress's homepage at https://wordpress.org links to their developer docs. For Plandalf-side questions about the WordPress integration, see the Plandalf docs.