Native on one side, webhook on the other

Stripe + Flodesk integration

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.

Does Stripe integrate with Flodesk?

Plandalf 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.

What moves between Stripe and Flodesk

EventFrom and toThroughWhat happens
Checkout completedPlandalf (paid via Stripe)FlodeskWebhookSend 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 segmentFlodesk segmentFlodesk workflowBy handAdding 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 segmentFlodeskPlandalfWebhookFlodesk'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 saleFlodeskStripeBy handFlodesk Checkout runs its own sales through a Stripe account kept separate from your other Stripe activity, so those sales never pass through Plandalf.

Put each Plandalf buyer into a Flodesk segment

You need a published Plandalf checkout on Stripe, a Flodesk API key, and a segment to receive buyers.

  1. Get the segment ID and API key

    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.

  2. Encode the header once

    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.

  3. Build the sequence

    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.

  4. Add Send Webhook

    Choose Plandalf, Send Webhook. Set POST, the Flodesk subscribers URL and an Authorization header holding Basic and the encoded value.

  5. Write the body

    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.

  6. Rehearse and build the workflow

    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.

What sellers do with Stripe and Flodesk

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.

Separate Flodesk Checkout and Plandalf offers

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.

Launch countdown for subscribers

When a subscriber joins a segment, a Flodesk webhook event reaches a Plandalf catch URL and starts their personal deadline.

Limits and gotchas

  • Flodesk's workflow triggers as documented are Added to segment, Submits an opt-in form, Makes a purchase and Abandons a cart. The article mentions no webhook action, so Flodesk cannot call Plandalf from a workflow step.
  • Flodesk's Makes a purchase and Abandons a cart triggers do not cover Plandalf. Use a segment as the trigger instead.
  • The Flodesk subscriber call is limited to 100 requests a minute by default and answers HTTP 429 when exceeded. A busy launch can hit it.
  • Flodesk Checkout sales are managed separately from your other Stripe payments, so reports and refunds for Flodesk Checkout and Plandalf live in different places.
  • Plandalf's Send Webhook posts JSON and keeps no promise of retries. If Flodesk rejects a call, fix the cause and re-run the step from the Events view.

Stripe and Flodesk: common questions

Does Stripe integrate with Flodesk?
Flodesk Checkout runs its payments through Stripe, using a Stripe account Flodesk keeps separate from your other activity. Plandalf is a different checkout that charges your own connected Stripe account.
How do I connect Stripe to Flodesk?
For Flodesk Checkout, Stripe is connected when you first publish a checkout. For Plandalf sales, connect Stripe to Plandalf and add a Send Webhook step that adds the buyer to a Flodesk segment.
Can Plandalf add buyers to Flodesk?
Yes, through the Flodesk API from a Send Webhook step. Plandalf has no Flodesk app, so you supply the API header, the segment ID and the JSON body.
Will a Plandalf purchase trigger Flodesk's Makes a purchase workflow?
No. That trigger is limited to specific sellers. Start the workflow from a segment that your webhook step adds the buyer to.

Feature detail