Resources · Make integration

Flodesk Make integrationAutomate Flodesk with Make.

Can Make keep your Flodesk list in sync with the rest of your tools? Yes: the Flodesk Make integration gives you 10 modules, including 1 instant trigger. This page is for creators and small marketing teams, and it walks you from the connection to a first working scenario.

Try the Flodesk integration on MakeSee the 10 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Flodesk Make integration do for you?

The Flodesk Make integration links your Flodesk account to Make so that subscribers and segments move on their own. You build a scenario, the automation made of modules, and each module either reacts to something in Flodesk or changes a subscriber for you. No code is involved: you pick modules and fill their fields.

Every buyer lands in the right segment. When your shop or form tool records a new customer, Create or Update a Subscriber adds the person to Flodesk and Add a Subscriber to Segments places them in the sequence meant for buyers. Nobody copies emails by hand anymore.

Your CRM hears about every unsubscribe. Watch Events is an instant trigger: Flodesk calls Make through a webhook as soon as someone subscribes, joins a segment or unsubscribes. You can pass that news to your CRM or to a shared sheet in the same scenario.

A quick audit of your audience. List Segments and List Subscribers return your segments, or your subscribers filtered by status, so you can copy them into a spreadsheet and review who is still active.

What Make does not do for Flodesk: the listed modules cover subscribers and segments only. For anything else the Flodesk API offers, Make an API Call reuses the same connection. If you are still weighing tools, read the n8n vs Make comparison, check Make pricing, or learn the editor step by step with our Make training.

Connect

How do you connect Flodesk to Make?

  1. 01

    Copy your Flodesk API key

    In Flodesk, open the account settings, click the Integration tab, then the API Key section. Copy the key shown on screen. You need an active Flodesk account; partner integrations use a registered OAuth2 app instead.

  2. 02

    Add a Flodesk module in Make

    In your scenario, add any Flodesk module and click Create a connection. The Connection name field is optional, but a clear name helps when you run several Flodesk accounts.

  3. 03

    Paste the key and save

    Paste the API key, or follow the on-screen instructions, and confirm. This connection is your Flodesk account linked to Make once: every other Flodesk module reuses it without asking again.

First scenario

Your first scenario: send new customers to a Flodesk segment

GoalWhen a new customer appears in another tool, Make creates the subscriber in Flodesk and adds them to your buyers segment.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the +. Pick the module of the tool where your customers show up, such as your shop or your form builder.

  2. 02

    Add Create or Update a Subscriber

    Click the + on the right, search for Flodesk and choose Create or Update a Subscriber. Map the email from the first module. If the person already exists, Flodesk updates them instead of adding a duplicate.

  3. 03

    Place them in a segment

    Add Add a Subscriber to Segments next. Once the connection exists, Make lists your Flodesk segments, so you only pick the buyers segment from the menu.

  4. 04

    Test with Run once

    Click Run once. Each module shows the bundles it received, a bundle being one item passed along, here one customer. Check that the subscriber now sits in the right segment in Flodesk.

  5. 05

    Schedule and switch on

    Set the schedule on the first module, every 15 minutes by default, then switch the scenario on. From now on, each new customer reaches Flodesk without you touching it.

Triggers

What starts a Flodesk scenario

1 module starts a scenario when something happens in Flodesk. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Flodesk as soon as it happens.

Flodesk1Watch Events

Watch Events

Instant trigger

In Make“Triggers when a subscriber is created, added to a segment or unsubscribed.”

Watch Events starts your scenario the moment something changes in your audience: a subscriber is created, joins a segment or unsubscribes. You get one bundle per event, ready for the next module.

How it fires
instant, Flodesk calls Make through a webhook as soon as it happens, so there is no interval to wait for.
When to use it
you want your CRM or support tool to reflect an unsubscribe right away.
Watch out
three kinds of events feed this one trigger, so a scenario meant for new subscribers will also receive unsubscribes. Decide what each event should do before adding actions.
Modules

Every Flodesk module in Make

Flodesk gives you 9 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Flodesk1

Add a Subscriber to Segments

Action

In Make“Adds a subscriber to segments.”

This action drops an existing subscriber into one or several segments, so your audience stays sorted without manual tagging.

When to use it
a client books a call or buys a course and should move to the matching nurture sequence.
Watch out
the subscriber must already exist, so place Create or Update a Subscriber before it when the contact is new.
Flodesk2

Create or Update a Subscriber

Action

In Make“Creates a new subscriber or updates a subscriber by their ID or Email.”

Adds a person to Flodesk, or refreshes their details when Flodesk already knows them by ID or email. One module covers both cases, so you avoid duplicates.

