Resources · Make integration

EngageBay Make integrationAutomate EngageBay with Make.

Can Make keep your EngageBay CRM moving while you work on deals? The EngageBay Make integration gives you 38 modules: 8 triggers, 24 actions and 6 searches over contacts, companies, deals, tasks and tracks. This page shows how to link your account and build a first scenario.

Try the EngageBay integration on MakeSee the 38 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the EngageBay Make integration let you automate?

The EngageBay Make integration links your EngageBay account to Make so that records move on their own. You build a scenario (the automation itself, a chain of modules) where each module is one brick: it watches EngageBay for new or updated records, creates or edits contacts, companies, deals and tasks, or looks them up.

A follow-up task for every new deal. Watch New Deals spots the deal, then Create a Task puts the next step on the sales rep's list, so nobody has to remember to open it.

Contacts that arrive already sorted. When a lead comes in from another app, Create a Contact files it in EngageBay and Add a Contact to a Sequence starts the outreach you already wrote. Add Tags to Contact labels it by source.

A company record that stays in sync. Watch Companies Updates catches each edit and passes it to the tool your finance or support team reads, with no copy and paste.

What Make will not do for you: the official doc lists no module groups and no troubleshooting section for EngageBay, and it flags its own text as AI-generated, so check the details in EngageBay before you rely on them. When a listed module falls short, Make an API Call reaches the rest of the API with the same connection.

New to Make? The Make review walks through the editor, and Make pricing explains how operations are counted. Weighing another tool? Read n8n vs Make.

Connect

How do you connect EngageBay to Make?

  1. 01

    Copy your REST API Key

    In EngageBay, open Account Admin Settings, then the API section. Your REST API Key sits there: copy it. You need an active EngageBay account for this key to exist.

  2. 02

    Add an EngageBay module

    In your Make scenario, add any EngageBay module and click Create a connection. A connection is your EngageBay account linked to Make once, then reused by every EngageBay module you add later.

  3. 03

    Paste the key and save

    Give the connection a clear label in Connection name if you like (it is optional), paste the REST API Key, and confirm. Make can now read and write your EngageBay records.

First scenario

Your first scenario: a task for each new EngageBay deal

GoalWhen a new deal lands in EngageBay, Make creates a follow-up task for it.

  1. 01

    Create the scenario

    Open the Scenarios page in Make, create a new scenario, and click the big + to place your first module.

  2. 02

    Add Watch New Deals

    Search for EngageBay, pick Watch New Deals, then click Create a connection and paste your REST API Key. This trigger is scheduled: Make checks EngageBay on the scenario's schedule.

  3. 03

    Add Create a Task

    Click the + on the right of the trigger, choose EngageBay again, then Create a Task. Map the deal details from the first module into the task so the rep knows which deal it belongs to.

  4. 04

    Test with Run once

    Add a test deal in EngageBay, then click Run once. Make runs the scenario one time and shows each bundle (one item passed between modules, here one deal) that every module received.

  5. 05

    Schedule and switch it on

    Click the clock on the first module to set the schedule (every 15 minutes by default), then switch the scenario on. Each module run counts as one operation on your plan.

Triggers

What can start an EngageBay scenario?

8 modules start a scenario when something happens in EngageBay. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by EngageBay as soon as it happens.

EngageBay1Watch Companies Updates

Watch Companies Updates

Scheduled trigger

In Make“Triggers when some company is updated.”

You get every company record that someone edited in EngageBay, handed to the rest of your scenario as one bundle per company. It lets another tool learn about changed account details without anyone retyping it.

How it fires
scheduled, Make checks the app on the scenario's schedule, so changes arrive in batches and not the second they happen.
When to use it
your billing or support tool keeps its own copy of each client company and must follow EngageBay.
Watch out
it catches edits only; brand new companies belong to Watch New Companies.
EngageBay2Watch Contacts Updates

Watch Contacts Updates

Scheduled trigger

In Make“Triggers when some contact is updated.”

This trigger hands you each contact that changed in EngageBay, so a scenario can react when a lead's record moves. One edited person becomes one bundle for the next module.

