Flodesk

Integration

Flodesk

Plandalf integrates with Flodesk as a email, marketing, website, sdk platform.

What it does

Product surfaces

Where Flodesk 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 Flodesk receives checkout, payment, tax, or workflow context.

The Numi offer editor showing layout, product, theme, automation, invoice, and settings controls.
The Numi checkout elements palette showing content, interactive, and selling blocks.
The Numi offer editor automation tab showing sequence controls beside the checkout canvas.

Purchase events can start follow-up

Flodesk should fit into the work after checkout: fulfilment, records, CRM updates, support context, webhooks, and sequences.

The Numi offer editor showing hosted checkout mode controls.

Builder paths

Stack guides that use Flodesk

Use these stack guides when a builder needs the whole path: sales surface, Plandalf offer, payment handoff, automation, fulfilment, records, and downstream integrations.

Overview

Flodesk is a design-first email platform. Its workflow builder is lighter than the Klaviyo / ActiveCampaign tier and doesn’t expose a native webhook action, so promo enrolment routes through Zapier for most users.

What Plandalf does here

  • Countdown in emails — works in HTML blocks; personalisation depends on the plan’s merge-tag support.
  • Zapier-bridged enrolment — the New Subscriber trigger feeds a Webhooks-by-Zapier POST to the promo’s catch URL.

Setup templates

Drop-in implementations

Copy-paste setups for the most common ways to wire Flodesk into Plandalf.

promo · email

Drop the Plandalf countdown image into a Flodesk email

Paste this <img> tag into an HTML block in your Flodesk email. Flodesk doesn't expose a raw email-address merge tag in all plans — if yours supports {{ email }} personalisation, use that; otherwise drop the ?ref= parameter and Plandalf will fall back to an anonymous deadline per visitor.

<img
  src="{{ promo.countdown_url }}?ref={{ email }}"
  alt="Time remaining on this offer"
/>

promo · automation

Enrol Flodesk subscribers via Zapier

Flodesk's built-in workflow actions don't include a webhook step, so the cleanest bridge is Zapier (see the Zapier tab). A typical Zap:

  1. Trigger: Flodesk → New Subscriber.
  2. Filter (optional): only when the subscriber is added to the segment you want to enrol into the promo.
  3. Action: Webhooks by Zapier → POST to:
    {{ promo.catch_url }}
    
    with body {"email": "{{trigger.email}}", "ref": "{{trigger.email}}"}.

Automation graph

Connecting Flodesk

How Flodesk participates in Plandalf sequences: what events it exposes upward, and what actions Plandalf can perform on it.

Triggers from Flodesk

Events Plandalf can subscribe to through webhooks, API work, checkout state, payment context, and connected integrations.

flodesk.subscriber_added
Fires when a new subscriber is added to Flodesk.
flodesk.automation_step_reached
Fires when a contact reaches a designated step in a Flodesk automation.
flodesk.form_submitted
Fires when a form on Flodesk is submitted.
flodesk.webhook
Fires when Flodesk POSTs to a Plandalf webhook URL — use for anything not covered by a native trigger.

Actions on Flodesk

Things Plandalf sequences can do after checkout, payment, invoice, customer, or deadline events.

flodesk.add_subscriber
Add a contact to a list or audience in Flodesk.
flodesk.tag
Apply a tag or segment to an existing Flodesk contact.
flodesk.send_email
Send a one-off transactional or broadcast email through Flodesk.
flodesk.start_automation
Enrol a contact into a Flodesk automation.
flodesk.custom_api_call
Hit any Flodesk REST endpoint with a templated payload.

Embeddable surfaces: Plandalf countdown image and buy button HTML · Per-recipient countdown GIF with merge-tag substitution

Example sequence
trigger: stripe.payment_succeeded
actions:
  - flodesk.add_subscriber:
      list: paying-customers
      tag: tier-${plan}
  - plandalf.grant_entitlement: ${product_slug}

Integration methods

How Flodesk connects to Plandalf

Each method below is the minimum viable setup. Pick the one closest to how you already use Flodesk with checkout, payments, invoices, webhooks, API work, SDK checkout, and integrations.

  1. Method 1

    Embed a Plandalf buy button

    Drop the Plandalf embed script into a Flodesk 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>
  2. Method 2

    Drop in a per-recipient countdown image

    Add an HTML block to any Flodesk email and paste the Plandalf countdown URL. Flodesk's merge tag `{{ email }}` substitutes per recipient so each subscriber sees a timer pegged to their own deadline.

    <img
      src="https://cdn.plandalf.com/timers/{TIMER_ID}.gif?ref={{ email }}"
      alt="Time remaining on this offer"
      width="600"
      height="120"
    />
  3. Method 3

    Trigger a sequence from a form

    Point a Flodesk form's webhook / POST URL at Plandalf's intake endpoint and every submission starts whatever sequence you've mapped to it.

    curl -X POST https://api.plandalf.com/v1/intake/flodesk \
      -H "Content-Type: application/json" \
      -d '{"email": "{{ form.email }}", "source": "flodesk"}'
  4. Method 4

    Enrol from an automation step

    Inside Flodesk's automation builder, add a Webhook step that POSTs the contact to a Plandalf sequence catch URL. Use this to mirror Flodesk journey logic into Plandalf without re-building the segmentation.

    {
      "email": "{{ contact.email }}",
      "sequence": "post-signup-onboarding",
      "source": "flodesk"
    }
  5. Method 5

    REST API webhook

    For anything not covered by a native trigger, configure a Flodesk webhook to POST to Plandalf. The payload is forwarded into the sequence as `${event}`.

    curl -X POST https://api.plandalf.com/v1/webhooks/flodesk \
      -H "Authorization: Bearer $PLANDALF_API_KEY" \
      -H "Content-Type: application/json" \
      -d @event.json
Official Flodesk docs and sign-up: flodesk.com

FAQ

Common questions about the Flodesk integration

Do I need a paid plan to use Flodesk with Plandalf?

Plandalf itself is free to connect. Flodesk's native webhook step is on its paid tiers — on the free plan, route the trigger through Zapier instead, which still works end-to-end.

How long does setup take?

Under 10 minutes. OAuth (or paste an API key), pick the lists/segments you care about, and you're live. No code unless you want it.

Can I disconnect Flodesk later without losing data?

Yes. Disconnecting only revokes the credentials — historical events Plandalf fired stay in your sequence logs, and Flodesk's own records are untouched. You can reconnect any time and resume from the last seen event.

Does Plandalf store Flodesk data?

Plandalf stores the Flodesk contact ID and the events Plandalf fired against that contact. Email content stays in Flodesk; Plandalf doesn't mirror your audience or newsletter archive.

What if my email need isn't covered by the actions or triggers listed here?

Use the generic `flodesk.custom_api_call` action or the inbound `flodesk.webhook` trigger. Anything Flodesk's REST API can do, a Plandalf sequence can drive.

Is there a usage limit?

Plandalf respects Flodesk's API rate limits and backs off on 429s. For very high-volume use cases, ask about a dedicated worker pool.

Where do I find Flodesk's own documentation?

Flodesk's homepage at https://flodesk.com links to their developer docs. For Plandalf-side questions about the Flodesk integration, see the Plandalf docs.

Feature detail