Resources · Make integration

Engage Make integrationAutomate Engage with Make.

Your user data already lives in other tools, so why retype it in Engage? The Engage Make integration gives you 3 action modules, no trigger. This guide is for marketers who connect the account, then build a first scenario that pushes users into Engage.

Try the Engage integration on MakeSee the 3 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Engage Make integration do?

The Engage Make integration links your Engage account to Make, a no-code tool where you build a scenario (the automation itself, a chain of modules). Each module is one brick of that chain. Engage brings three of them, all actions: Identify a User, Track a User and Make an API Call. Something else has to start the scenario.

Users that appear in Engage on their own. Someone signs up through a form or a shop in another app. That app starts the scenario, and Identify a User hands the person to Engage, so nobody copies profiles by hand.

Actions that follow the user. Track a User comes right after, in the same scenario, when a step taken in another tool should land on that user's record in Engage. The official documentation gives no description of either module, so open them in the editor to read the exact fields before you rely on them.

Everything else in the API. Make an API Call reaches any endpoint of the Engage API with the same connection. It is the way out when the two named modules do not cover your case.

What Make does not offer here: no trigger. Engage cannot start a scenario by itself, so the start comes from another app or from the schedule of the scenario. If the basics of Make are new to you, the Make review and the Make training cover them. Engage may also have an n8n node, and n8n vs Make sets out the criteria for choosing.

Connect

How do you connect Engage to Make?

  1. 01

    Copy your API key and secret

    In Engage, open the account dashboard, go to the Settings section and click the API panel. Copy the API key and the API secret shown there. You need an active Engage account to see them.

  2. 02

    Open the connection window

    In your Make scenario, add any Engage module and click Create a connection. A connection is your Engage account linked to Make once, then reused by all three modules. The Connection name field is optional.

  3. 03

    Paste the credentials and save

    Paste the API key and the API secret you copied, or follow the on-screen instructions, then save. From now on every Engage module in any scenario can pick this connection from a short list.

First scenario

Your first scenario with Engage

GoalWhen a new person signs up in another app, Make hands that person to Engage with Identify a User, then records what they did with Track a User.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + to add the first module. Since Engage has no trigger, pick the app where your sign-ups happen, such as your form tool.

  2. 02

    Add Identify a User

    Click the + on the right of that first module, search for Engage and choose Identify a User. Select your connection, or click Create a connection if you have not made one yet.

  3. 03

    Map the person's data

    Fill the fields of Identify a User with data from the first module. Each bundle, meaning one item passing between modules (here one sign-up), carries values you can click to drop them in place.

  4. 04

    Chain Track a User

    Add Track a User after it with another +, and map the same person again. This keeps the user and the step they took together in a single run of the scenario.

  5. 05

    Test with Run once

    Click Run once to execute the scenario a single time. Make shows the bundles each module received, so you can check in Engage that the user arrived with the right values.

  6. 06

    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 can Make do in Engage?

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

Engage1

Identify a User

ActionIn the docs only

Going by its name, Identify a User tells Engage who a person is, using the data another app just sent. The documentation has no description, so its fields are your real guide: open it once connected.

When to use it
right after the step that brings in a new contact, before anything else touches Engage.
Watch out
it acts on one bundle at a time, so a list of contacts means one operation per person.
Engage2

Make an API Call

ActionIn the docs only

This module opens the whole Engage API to your scenario, with the connection you already set up, so you are not limited to the two named modules. You write the request yourself, which asks for a look at the Engage API reference.

When to use it
when Identify a User and Track a User do not cover the change you need in Engage.
Watch out
a wrong request only shows up when it runs, so test it with Run once before you switch the scenario on.
Engage3

Track a User

ActionIn the docs only

Judging by its name, Track a User records in Engage what someone did in another tool, in the same run that identified them. No official description exists for it, so check its fields in the editor before you map anything.

When to use it
placed after Identify a User, whenever an action taken outside Engage matters for that person.
Watch out
map the same user value in both modules, otherwise the two steps may not meet on one record.
Need help

Need help automating Engage with Make?

A person reads every message.

FAQ

Engage and Make: common questions

01Is the Engage Make integration free?
Yes, Engage is a standard app in Make, so it works on the Free plan. That plan has limits: 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution at most, 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 and remove the cap on active scenarios. Usage is counted in operations, one per module run on one item. You still need your own active Engage account, which Engage bills on its side.
02What do you need to connect Engage to Make?
You need an active Engage account and its API credentials, which are two values: an API key and an API secret. In Engage, open the account dashboard, then the Settings section, then the API panel, and copy both. In Make, add an Engage module, click Create a connection, give it a name if you like and paste the two values. The connection is then shared by the three Engage modules, so this setup happens once per account.
03Can Engage trigger a Make scenario in real time?
No, Engage has no trigger module in Make, so it cannot start a scenario by itself. Two ways around that. Start the scenario with a trigger from another app, for example the tool where people sign up, and add the Engage modules after it. Or put a scheduled first module in front, which Make runs on the scenario schedule, every 15 minutes by default and every 15 minutes at the shortest on the Free plan. Any real-time behavior depends on that first app, not on Engage.
04What if an Engage module is missing in Make?
It depends on the action, but Make an API Call usually closes the gap. It calls any endpoint of the Engage API with the same connection you already created, so anything the API allows is within reach even without a dedicated module. You write the request yourself, so keep the Engage API reference open. The Make documentation for Engage also warns that it was generated with AI from the vendor docs and may contain mistakes, so check important details with Engage directly.
05Should you use Make or n8n for Engage?
It depends on your criteria more than on Engage. On Make, Engage offers 3 action modules, Identify a User, Track a User and Make an API Call, all on one connection, and it is available from the Free plan. Engage may also have an n8n node. Compare what each tool offers for this app, how its connection works and which one your team already uses. There is no ranking or cost comparison to lean on between the two here, so test the Make version with Run once and judge on your own use case.
Same platform

Other docs you might need on this stack.

Browse all integrations