How it fires
scheduled, Make checks the app on the scenario's schedule and collects the edits made since the last check.
When to use it
a contact is updated by your sales team and your newsletter tool or spreadsheet must reflect it.
Watch out
if a later module edits the same contact with Update a Contact, the scenario can pick that edit up again and loop; add a filter first.
EngageBay3Watch Deals Updates

Watch Deals Updates

Scheduled trigger

In Make“Trigger when some deal is updated.”

Edited deals come out of this trigger, one bundle each, which is what you want when a change to a deal should set off work elsewhere. It follows the deal after its creation, not the creation itself.

How it fires
scheduled, Make checks the app on the scenario's schedule, so expect a short wait between the edit and the run.
When to use it
a deal moves forward and your team channel or your invoicing tool should hear about it.
Watch out
any edit counts, so filter on the detail you care about before acting.
EngageBay4Watch New Companies

Watch New Companies

Scheduled trigger

In Make“Triggers when new company is created.”

Each company created in EngageBay starts your scenario, with that company as the bundle passed along. A fresh account record can open a folder, a channel or a row in another app without a manual step.

How it fires
scheduled, Make checks the app on the scenario's schedule and picks up companies added since the previous check.
When to use it
a signed client is added as a company and your project tool needs a matching workspace.
Watch out
a company created by the same scenario, through Create a Company, will be seen again on the next check.
EngageBay5Watch New Contacts

Watch New Contacts

Scheduled trigger

In Make“Triggers when new contact is added.”

New people in your CRM become the start of a scenario: every contact added to EngageBay arrives as one bundle. It is the usual entry point for welcome steps, tagging or copying leads into a sheet.

How it fires
scheduled, Make checks the app on the scenario's schedule, not the moment the contact is saved.
When to use it
a form fill or a manual entry creates a contact and you want a sales rep alerted.
Watch out
a contact your scenario creates itself will come back through this trigger, so avoid pairing it with Create a Contact in the same flow.
EngageBay6Watch New Deals

Watch New Deals

Scheduled trigger

In Make“Triggers when new deal is added.”

This one reacts to every deal opened in EngageBay and passes it on as a bundle, which makes it the natural start for follow-up tasks and team alerts. It answers the question: which opportunities appeared since the last check?

How it fires
scheduled, Make checks the app on the scenario's schedule, every 15 minutes by default.
When to use it
a rep logs a new opportunity and a task, a message or a sheet row should follow without them asking.
Watch out
later changes to that deal are not seen here; Watch Deals Updates covers them.
EngageBay7Watch New Tasks

Watch New Tasks

Scheduled trigger

In Make“Triggers when new task is added.”

Tasks added in EngageBay flow out of this trigger, one bundle per task, so your to-do list can reach the calendar, chat or project board your team really opens.

How it fires
scheduled, Make checks the app on the scenario's schedule and returns the tasks created in between.
When to use it
a manager assigns a call in EngageBay and the owner should get a message in the tool they check first.
Watch out
if the same scenario runs Create a Task, those tasks show up here too and can start a loop; keep the two in separate scenarios.
EngageBay8Watch Tasks Updates

Watch Tasks Updates

Scheduled trigger

In Make“Triggers when some task is updated.”

Here you receive each task that changed in EngageBay, as a bundle, which lets a scenario notice when work is edited or finished. It is the pair to Watch New Tasks, focused on what happens after creation.

How it fires
scheduled, Make checks the app on the scenario's schedule and gathers edits since the last pass.
When to use it
a completed task should close the matching card in your project tool or log a line in a report sheet.
Watch out
every kind of edit comes through, so add a filter before any action that writes back.
Modules

What else can Make do in EngageBay?

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

EngageBay1

Add a Contact to a Form

Action

In Make“Adds contact to a form.”

Links an existing contact to one of your EngageBay forms, even when the lead came through another channel than that form.

When to use it
leads captured on a landing page built outside EngageBay should be tied to the matching EngageBay form.
Watch out
the contact must already exist; run Create a Contact or Get a Contact before this module.
EngageBay2

Add a Contact to a Sequence

Action

In Make“Adds a contact to a sequence.”

