Flodesk

Manage your Flodesk email list from your workflows. Agents create or update subscribers, add them to segments, remove them when they churn, and read segment membership to drive targeted sends.

6 actions Basic auth available

Flodesk website ↗ Platform Documentation ↗ Capability data verified 2026-07-27

A new customer completes their first purchase in the storefront

Get Subscriber checks whether the email already exists in the Flodesk audience

Create or Update Subscriber upserts the record with name and purchase-related custom fields

The agent determines which segments the customer now qualifies for based on what they bought

The list owner approves segment placement when the target segment feeds an active email sequence

Add To Segments places the subscriber into the approved segments

The day's audience changes post to the team channel as a digest

What This Integration Enables

Flodesk is deliberately simple: subscribers, segments, and beautiful sends, with flat pricing that does not punish list growth. That simplicity puts all the leverage in one place, segment membership, because segments are what target the sends and feed the automated sequences. Keeping membership honest as customers act is exactly the continuous work FlowRunner agents are for. They upsert subscribers from stores, forms, and CRMs, move people between segments as behavior changes, and read membership back out for reporting and cross-platform sync. - Sync new customers and leads from your store, forms, and CRM into the audience - Upsert names and custom fields whenever contact details change anywhere - Route subscribers into the right segments automatically as they qualify - Remove subscribers from segments they no longer match - Export subscribers and segments to spreadsheets or a second platform in sync The upsert-by-email model is worth dwelling on, because it is what makes continuous sync safe. Create or Update Subscriber cannot mint a duplicate: the same customer arriving from the storefront, a form, and the CRM converges on one record, with each source contributing the fields it knows. Custom fields carry the operational detail, purchase dates, product categories, lifecycle markers, that turn a flat email list into something segments can actually reason about. And because the connector reads as well as it writes, membership flows back out for reporting instead of living only inside Flodesk. Because a segment can be the front door to an automated sequence, FlowRunner's [human-in-the-loop](/concepts/human-in-the-loop) gate watches the placements that trigger real email. Quiet segments move at machine speed; live ones wait for the owner's yes.

Without FlowRunner

The audience trails the business Customers buy, subscribe, and churn all week, and the Flodesk list catches up whenever someone imports

Segments go stale Membership reflects who people were at signup, not what they have done since

Two platforms, two truths The store knows one version of a customer, the email list another, and nobody reconciles them

With FlowRunner

Every event updates the audience Purchases, form fills, and profile changes upsert subscribers within the same workflow run, every time

Segments reflect behavior Agents move subscribers between segments as their actual activity changes

One customer, everywhere The same record flows to Flodesk, the spreadsheet, and any second platform in sync

Use Case Scenarios

Customers who join the audience the moment they buy

A [Shopify](/integrations/shopify) customer checks out. The agent calls Create or Update Subscriber matched on email, writing first name, last name, and custom fields like first purchase date and product category. Add To Segments then places them in the customers segment and the category segment their purchase qualifies them for. The welcome sequence tied to that segment does the rest. Time from checkout to correctly-segmented subscriber: one workflow run, with no import step for anyone to forget during a busy launch week.

Form fills routed to the right list, not just a list

Responses arrive from a [Typeform](/integrations/typeform) lead magnet. For each respondent, the agent upserts the subscriber, then reads their answers to pick segments: the freelancer answer routes to one nurture segment, the agency answer to another. Add To Segments applies the whole routing in a single call, up to fifty segments at once if the answers warrant it. The lead magnet stops feeding one undifferentiated list and starts feeding the audiences the sends were designed for, which is the difference the open rates eventually show.

The audience report and the second platform

Weekly, the agent resolves the segments worth tracking with List Segments, then walks List Subscribers page by page for each one, appending rows to [Google Sheets](/integrations/google-sheets) so the team sees segment sizes trend over time. The same pass mirrors records into [Klaviyo](/integrations/klaviyo) for the brand that runs both platforms, so neither list drifts from the other. When a subscriber stops matching a segment's criteria, Remove From Segment trims them without touching the rest of their memberships, so the trend lines in the sheet reflect a list that is actually being maintained.

Human-in-Loop Highlight

Add To Segments looks administrative, but in Flodesk a segment is frequently wired to an automated sequence, which means placement is a send decision. Add three hundred imported contacts to the wrong segment and the welcome sequence starts delivering to all of them within minutes, and there is no recalling email. So FlowRunner agents distinguish between quiet segments and live ones. Placements into reporting-only segments flow straight through. Placements into any segment that fronts an active sequence, especially in bulk, get staged: the agent posts the subscriber list, the target segment, and the sequence it will trigger, and the list owner approves before the call fires. The upserts happen at machine speed. The decision to start email landing in inboxes stays human.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via email

Human decides

Agent resumes with decision

Agent Capabilities

6 actions

Subscribers

List Subscribers Retrieves subscribers with pagination, optionally filtered to a single segment. The read behind audience reports and cross-platform sync.
Get Subscriber Retrieves one subscriber by ID or email, returning name, status, custom fields, and segment memberships. The lookup before any update or routing decision.
Create or Update Subscriber Upserts a subscriber matched on email, setting first name, last name, and existing custom fields as key/value pairs. The default write for every sync workflow, because it cannot create a duplicate.

Segments

Add To Segments Adds a subscriber to one or more segments, up to fifty per request, without disturbing existing memberships. The placement that can trigger a live sequence, and the reason this page's human gate exists.
Remove From Segment Removes a subscriber from a single segment without deleting them or touching other memberships. The trim that keeps segments honest.
List Segments Retrieves the account's segments with pagination. Used to resolve segment IDs before placement, removal, or filtered listing.

Frequently Asked Questions

What can FlowRunner do with Flodesk?

FlowRunner agents can run List Subscribers, Get Subscriber, and Create or Update Subscriber in Flodesk, plus 3 more actions.

Does connecting Flodesk to FlowRunner require OAuth?

No. Flodesk connects to FlowRunner with basic authentication (a username and password), no OAuth flow required.

Can Flodesk trigger a FlowRunner workflow automatically?

Flodesk doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Flodesk

$100 in credits. No card required. Connect in minutes.

Start Building Free Talk to us