When to use it
a lead fills a form elsewhere and you want them on your list with up to date details.
Watch out
the email you map decides which record gets updated, so map it from a reliable source.
Flodesk3

Get a Segment

Action

In Make“Retrieves the details of a segment by its ID.”

Fetches the details of one segment from its ID, so later modules can use its details instead of a raw identifier.

When to use it
an earlier module hands you a segment ID and your team message should show a readable segment name.
Watch out
it needs the ID, not the name; run List Segments first if you only know the name.
Flodesk4

Get a Subscriber

Action

In Make“Retrieves the details of a subscriber by their ID or Email.”

Looks up one subscriber by ID or email and returns their details, useful to enrich a record before you pass it on.

When to use it
Watch Events tells you someone joined a segment and your CRM needs the full profile.
Watch out
each lookup is one operation, a single run of one module that Make counts on your plan, so avoid calling it when the trigger already gives you what you need.
Flodesk5

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Sends any request the Flodesk API accepts, with the connection you already set up. It covers what the nine other modules leave out.

When to use it
you need a Flodesk feature that has no dedicated module in Make.
Watch out
you write the request yourself from the Flodesk API documentation, so test it with Run once before switching the scenario on.
Flodesk6

Remove a Subscriber from Segments

Action

In Make“Removes a subscriber from segments by their ID or Email.”

Takes a subscriber out of chosen segments by ID or email while keeping them on your list and in every other segment.

When to use it
a prospect becomes a customer and should leave the sales sequence without losing your newsletter.
Watch out
do not confuse it with Unsubscribe a Subscriber, which removes the person from all segments at once.
Flodesk7

Unsubscribe a Subscriber

Action

In Make“Removes a subscriber from all segments by their ID or Email.”

Removes a subscriber from all your segments in one step, found by ID or email. It is the clean way to honor an opt out that arrived in another tool.

When to use it
someone asks your support desk to stop every email.
Watch out
it touches every segment, so keep it out of scenarios where a partial removal would be enough.
Flodesk8

List Segments

Search

In Make“Retrieves a list of all segments.”

Returns every segment in your Flodesk account, one bundle per segment, which gives you a map of how your audience is organized.

When to use it
you want to copy the segment list into a sheet or find the ID of a segment you only know by name.
Watch out
as a search, it can return many bundles, and each module placed after it runs once per segment.
Flodesk9

List Subscribers

Search

In Make“Retrieves a list of subscribers by their status.”

Pulls your subscribers filtered by their status, so you can work on a precise slice of your list rather than the whole audience.

When to use it
you are auditing your list and want every unsubscribed contact exported to a spreadsheet.
Watch out
a large list means many bundles, and every module after this one spends operations on each of them.
Need help

Need help automating Flodesk with Make?

A person reads every message.

FAQ

Flodesk and Make: frequent questions

01Is the Flodesk Make integration free?
Yes, Flodesk is a standard app in Make, so it works on the Free plan. That plan has limits: 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution at most, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute and remove the cap on active scenarios. Your Flodesk subscription is separate and depends on Flodesk itself.
02What do you need to connect Flodesk to Make?
You need an active Flodesk account and an API key, which you copy from the account settings under the Integration tab, in the API Key section. Partner integrations use a registered OAuth2 app instead of a key. In Make, add a Flodesk module, click Create a connection, paste the key and save. If your first module is Watch Events, click Create a webhook before creating the connection. The connection is created once and every Flodesk module of your scenarios reuses it.
03Does the Flodesk Make trigger work in real time?
Yes. Watch Events is an instant trigger: Flodesk calls Make through a webhook as soon as a subscriber is created, added to a segment or unsubscribed, so your scenario starts without waiting for a schedule. It is the only Flodesk trigger in Make. Scenarios that start from another app instead follow the schedule set on their first module, every 15 minutes by default. With Watch Events you never need to adjust the interval, because Flodesk decides when the scenario starts.
04What if the Flodesk module you need is missing in Make?
Use Make an API Call. It sends any request the Flodesk API accepts with the connection you already have, so you are not limited to the nine dedicated modules, which focus on subscribers and segments. You write the request from the Flodesk API documentation and test it with Run once. If the Flodesk API cannot do it either, the task has to happen in another tool of your scenario. Keep in mind that each call counts as one operation, like any other module.
05Should you use Make or n8n for Flodesk?
It depends on the modules you need. In Make, Flodesk comes with 10 modules: an instant trigger, seven actions and two searches, with Make an API Call among the actions to reach the rest of the API, all usable from the Free plan. Before choosing n8n, check whether it offers the same Flodesk operations and whether your team already builds there. Pick the tool where your other apps and your habits already live.
Same platform

Other docs you might need on this stack.

Browse all integrations