Enrolls a contact in a sequence you prepared in EngageBay, so the outreach starts without anyone opening the CRM to press a button.

When to use it
a trial signup or a webinar registration in another app should kick off your nurture emails right away.
Watch out
nothing stops a contact from being enrolled twice by two runs, so add a filter or a tag check upstream.
EngageBay3

Add Tags to Contact

Action

In Make“Adds one or more tags to contact.”

Puts one or more tags on a contact, which gives you a clean way to mark source, interest or stage without editing the full record.

When to use it
a contact downloads a guide or attends an event and your team segments lists by tag.
Watch out
this module only adds; to take a tag back off, use Delete Tags From a Contact rather than Update a Contact.
EngageBay4

Create a Company

Action

In Make“Creates a company.”

Opens a new company record in EngageBay from data held in another app, so account details are typed once, at the source.

When to use it
a client signs in your quoting or e-signature tool and the account should exist in the CRM straight away.
Watch out
the doc says nothing about duplicate checks, so search with List Companies first if the company may already be there.
EngageBay5

Create a Contact

Action

In Make“Creates a contact.”

Adds a person to EngageBay from any form, sheet or app that Make reads. It is the entry point for most lead-capture scenarios.

When to use it
a lead fills a form on your site builder or books a call, and sales should see them in EngageBay without copying anything.
Watch out
run List Contacts or Get a Contact first when the person may already be in the CRM, otherwise you risk a second record.
EngageBay6

Create a Deal

Action

In Make“Creates a deal.”

Starts a new deal in EngageBay so an opportunity is logged the moment it appears somewhere else, with its details mapped from the earlier module.

When to use it
a quote request lands in your inbox or a form and should become a pipeline item for the sales team.
Watch out
if your account has several tracks, List Tracks tells you which one the deal should go into.
EngageBay7

Create a Task

Action

In Make“Creates a task.”

Drops a task into EngageBay, so the next action on a lead or a deal is written down where the team already works.

When to use it
a new deal, a missed call or a support ticket should put a follow-up on someone's list.
Watch out
List Owners gives you the people you can assign it to; without an owner the task can sit unnoticed.
EngageBay8

Create a Track

Action

In Make“Creates new track.”

Sets up a new track, the container your deals are listed by, straight from a scenario. It saves you building the same pipeline by hand for each new line of business.

When to use it
launching a new product or region calls for its own deal track in EngageBay.
Watch out
tracks are structure, not daily data; run this with care so you do not end up with near-identical tracks.
EngageBay9

Delete a Company

Action

In Make“Deletes a company.”

Removes a company from EngageBay, which keeps the CRM clean when an account is closed or merged somewhere else.

When to use it
a company is flagged as a duplicate or marked as gone in the tool your ops team treats as the reference.
Watch out
a delete cannot be undone from Make; test on a dummy record with Run once and put a filter in front before switching it on.
EngageBay10

Delete a Contact

Action

In Make“Deletes single contact from account.”

Erases a single contact from your EngageBay account, useful when a person asks to be removed or a record was created by mistake.

When to use it
a removal request reaches your support desk and the CRM should follow without a manual search.
Watch out
there is no recycle step on the Make side, so confirm the right contact with Get a Contact first.
EngageBay11

Delete a Deal

Action

In Make“Deletes a deal.”

Takes a deal out of EngageBay for good, which helps when test entries or duplicate opportunities clutter the pipeline.

When to use it
a deal was opened twice by two different scenarios and one copy has to go.
Watch out
a lost deal is often better kept for reporting; delete only what should never have existed, and filter strictly before this module.
EngageBay12

Delete a Task

Action

In Make“Deletes a task.”

Clears a task from EngageBay when it no longer makes sense, so reps are not chasing actions that were cancelled elsewhere.

When to use it
a meeting is cancelled in your booking tool and the matching reminder task should disappear.
Watch out
you need the task's ID, so pair it with List Tasks or keep the ID from the module that created it.
EngageBay13

Delete a Track

Action

In Make“Deletes a track.”

Removes a whole track from EngageBay, which only makes sense when a pipeline is retired for good.

