Resources · Make integration

Flock Make integrationAutomate Flock with Make.

Want a teammate to hear about it in Flock when something happens in another tool? The Flock Make integration gives you 2 action modules: one sends a message to a user, the other calls the Flock API directly. This guide connects your account and walks you through a first scenario.

Try the Flock integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Flock Make integration do for you?

The Flock Make integration links your Flock account to Make so a scenario, the automation you build in Make, can send messages in Flock for you. Flock has no trigger in Make, so something else starts the flow: another app's event or a schedule you set, and Flock receives the result as a message.

A heads-up for the person who owns the task. A form entry, a new row in a table or a signed booking lands in another app, and Send a Message tells the right teammate in Flock, with the details mapped from that first app. For example, the Airtable Make integration can supply the record.

A status note sent on a schedule. With no event to wait for, the scenario can simply run on its schedule and post the same reminder or summary to one user, built from data Make just read elsewhere.

Anything the listed module does not cover. Make an API Call reaches any endpoint of the Flock API with the same connection, so a need beyond sending a message is still possible if you are comfortable reading API docs.

What Make does not offer here: a way to react to a message arriving in Flock, since the app has no trigger. The Make documentation for Flock also warns that it was AI-generated from Flock's own docs, so double-check anything important with Flock. If you also use n8n, the same app often has a node there; the n8n vs Make comparison lays out how the two tools differ, and our Make training covers the basics step by step.

Connect

How do you connect Flock to Make?

  1. 01

    Generate an API token in Flock

    You need a Flock account and an API token. Once logged in to Flock, open its API platform dashboard, create a new key with the button provided, then copy the key shown in the window. Keep it at hand for the next step.

  2. 02

    Add a Flock module and open the connection

    In your Make scenario, add a Flock module such as Send a Message and click Create a connection. A connection is your Flock account linked to Make once, then reused by every Flock module you add later.

  3. 03

    Name it and paste your credentials

    The Connection name field is optional, but a clear name helps when you manage several accounts. Paste the token you copied from Flock, or follow the on-screen instructions, then save. The connection now shows up in the module.

First scenario

Your first scenario with Flock

GoalWhen a new item shows up in another app, Make sends a Flock message about it to a teammate.

  1. 01

    Create the scenario

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

  2. 02

    Set up the starting module

    Connect that first app and fill its fields. Once the connection exists, Make lists the folders, sheets or objects it can read, so you choose from a list instead of typing paths.

  3. 03

    Add Send a Message

    Click the + on the right of the first module, search for Flock, choose Send a Message and select your Flock connection. Map data from the previous module into the message so each teammate sees the real details.

  4. 04

    Test with Run once

    Click Run once to execute the scenario one time. Each module shows the bundles it received, a bundle being one item passed along, like one row. Check that the message landed in Flock as expected.

  5. 05

    Schedule and switch it on

    Set the schedule on the first module, which is every 15 minutes by default, then switch the scenario on. On the Free plan, 15 minutes is also the shortest interval between two scheduled runs.

Modules

What the Flock modules do

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

Flock1

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

This module lets you call any endpoint of the Flock API from your scenario, using the connection you already set up, so you are not limited to the one ready-made action.

When to use it
your team needs something from Flock that Send a Message does not handle, and you have the Flock API documentation open to find the right request.
Watch out
you write the request yourself, so a wrong request fails where a ready-made module would have guided you.
Flock2

Send a Message

Action

In Make“Sends a message to a user.”

Send a Message posts a message to a Flock user, so a teammate hears about an event the moment your scenario reaches this step, with details pulled from earlier modules.

When to use it
a new lead, order or form answer arrives in another app and one person on the team should get a direct note about it in Flock.
Watch out
each message is one operation, meaning one run of one module that Make counts on your plan, so a busy source can use operations quickly.
Need help

Need help automating Flock with Make?

A person reads every message.

FAQ

Flock and Make: common questions

01Is the Flock Make integration free?
Yes. Flock is a standard app in Make, so it works from the Free plan onward. The Free plan allows 2 active scenarios, a shortest interval of 15 minutes between scheduled runs, up to 5 minutes per run and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) drop the interval to 1 minute and allow unlimited active scenarios. Usage is counted in operations per month. Your Flock subscription itself is a separate matter, covered on Flock's pricing page.
02What do you need to connect Flock to Make?
You need a Flock account and an API token generated from it. In Make, add a Flock module, click Create a connection, optionally give the connection a name, then paste the credentials you copied from Flock or follow the on-screen instructions. Make's documentation notes that its Flock setup steps were written with AI help from Flock's docs, so if a screen in Flock looks different, check Flock's own documentation or ask Flock.
03Does the Flock Make integration react in real time?
Not on its own, because Flock has no trigger module in Make. Both Flock modules are actions, so your scenario has to start elsewhere. You can open it with a trigger from another app, such as a new row or a form entry, or let it run on its schedule, which is every 15 minutes by default for a new scenario. How fast a message goes out then depends on that starting module, not on Flock.
04What if the Flock module you need is missing in Make?
Use Make an API Call. It reaches any endpoint of the Flock API with the same connection you already created, so anything beyond sending a message to a user stays possible. You build the request yourself from Flock's API documentation. Also keep in mind that Make's page on Flock was generated with AI from Flock's docs and may contain mistakes, so verify important details with Flock before relying on them.
05Should you use Make or n8n for Flock?
It depends on the tool your team already works in. Apps like Flock often have an n8n node too, so check the n8n side before deciding. In Make, you get 2 modules: Send a Message for the everyday case and Make an API Call for the rest, both on the Free plan. The choice comes down to which editor you prefer building in, not to anything specific to Flock, so a quick test in the editor you know best is a sensible first step.
Same platform

Other docs you might need on this stack.

Browse all integrations