Resources · Make integration

EnforcedFlow Make integrationAutomate EnforcedFlow with Make.

Need a person to check an item before your automation moves on? The EnforcedFlow Make integration gives you 4 modules: 1 trigger and 3 actions. This page shows who it suits, how to link your account and how to build a first scenario step by step.

Try the EnforcedFlow integration on MakeSee the 4 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the EnforcedFlow Make integration do for you?

The EnforcedFlow Make integration links your EnforcedFlow account to Make, a visual automation tool. In Make you build a scenario, which is the automation itself: a chain of modules, each module being one brick such as a trigger or an action. Here the bricks let you hand work to a human reviewer and pick it back up once the review is done.

Put a person between two automated steps. An item arrives from another app, say a request typed into a form. Instead of pushing it straight through, Create a Human in the Loop task sends it to EnforcedFlow so someone looks at it first.

Continue once the check is done. Watch reviewed Human in the Loop tasks picks up tasks that went through review, so a second scenario can carry on with the approved work. It is a scheduled trigger: Make asks EnforcedFlow on the scenario's schedule, it is not called by the app.

Share work across a team. Get the next item (simple round robin) hands back the next item in a rotation, which is handy when several people take turns. The name is all the documentation gives, so test it with Run once before relying on it.

Be aware of one limit: Make's documentation for EnforcedFlow is flagged as limited, with no field list and no module descriptions. What these modules return is best learned in your own test run. If you get stuck, the Make troubleshooting guide covers common errors, and the Make review gives a wider view of the tool. Weighing another platform? The n8n vs Make comparison lays out the criteria.

Connect

How do you connect EnforcedFlow to Make?

  1. 01

    Add an EnforcedFlow module

    In your scenario, click the +, search for EnforcedFlow and pick any of its modules. The first time, Make asks for a connection: your EnforcedFlow account linked to Make once and reused by every EnforcedFlow module. Click Create a connection.

  2. 02

    Name the connection

    Giving the connection a name is optional, but it helps later. If you manage a test account and a live account, a clear label saves you from sending real reviews to the wrong place.

  3. 03

    Authorize and save

    Depending on what EnforcedFlow offers, you either approve Make on an EnforcedFlow page or paste a key the app gives you. Then click Save. The documentation lists no special prerequisite for this step.

First scenario

Your first scenario with EnforcedFlow

GoalWhen a new item comes in from another app, Make creates a Human in the Loop task in EnforcedFlow so a person reviews it.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + to add the first module. This first brick is the app your items come from, such as a form or a spreadsheet.

  2. 02

    Set up the source module

    Pick the module of that app, create its connection and fill the fields. Each new entry becomes one bundle, the item that travels from one module to the next.

  3. 03

    Add the EnforcedFlow action

    Click the + on the right of the first module and choose Create a Human in the Loop task. Link your EnforcedFlow account, then map the data from the source module into the fields Make shows.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario a single time and shows the bundles each module received. Check in EnforcedFlow that the task arrived with the data you expected.

  5. 05

    Schedule and switch on

    On the first module, open the clock and set the schedule (every 15 minutes by default). Then switch the scenario on. On the Free plan, 15 minutes is the shortest gap between two runs.

Triggers

What starts an EnforcedFlow scenario

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

EnforcedFlow1Watch reviewed Human in the Loop tasks

Watch reviewed Human in the Loop tasks

triggerIn the docs only

This trigger gives your scenario the tasks a person has finished reviewing in EnforcedFlow, so the work can move on without anyone copying results by hand. Each reviewed task arrives as its own bundle for the next modules.

How it fires
scheduled. Make checks the app on the scenario's schedule, every 15 minutes by default, and 15 minutes at the shortest on the Free plan.
When to use it
as the start of a follow-up scenario, once tasks created elsewhere have been checked and you want to act on the outcome.
Watch out
the documentation does not describe what a reviewed task contains, so run the scenario once and read the bundle before mapping anything.
Modules

What the EnforcedFlow modules do

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

EnforcedFlow1

Create a Human in the Loop task

ActionIn the docs only

This action places an item in front of a human reviewer in EnforcedFlow, so nothing sensitive goes through on autopilot. It is the module that opens the review loop.

When to use it
right after the module that brings in the item, when a person has to validate it before the scenario continues.
Watch out
the documentation lists no fields, so check what Make shows once the connection exists.
EnforcedFlow2

Get the next item (simple round robin)

ActionIn the docs only

Going by its name, this action returns the next entry of a round robin, the rotation where each member takes a turn in order. You get one item per run of the module.

When to use it
when several colleagues share incoming work and you want the scenario to pick whose turn it is.
Watch out
no description exists in the documentation, so confirm its output with Run once first.
EnforcedFlow3

Make an API Call

ActionIn the docs only

This universal module lets you call any endpoint of the EnforcedFlow API from your scenario, using the same connection as the other modules. It covers what the three listed modules leave out.

When to use it
when you need an EnforcedFlow feature that has no dedicated module in Make.
Watch out
you have to know the endpoint yourself, and Make's EnforcedFlow documentation is flagged as limited.
Need help

Need help automating EnforcedFlow with Make?

A person reads every message.

FAQ

Questions about EnforcedFlow and Make

01Is the EnforcedFlow Make integration free?
Yes, EnforcedFlow is a standard app, so it is available from the Make Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution per run, 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 allow unlimited active scenarios. Usage is counted in operations: one operation is one module handling one bundle.
02What do you need to connect EnforcedFlow to Make?
You need an EnforcedFlow account and a Make account. Make's documentation lists no specific prerequisite for this app. The connection follows the usual Make steps: add an EnforcedFlow module, click Create a connection, optionally name it, authorize Make on the app's page or paste the key EnforcedFlow gives you, then click Save. The connection is then reused by all 4 EnforcedFlow modules. If a key is requested, have your EnforcedFlow account settings open before you start.
03Does the EnforcedFlow trigger react in real time?
No. Watch reviewed Human in the Loop tasks is a scheduled trigger: Make checks EnforcedFlow at the interval set on the scenario, every 15 minutes by default. On the Free plan, 15 minutes is the shortest interval; on paid plans it can go down to 1 minute. Reviewed tasks are therefore picked up at the next check, not the moment the review ends. There is no instant trigger for EnforcedFlow in Make.
04What if an EnforcedFlow module is missing in Make?
It depends on what you need, but Make an API Call is the answer in most cases. This module can call any endpoint of the EnforcedFlow API with the connection you already set up, so you can reach features the three other modules do not cover. Keep in mind that Make flags its EnforcedFlow documentation as limited, so you will need the endpoint details from EnforcedFlow itself. Test each call with Run once and read the bundle it returns before you switch the scenario on.
05Should you use Make or n8n for EnforcedFlow?
It depends on your criteria. The same app often has an n8n node as well, so check whether one exists for EnforcedFlow before choosing. On the Make side, you get 4 modules, a visual editor and a Free plan to test your first scenario. Compare what each tool offers for this specific app and how your team prefers to build, rather than relying on a general ranking. If you do look at n8n, the n8n vs Make comparison on this site sets out the criteria side by side.
Same platform

Other docs you might need on this stack.

Browse all integrations