Resources · Make integration

Flow XO Make integrationAutomate Flow XO with Make.

Got data leaving Flow XO and nowhere good to put it? The Flow XO Make integration gives you 1 instant trigger that catches that data the moment it arrives. This guide walks a Make beginner from connection to a live first scenario.

Try the Flow XO integration on MakeSee the 1 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Flow XO Make integration do for you?

The Flow XO Make integration is a single listening point. Flow XO posts data to a webhook (a private web address Make gives you), and Make starts a scenario, the automation you build as a chain of modules, with that data. Everything after that first step comes from other apps you add.

Think of Watch Custom Data as the front door. What happens behind it is your call. A sales team could push each piece of data it receives into a lead sheet. A support desk could turn it into an alert for whoever is on duty. An operations manager could file it in a database so nothing gets retyped by hand.

In each case, Flow XO only hands the data over. The storing, the alerting and the filing are done by modules of other apps, placed after the trigger. Each module is one brick of the scenario, and each item that travels between them is called a bundle (one record, one contact, one row).

Be clear about the limits. The Make catalog lists 1 module for Flow XO and nothing else: no action to send something back into Flow XO, no search, and no Make an API Call module to reach the rest of its API. If your plan needs Make to write into Flow XO, this app will not cover it.

If you are weighing tools, the same app also has an n8n page: the Flow XO n8n integration describes that side, and n8n vs Make sets the two editors side by side. New to the editor itself? Make training starts from zero.

Connect

How do you connect your Flow XO account to Make?

  1. 01

    Add the Flow XO module

    In a new scenario, click the + and type Flow XO in the search box. Pick Watch Custom Data, then click Create a connection. A connection is your Flow XO account linked to Make one time and reused afterwards.

  2. 02

    Name it so you can find it

    Make offers a name field for the connection. It is optional, yet worth filling if several people or several Flow XO accounts share the same Make workspace. A clear name saves guessing later when you pick it from a list.

  3. 03

    Authorize and save

    Depending on what Make shows, either approve access on the Flow XO page that opens, or paste the key Flow XO gives you. Then click Save. The connection now appears in the module and you can move on to its settings.

First scenario

Build your first scenario with Flow XO

GoalWhen Flow XO sends data to its webhook, Make passes that data to the next app you choose.

  1. 01

    Create the scenario

    Open the Scenarios page in Make, create a new scenario, and click the +. That empty circle is where your first module, the trigger, will sit.

  2. 02

    Place the Flow XO trigger

    Search for Flow XO, choose Watch Custom Data and attach the connection you just made. The lightning badge on the circle tells you this trigger is instant rather than checked on a clock.

  3. 03

    Add the app that receives the data

    Click the + on the right of the Flow XO module and pick the app where the data should land. Map the values the trigger delivers into that module's fields, one by one.

  4. 04

    Test with Run once

    Click Run once, then send some data from Flow XO. Look at the bundles each module received and confirm the mapping put every value where you expected.

  5. 05

    Switch it on

    Switch the scenario on in the editor. From then on, every time Flow XO posts data, the scenario runs by itself without you opening Make.

Triggers

What starts the scenario

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

Flow XO1Watch Custom Data

Watch Custom Data

Instant trigger

In Make“Triggers when data send to webhook URL.”

This is the one entry point Flow XO offers in Make. It gives you a webhook address, and each batch of data Flow XO sends there becomes a bundle that the rest of your scenario can use.

How it fires
instant, meaning Flow XO calls Make through a webhook as soon as it happens, so there is no clock to set.
When to use it
any time you want information collected in Flow XO to end up in another tool without copying it over yourself.
Watch out
Make counts an operation, one run of one module on one bundle, for every delivery, so a busy flow eats your plan faster than you might expect.
Need help

Need help automating Flow XO with Make?

A person reads every message.

FAQ

Questions people ask next

01Is the Flow XO Make integration free?
Yes, Flow XO is a standard app in Make, so you can use it on the Free plan. That plan has its own ceilings: 2 active scenarios, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) remove the cap on active scenarios and allow 40 minutes of execution. Usage is counted in credits, which are operations, each month. This page gives no price for Flow XO itself or for Make, because the only honest source for that is each vendor's own pricing page.
02What does it take to connect Flow XO to Make?
A Flow XO account and a Make account, nothing else that the catalog mentions. There is no official Make doc for Flow XO, so no special prerequisite is listed either. The steps are Make's usual ones: add the Watch Custom Data module, click Create a connection, optionally give it a name, then approve access on the Flow XO side or paste the key Flow XO provides, and save. That connection is stored once and reused by the module every time the scenario runs, so you do this only one time per account.
03Does the Flow XO trigger react in real time?
Yes. Watch Custom Data is an instant trigger, marked with a lightning badge in the editor. Flow XO calls Make through a webhook as soon as data is sent, and the scenario starts right away instead of waiting for a schedule. That is different from scheduled triggers, which Make checks on a clock, every 15 minutes by default for a new scenario. The one condition is that the scenario must be switched on. While it is off, Make is not listening for anything Flow XO sends.
04What if a Flow XO module is missing in Make?
It depends on what you are after. Make lists exactly 1 module for Flow XO, the Watch Custom Data trigger, and there is no Make an API Call module for this app. So if you need Make to send data back into Flow XO or look something up there, Make cannot do it through this integration. Everything else, storing, alerting, enriching, happens in modules of other apps placed after the trigger. If your case falls outside that, the team behind this page can look at it with you through the help form below.
05Make or n8n for Flow XO: which one fits?
It depends on how you like to build. On Make, Flow XO comes down to one instant trigger, available on the Free plan, with a visual editor where each module is a circle you drag and connect. The same app also has an n8n node, which this site covers on a separate page. Neither is ranked here, and no pricing or speed comparison is made. The fair way to choose is to check that the tool can do the exact step you need, then pick the editor your team is most comfortable maintaining.
Same platform

Other docs you might need on this stack.

Browse all integrations