Resources · Make integration

Enflow Make integrationAutomate Enflow with Make.

Can Make keep your Enflow leads and calls up to date without code? Yes: the Enflow Make integration gives you 11 modules, 9 actions and 2 searches. This page shows how to connect your account, build a first scenario and pick the right module.

Try the Enflow integration on MakeSee the 11 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Enflow Make integration let you automate?

The Enflow Make integration links your Enflow account to Make, so a scenario (the automation you build in Make as a chain of modules) can create, read, update or remove your leads and calls. Each module is one brick of that chain: here, an action on one lead or one call, or a search that returns several calls.

New leads land in Enflow on their own. Another app starts the scenario, for example a form tool, and Create a Lead records the person in Enflow. When the contact is already known, Update a Lead refreshes the record rather than adding a second one.

A call history you can reuse. List Calls for Lead returns the calls linked to one lead, and List Calls by Date works from a date. Each call comes out as a bundle, one item handed to the next module, so you can push them into a sheet or a report.

Clean records after a change. Update a Call and Delete a Call keep the call log in line with what really happened. Make's documentation for Enflow is short on detail, so test every module with Run once before trusting it. Whatever the dedicated modules miss goes through Make an API Call, on the same connection.

Enflow may also be available as an n8n node; the n8n vs Make comparison helps you choose. To learn the editor properly, the Make training is a good start, and the Make troubleshooting guide helps when a run fails.

Connect

How do you connect Enflow to Make?

  1. 01

    Open the connection window

    Add any Enflow module to your scenario, then click Create a connection. A connection is your Enflow account linked to Make once; every Enflow module in every scenario reuses it afterwards.

  2. 02

    Name it and authorize Make

    Give the connection a name you will recognize, which is optional but handy with several accounts. Then authorize Make on the Enflow page that opens, or paste the key Enflow gives you, depending on what the window asks for.

  3. 03

    Save and check the module

    Click Save. Back in the module, Make can now list what it is able to read from your account. If the fields fill in, the connection works and you can move on to the scenario.

First scenario

Build your first scenario with Enflow

GoalWhen a form in another app receives a new contact, Make creates the matching lead in Enflow.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + to add the first module. Enflow has no trigger, so this first module comes from the app where your contacts start, such as a form tool.

  2. 02

    Set the starting module

    Pick the trigger of that other app and connect its account. A trigger starts the scenario: scheduled when Make checks on a clock, instant when the app calls Make as soon as something happens.

  3. 03

    Add Create a Lead

    Click the + on the right of the first module, search for Enflow and choose Create a Lead. Link your account with Create a connection, then map the contact data from the previous module.

  4. 04

    Test it with Run once

    Click Run once to execute the scenario one time. Read the bundles each module received, then look in Enflow to confirm that the lead appeared as expected.

  5. 05

    Schedule and switch on

    Set the schedule on the first module: a new scenario runs every 15 minutes by default, which is also the shortest gap on the Free plan. Then switch the scenario on.

Modules

What each Enflow module does

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

Enflow1

Create a Call

ActionIn the docs only

Adds a call record to Enflow straight from your scenario, so a conversation noted elsewhere also exists in Enflow.

When to use it
another app knows a call just took place, for instance your calendar or phone tool, and you want Enflow to keep the trace without typing it again.
Watch out
each run creates a new record, so a scenario that fires twice on the same event leaves two calls.
Enflow2

Create a Lead

ActionIn the docs only

Gets a new prospect into Enflow with the data mapped from an earlier module, so nobody copies contacts by hand.

When to use it
someone fills a form, signs up or answers a campaign in another tool and should show up in Enflow right after.
Watch out
if the same person can reach the scenario twice, plan a check before this module, otherwise you may end up with two leads.
Enflow3

Delete a Call

ActionIn the docs only

Clears one call out of Enflow, which keeps the log honest when a call was recorded by mistake or never happened.

When to use it
a meeting is cancelled in your booking app and the matching call in Enflow no longer makes sense.
Watch out
assume a deletion cannot be undone from Make; try it on a throwaway record with Run once before switching the scenario on.
Enflow4

Delete a Lead

ActionIn the docs only

Takes a lead out of Enflow for good, useful when a contact asks to be forgotten or turns out to be a test entry.

When to use it
a removal request arrives through a form or your help desk and the person must disappear from Enflow as well.
Watch out
check in the Run once output that the mapped lead is the right one before you activate, since nothing suggests you can undo it.
Enflow5

