Paid templates sold from a creator's site
A designer sells a template pack from a WordPress page and keeps a free Flodesk form in the footer. Pack buyers go into a Customers segment, which can receive launch emails the free list does not.

Checkout embed
Flodesk forms collect subscribers on your WordPress site. A Plandalf button on the same site adds paid buyers to Flodesk through Send Webhook.
No credit card required. No coding required.
WordPress
FlodeskPlandalf has no native Flodesk step. WordPress hosts a Plandalf button in a Custom HTML block, and a Plandalf sequence then writes the buyer into Flodesk with Send Webhook or Zapier, using Flodesk's subscriber API. Flodesk forms on the same page are Flodesk's own embed code and are separate from Plandalf.
| Event | From and to | Through | What happens |
|---|---|---|---|
| Checkout opened from a WordPress page | WordPress → Plandalf | The button and SDK go in a Custom HTML block or the theme footer. The payment is taken by your Stripe or PayPal account. | |
| Checkout completed | Plandalf (paid via Stripe) → Flodesk | Webhook | Send Webhook POSTs to Flodesk's create-or-update subscriber endpoint. The reference needs an email or an id, and authenticates with an API key as the username of HTTP Basic auth. |
| Checkout completed | Plandalf (paid via Stripe) → Flodesk | Webhook | A second Send Webhook can add the buyer to a Flodesk workflow. The reference notes that abandoned cart workflows cannot be used with that endpoint. |
| Upsell accepted | Plandalf (paid via Stripe) → Flodesk | Webhook | Add the subscriber to a segment named for the upgrade, using the add-to-segments endpoint. |
| New subscriber | Flodesk → Plandalf | Zapier or Make | Plandalf's Flodesk page uses Zapier: a Flodesk new-subscriber trigger sends the email to a Plandalf catch URL, which can run Enroll in Promo. |
You need a WordPress login that can insert JavaScript, a published Plandalf offer and a Flodesk account where you can create an API key.
Create or edit the page in the Code editor or a Custom HTML block, and add the SDK script and a button with data-plandalf-present set to your offer slug. Save the draft and confirm WordPress kept the script.
Flodesk's embed article says a form needs its header code in the page head and, for inline forms, its form code where the form shows. Plandalf's script is a separate tag, so check both load on the published page.
Flodesk's developer docs say keys are made in Account settings on the API page and sent as the username in HTTP Basic auth with an empty password. Base64-encode the key followed by a colon for the header.
In Plandalf open Automation, then My Sequences. Choose Plandalf, Checkout Completed and the offer, then choose a recent checkout as the sample on the Test tab.
Add Send Webhook, POST, https://api.flodesk.com/v1/subscribers, with the Authorization header and a payload holding email as {{trigger.customer_email}}. Add name fields using the names in Flodesk's subscriber reference.
Add a second Send Webhook for the segment. Turn on Run on test purchases, buy with your own email, and check Flodesk. For refunds, build a sequence on Invoice Refunded that calls the remove-from-segments endpoint with DELETE.
A designer sells a template pack from a WordPress page and keeps a free Flodesk form in the footer. Pack buyers go into a Customers segment, which can receive launch emails the free list does not.
A photographer takes a deposit for a session through a Plandalf offer on the WordPress site. The paid client is added to a workflow with the prep guide and the shoot-day reminder.
Checked October 26, 2026 against Plandalf's own setup guides and the vendor documentation: Flodesk help: How to add a Flodesk opt-in form to your website, Flodesk developer documentation.