Marketing Automation · Integration
Flodesk
Add Flodesk to your product for your customers, and give your AI agents governed access to it.
Flodesk is built around a very short list of nouns, and an integration that respects that is far simpler than one that fights it. There are subscribers, the segments they sit in, and custom fields defined on the account. Workflows are started by segment membership rather than by a call of their own, which is the single most useful thing to know about it: to enrol somebody you add them to the segment the workflow watches, and to take them out you remove them from it. Subscriber writes are upserts on email, so one request creates or updates. Status deserves care, because an unsubscribed subscriber stays in the account and putting them back into a segment does not resurrect their consent. The API is available on every Flodesk plan and each customer creates their own key, so what your product sends comes off their account rather than a shared one.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each customer connect their own Flodesk account so emails send under their brand and against their own sending limits.
Upsert a subscriber on email so a signup from two places in your product does not create two people.
Add a subscriber to a segment to enrol them in the workflow that segment feeds, and remove them from it to take them out.
Read the account's custom fields first, so a value your product writes lands in a field that customer actually defined.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent adds a subscriber to the right segment after a qualifying event, with the segment recorded on the call.
An agent reports which segments a person belongs to and therefore which emails they are due.
An agent removes somebody from a nurture segment once they convert, so the sequence stops.
Example prompt
Move this customer out of the trial nurture segment into the onboarding one, and tell me what that changes for them.
Set up Flodesk in 4 steps
- 01Enable the Flodesk connector in your fastn dashboard.
- 02Have each customer create their own API key, so subscribers and sends stay in the account they own.
- 03Map the account's custom fields and decide which segment each of your product's events adds to or removes from.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the Flodesk integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Flodesk integration without building it. Your customers connect their own Flodesk account inside your product and work their campaigns, segments and subscribers there, with no per-customer code on your side.
- Handle the part that actually costs time: engagement data arrives as a high-volume event stream, so ordering and deduplication matter. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Flodesk update is not your on-call problem.
- One integration serves your product and your agents. The same governed Flodesk connection powers in-product features and gives AI agents scoped, audited access, so you trigger and measure campaigns from inside your product without wiring it twice.
Used by these teams
Compare with
Kit
Constant Contact
MailerLiteOften used alongside
Tools the same teams tend to run next to Flodesk, across other categories.
Salesforce
HubSpot
Pipedrive
Zoho CRMFlodesk integration FAQ
How do I add a Flodesk integration to my product?
Enable the Flodesk connector in your fastn dashboard, then let each customer authenticate their own Flodesk account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Flodesk client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Flodesk account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Flodesk account and only ever sees their own campaigns, segments and subscribers. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Flodesk integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent adds a subscriber to the right segment after a qualifying event, with the segment recorded on the call.
Who maintains the Flodesk integration?
fastn does. When Flodesk changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Can I trigger a Flodesk campaign from an event in my product?
Yes. Product events can start a campaign, add a contact to a segment, or enrol someone in a journey, so lifecycle messaging follows what a user actually did rather than a nightly export.
Can I read engagement results back from Flodesk?
Yes. Results come back scoped per tenant, so your product can act on them without one customer's data mixing with another's. What you get depends on the channel: opens, clicks, bounces and unsubscribes where there are sends, and impressions, spend and conversions where there are campaigns.
What can I build with the Flodesk integration?
A common starting point: let each customer connect their own Flodesk account so emails send under their brand and against their own sending limits. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Flodesk integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Flodesk does not change your per-connector cost. You can start free with 3 connected accounts.
Add Flodesk to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.