Get a Call

ActionIn the docs only

Fetches the record of one call you already know about, so later modules can reuse its data.

When to use it
an earlier step hands you a call and you need the rest of its details, for example to write a summary in a shared document.
Watch out
it reads a single call; to gather several, pick List Calls by Date or List Calls for Lead instead.
Enflow6

Get a Lead

ActionIn the docs only

Reads one lead from Enflow and passes its data to the next modules, which saves you from keeping a copy somewhere else.

When to use it
before sending an email or updating a deal in another app, you want the latest version of the lead as Enflow holds it.
Watch out
this module works on one known lead, it does not search; an earlier module has to tell it which lead to read.
Enflow7

List Calls by Date

SearchIn the docs only

Returns the calls that match a date, one bundle per call, ready to feed a sheet or a report.

When to use it
a sales manager wants a recap of calls copied into a spreadsheet without exporting anything by hand.
Watch out
as a search it can return zero, one or many calls, and every module after it runs once per call, which adds operations to your plan.
Enflow8

List Calls for Lead

SearchIn the docs only

Gathers the calls tied to a single lead, giving you that contact's history in one step.

When to use it
a lead reaches a new stage and you want to attach its past calls to a message for the colleague who takes over.
Watch out
a lead with no call returns zero bundles; test that case with Run once so the result does not surprise you later.
Enflow9

Make an API Call

ActionIn the docs only

Opens the rest of the Enflow API to your scenario, with the same connection as the other modules, for anything the dedicated modules leave out.

When to use it
you need an Enflow endpoint that none of the listed modules covers.
Watch out
Make's documentation for Enflow is limited, so the endpoint and its parameters have to come from Enflow itself before you build.
Enflow10

Update a Call

ActionIn the docs only

Changes an existing call in Enflow so the record reflects what actually happened after the fact.

When to use it
the outcome of a call is decided later, in another tool, and the Enflow entry should carry it too.
Watch out
choose this over Create a Call when the call already exists, otherwise you get two versions of the same conversation.
Enflow11

Update a Lead

ActionIn the docs only

Keeps a lead current by writing fresh information into the record Enflow already has.

When to use it
a prospect's details change in your CRM or billing tool and Enflow should follow without a manual edit.
Watch out
map only what you mean to change and test with Run once, because a wrong mapping can overwrite good data.
Need help

Need help automating Enflow with Make?

A person reads every message.

FAQ

Enflow and Make: common questions

01Is the Enflow Make integration free?
Yes. Enflow is a standard app, so its modules work from the Make Free plan onward. The Free plan allows 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes per execution, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute, lift the cap on active scenarios and allow 40 minutes per run. Make counts each execution of a module as an operation, taken from the monthly credits of your plan.
02What do you need to connect Enflow to Make?
An Enflow account and a Make account. Make's documentation lists no specific prerequisite and no dedicated connection steps for Enflow, so the usual path applies: add an Enflow module, click Create a connection, name it if you like, authorize Make on the Enflow page or paste the key Enflow provides, then click Save. The connection is stored once and every Enflow module you add later reuses it, in this scenario and in the next ones.
03Does Enflow trigger Make scenarios in real time?
No. Enflow has no trigger in Make, neither scheduled nor instant: its 11 modules are 9 actions and 2 searches, so something else has to start the scenario. Two options work. Put the trigger of another app first, for instance a form tool that calls Make through a webhook as soon as a response arrives. Or start the scenario on its schedule, the clock on the first module, which runs every 15 minutes by default, and open with a search such as List Calls by Date.
04What if an Enflow module is missing in Make?
Use Make an API Call. It reaches any endpoint of the Enflow API through the connection you already have, which covers what the dedicated modules leave out. Keep in mind that Make's own documentation for Enflow is limited, because little public information exists about the app, so the endpoint details will have to come from Enflow. If the need sits outside Enflow altogether, modules from another app can take over that step in the same scenario.
05Should you use Make or n8n for Enflow?
It depends on the steps you need. On Make, Enflow comes with 11 modules for leads and calls, plus Make an API Call for the rest, all usable on the Free plan. The same app often has an n8n node too, so look at which operations it offers there before deciding. Then compare both lists with your real use case, whether that is creating leads from a form, keeping call records current or pulling a call history, and pick the one whose modules match it.
Same platform

Other docs you might need on this stack.

Browse all integrations