Newsletter writer selling a template kit
A creator who writes in Flodesk sells a kit in a Plandalf checkout, then sends a delivery email from a workflow that starts when the buyer joins a segment.
Native on one side, webhook on the other
Stripe takes the payment in a Plandalf checkout, and a Send Webhook step can add the buyer to a Flodesk segment so a workflow emails them.
No credit card required. No coding required.
FlodeskPlandalf has no Flodesk steps and does not sync Stripe buyers into Flodesk. Flodesk Checkout is its own product with its own Stripe connection, so a Plandalf sale will not fire its purchase trigger. A Send Webhook step can call Flodesk's API to add the buyer to a segment, and that segment can start a Flodesk workflow.
| Event | From and to | Through | What happens |
|---|---|---|---|
| Checkout completed | Plandalf (paid via Stripe) → Flodesk | Webhook | Send Webhook posts to Flodesk's subscribers endpoint with the buyer's email, name and a segment ID. Flodesk creates or updates the subscriber and places them in the segment. |
| Buyer added to the segment | Flodesk segment → Flodesk workflow | By hand | Adding the buyer to a segment starts any Flodesk workflow whose trigger is Added to segment. Flodesk's Makes a purchase trigger is limited to Flodesk Checkout, Shopify, Squarespace, Wix and ThriveCart. |
| Subscriber created or added to segment | Flodesk → Plandalf | Webhook | Flodesk's API lists webhook events for a new subscriber, a segment join and an unsubscribe. One of them can be pointed at a Plandalf catch URL to start a sequence such as Enroll in Promo. Check Flodesk's developer docs for how to register the webhook. |
| Flodesk Checkout sale | Flodesk → Stripe | By hand | Flodesk Checkout runs its own sales through a Stripe account kept separate from your other Stripe activity, so those sales never pass through Plandalf. |
You need a published Plandalf checkout on Stripe, a Flodesk API key, and a segment to receive buyers.
Create a Customers segment in Flodesk and note its ID, and create an API key. Flodesk's developer docs say private integrations send the key as the username in a Basic authentication header, with an empty password.
Basic authentication needs your key followed by a colon, encoded as base64. Encode it on your own machine and keep the result for the next step. Never post the key in a public place.
In Plandalf go to Automation, then My Sequences. Choose Plandalf, Checkout Completed, pick the offer and choose a recent checkout as the sample on the Test tab.
Choose Plandalf, Send Webhook. Set POST, the Flodesk subscribers URL and an Authorization header holding Basic and the encoded value.
Send JSON with email as {{trigger.customer_email}}, first_name as {{trigger.customer_first_name}}, last_name as {{trigger.customer_last_name}} and segment_ids as a list holding your segment ID.
Switch on Run on test purchases, buy with a Stripe test card and read the run in the Events view. Then create the Flodesk workflow with the Added to segment trigger.
A creator who writes in Flodesk sells a kit in a Plandalf checkout, then sends a delivery email from a workflow that starts when the buyer joins a segment.
A seller runs a simple opt-in product in Flodesk Checkout and the higher-priced bundle in Plandalf with bumps and upsells, then merges both buyer lists in Flodesk segments.
When a subscriber joins a segment, a Flodesk webhook event reaches a Plandalf catch URL and starts their personal deadline.
Checked October 26, 2026 against Plandalf's own setup guides and the vendor documentation: Flodesk Help Center: what is Flodesk Checkout, Flodesk Help Center: Stripe FAQs, Flodesk Help Center: triggers 101, Flodesk developers: API.