When to use it
a temporary campaign pipeline has served its purpose and your admin wants the account tidy.
Watch out
deals are listed by track, so check with List Deals what still sits in it before you run this module; the action cannot be reversed from Make.
EngageBay14

Delete Tags From a Contact

Action

In Make“Removes one or more tags from contact.”

Strips one or more tags off a contact, so segments stay accurate when someone's situation changes.

When to use it
a prospect becomes a customer and the "prospect" tag should go, while the rest of the record stays untouched.
Watch out
it only removes tags; to add them, Add Tags to Contact is the matching module, and the two often sit in the same scenario.
EngageBay15

Get a Company

Action

In Make“Gets a company.”

Fetches one company's full record from EngageBay, giving later modules everything they need about that account.

When to use it
a trigger hands you only a company reference and you need the details before writing an invoice or a message.
Watch out
it returns one company you already know; to find companies by browsing, List Companies is the right module.
EngageBay16

Get a Contact

Action

In Make“Gets contact by ID.”

Reads a single contact by its ID and returns the whole record, so the rest of the scenario can use any detail of that person.

When to use it
a deal or a task points to a contact and your email or chat step needs their name and details.
Watch out
it works from an ID, not a name; if you only have a name, start from List Contacts.
EngageBay17

Get a Deal

Action

In Make“Gets single deal.”

Pulls up one deal with its current details, handy when a scenario must check a deal's state before acting on it.

When to use it
an invoice is paid in your accounting tool and you want to confirm the linked deal before updating anything.
Watch out
it reads a single deal; for a batch of deals in a track, reach for List Deals.
EngageBay18

Get a Task

Action

In Make“Gets a task.”

Retrieves one task and all its details, so you can see who owns it and what it says before the next step.

When to use it
a message about a task arrives in your chat tool and the scenario should look up the full task first.
Watch out
keep the task ID from the module that created or listed it, since this module needs it to find the task.
EngageBay19

Get a Track

Action

In Make“Gets a track by ID.”

Looks up a single track by its ID and returns its setup, which helps when a scenario must know where a deal sits.

When to use it
you route deals to different teams depending on their track and need the track's details to decide.
Watch out
the ID usually comes from List Tracks; run that once with Run once to see which IDs your account uses.
EngageBay20

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Calls any endpoint of the EngageBay API with the connection you already set up, so you are not stuck when no listed module does what you need.

When to use it
you need an EngageBay object or action that none of the listed modules covers.
Watch out
you write the request yourself, so read EngageBay's API reference first and test the call with Run once before relying on it.
EngageBay21

Update a Company

Action

In Make“Updates a company.”

Edits an existing company in EngageBay, so changed account details reach the CRM as soon as another tool knows it.

When to use it
your billing platform holds the up-to-date account details and EngageBay should mirror them.
Watch out
if Watch Companies Updates starts the same scenario, this edit will trigger it again; filter to avoid a loop.
EngageBay22

Update a Contact

Action

In Make“Updates contact info.”

Changes the details of a contact already in EngageBay, which keeps your CRM matching what people tell you in other channels.

When to use it
a customer changes their details in your help desk or shop, and sales should see the new one.
Watch out
for tags, the dedicated tag modules are cleaner; and pairing this with Watch Contacts Updates in one scenario can create a loop.
EngageBay23

Update a Task

Action

In Make“Updates a task.”

Adjusts an existing task, for example its details or its state, so EngageBay reflects what really happened to that piece of work.

When to use it
a call is logged as done in your phone system and the matching task in EngageBay should follow.
Watch out
the module needs the task ID; keep it from Create a Task or find it with List Tasks.
EngageBay24

Update a Track

Action

In Make“Updates a track.”

Modifies a track's setup from a scenario, which spares your admin from repeating the same edit across accounts or teams by hand.

When to use it
a pipeline is renamed or reorganized and several tracks must follow the same change.
Watch out
changing a track affects every deal listed in it, so try it on a test track with Run once first.
EngageBay25

List Companies

Search

In Make“Lists all companies.”

Returns the companies in your EngageBay account, one bundle per company, so you can loop over them or search for a match.

