Resources · Make integration

Flaree Make integrationAutomate Flaree with Make.

Can another tool send a Flaree for you? Yes. The Flaree Make integration gives you 2 action modules, one to send a Flaree and one to call the Flaree API directly. This guide is for HR and ops teams, and it walks you from the API key to a live scenario.

Try the Flaree integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Flaree Make integration do for your team?

The Flaree Make integration lets a scenario, the automation you build in Make, send a Flaree between users of your organization without anyone opening Flaree. The app has no trigger, so the start signal always comes from somewhere else: another app, or a schedule you set in Make.

A Flaree when a form comes in. A form tool catches a submission, and the Send a Flaree module passes it on to the right person in your organization. The same pattern works with any app that can start a scenario, like the one on the 123FormBuilder Make integration page.

A Flaree when a record changes. Your CRM or project tool starts the scenario, Make maps the details into the module, and the Flaree lands with context instead of a blank message.

Anything else through the API. Make an API Call reaches any endpoint of the Flaree API with the same connection, for the cases the send module does not cover.

What Make cannot do here: watch Flaree for new activity. There is no trigger module, so Flaree never starts a scenario on its own. The official doc also warns that its content was generated with AI, so check anything important with Flaree directly. Wondering whether Make is the right fit at all? Read the n8n vs Make comparison, and when a run fails, the Make troubleshooting guide is the place to start.

Connect

How do you connect Flaree to Make?

  1. 01

    Generate an API key in Flaree

    Log in to Flaree, open the Settings tab, then the API Key section. Click Generate API Key, give the key a name you will recognize later, and copy it right away.

  2. 02

    Add a Flaree module in Make

    In your scenario, add a Flaree module and click Create a connection. A connection is your Flaree account linked to Make once, then reused by every Flaree module. The Connection name field is optional.

  3. 03

    Paste the key and save

    Paste the API key you copied from Flaree, or follow the instructions Make shows on screen, and save. The connection now appears in the module, ready for your first test.

First scenario

Your first scenario with Flaree

GoalWhen a new entry arrives in another app, Make sends a Flaree to the right colleague.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + to add the first module. Since Flaree has no trigger, pick the app where the event happens, such as your form tool or CRM.

  2. 02

    Add Send a Flaree

    Click the + on the right of that first module, search for Flaree, and pick Send a Flaree. Choose the connection you created, or click Create a connection if this is your first Flaree module.

  3. 03

    Map the data

    Fill the module fields with data from the first module. Each item passed along is a bundle: one form entry, one contact. Mapping a name or a detail from it makes each Flaree specific.

  4. 04

    Test with Run once

    Click Run once to run the scenario one time. Open the bubble above each module to read the bundles it received, and check in Flaree that the message reached the right person.

  5. 05

    Schedule and switch on

    Set the schedule on the first module, every 15 minutes by default, then switch the scenario on. Each module run on one bundle counts as one operation on your Make plan.

Modules

What Flaree can do in Make

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

Flaree1

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

This module opens the whole Flaree API to your scenario, reusing the connection you already set up, so you never have to handle the key twice.

When to use it
you need an endpoint that Send a Flaree does not cover, and you would rather stay in one scenario than wait for a dedicated module.
Watch out
you describe the request yourself, so keep the Flaree API documentation open while you build it.
Flaree2

Send a Flaree

Action

In Make“Send Flaree between users in your organization in Flaree platform.”

Here is the heart of the integration: a Flaree goes from one user of your organization to another, triggered by whatever event starts the scenario, with nobody typing it by hand.

When to use it
an event in another app deserves a message to a colleague, like a completed form or an updated record in your CRM.
Watch out
every run sends a real Flaree, so point your Run once test at a colleague who expects it.
Need help

Need help automating Flaree with Make?

A person reads every message.

FAQ

Flaree and Make: common questions

01Is the Flaree Make integration free?
Yes, on the Make side. Flaree is a standard app, so it works from the Free plan. That plan gives you 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) lower the interval to 1 minute and count usage in credits each month. You still need an active Flaree account, which follows Flaree's own pricing.
02What do you need to connect Flaree to Make?
An active Flaree account and an API key. You generate the key in Flaree from the Settings tab, in the API Key section, with the Generate API Key button, then give it a name and copy it. In Make, you add a Flaree module, click Create a connection, and paste that key. The connection name is optional. Once saved, the same connection serves both Flaree modules, including Make an API Call.
03Does the Flaree integration react in real time?
It depends on what starts the scenario, because Flaree has no trigger module of its own. Put a trigger from another app first: if that app offers an instant trigger, it calls Make through a webhook as soon as something happens, and the Flaree goes out right after. If you use a scheduled trigger or a plain schedule instead, Make runs the scenario at the interval you set, every 15 minutes by default, or 1 minute at best on a paid plan.
04What if the Flaree module you need is missing?
Use Make an API Call. With the same connection, it can reach any endpoint of the Flaree API, so the lack of a dedicated module does not block you. You write the request yourself, which takes a look at the Flaree API documentation. Keep in mind that the Make doc for Flaree states it was generated with AI and may contain mistakes, so confirm important details with Flaree before relying on them in production.
05Should you use Make or n8n for Flaree?
It depends on the tool your team already uses. On Make, Flaree comes with 2 modules: Send a Flaree for the common case and Make an API Call for the rest, both on the same connection. The same app often has an n8n node as well, so check what exists there before you choose. Pick the platform where your other automations live, so the whole team maintains one set of scenarios.
Same platform

Other docs you might need on this stack.

Browse all integrations