When to use it
before creating a company, you want to check whether it already exists, or you need to export accounts to a sheet.
Watch out
a search module can return zero, one or many bundles; every module after it runs once per company, which counts in operations.
EngageBay26

List Contacts

Search

In Make“Gets list of all contacts.”

Brings back the contacts stored in EngageBay as separate bundles, ready to be filtered, copied or checked one by one.

When to use it
a mailing tool or a data sheet needs a full refresh from the CRM, or you look for an existing person before Create a Contact.
Watch out
a large contact base means many bundles and many operations downstream; add a filter right after it.
EngageBay27

List Deals

Search

In Make“Lists deals by track or from default track.”

Lists the deals in a given track, or in the default track when you leave it open, each deal as its own bundle.

When to use it
you build a pipeline report in a spreadsheet or need to find a deal before updating it.
Watch out
if you run several pipelines, choose the track explicitly, otherwise you only see the default one.
EngageBay28

List Owners

Search

In Make“Gets list of all owners.”

Gives you the list of owners in your EngageBay account, which is how a scenario learns who records can be assigned to.

When to use it
you spread new leads or tasks across reps and need their IDs to assign each record correctly.
Watch out
each owner comes out as a separate bundle; aggregate or filter them before assigning, or the next module runs once per owner.
EngageBay29

List Tasks

Search

In Make“Lists all tasks.”

Collects the tasks in EngageBay as individual bundles, useful for a digest, a cleanup or finding one task to edit.

When to use it
a manager wants open follow-ups copied into a shared sheet, or a scenario must find a task before Update a Task.
Watch out
expect many bundles on a busy account, and filter before any action so you do not burn operations.
EngageBay30

List Tracks

Search

In Make“Gets list of all tracks.”

Shows every track set up in your EngageBay account, so a scenario can pick the right one instead of guessing an ID.

When to use it
you are about to create or list deals and need to know which tracks exist and their IDs.
Watch out
run it with Run once while building to read the IDs, then map the right one into Create a Deal or List Deals.
Need help

Need help automating EngageBay with Make?

A person reads every message.

FAQ

EngageBay and Make: common questions

01Is the EngageBay Make integration free?
Yes, EngageBay is a standard app in Make, so you can use it from the 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, remove the cap on active scenarios and allow 40 minutes of execution. Usage is counted in operations, one per module run on one bundle. You still need your own EngageBay account.
02What does the EngageBay Make connection require?
You need an active EngageBay account and its REST API Key. In EngageBay, go to Account Admin Settings, open the API section and copy the REST API Key. In Make, add any EngageBay module, click Create a connection, optionally name it, then paste the key. That single connection is reused by every EngageBay module in your scenarios, so you only do this once per account. If the key is refused, copy it again from the same place, without extra spaces.
03Do EngageBay triggers in Make fire instantly?
No. All 8 EngageBay triggers in Make are scheduled, none is instant. Make checks EngageBay on the scenario's schedule, every 15 minutes by default, and picks up the new or updated contacts, companies, deals or tasks found since the previous check. On the Free plan the shortest interval is 15 minutes; paid plans go down to 1 minute. For most CRM follow-ups, such as creating a task after a new deal, that delay is fine. Plan for it when a step has to happen right after a change.
04What if an EngageBay module is missing in Make?
Use Make an API Call. It ships with the EngageBay app and lets a scenario call any endpoint of the EngageBay API with the connection you already have, so you are not limited to the listed modules. You write the request yourself, so keep EngageBay's API reference open and test the call with Run once. Note that the official Make doc for EngageBay lists no specific limits and warns that its text is AI-generated, so verify important details in EngageBay itself.
05Should EngageBay users pick Make or n8n?
It depends on how you prefer to work. On the Make side, the EngageBay app gives you 38 ready modules, including 8 scheduled triggers, a guided connection with your REST API Key, and a Free plan to start. The same app often exists as a node in n8n as well. Compare the modules each tool offers for EngageBay against the steps your scenario really needs, then try the one whose editor your team finds clearer. The comparison page linked above covers the general differences.
Same platform

Other docs you might need on this stack.

Browse all integrations