Resources · Make integration

GoHighLevel Make integrationAutomate GoHighLevel with Make.

What could GoHighLevel do on its own if Make handled the busywork? The GoHighLevel Make integration gives you 22 modules: 2 triggers, 17 actions and 3 searches. This guide shows agency owners and sales ops how to connect the account and ship a first working scenario.

Try the GoHighLevel integration on MakeSee the 22 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the GoHighLevel Make integration automate?

The GoHighLevel Make integration links your GoHighLevel account to Make, a visual tool where you build a scenario (the automation itself, a chain of bricks called modules). Each module reads or changes something in GoHighLevel: a contact, a task, an opportunity or a campaign, and passes the result to the next one.

A follow-up that never slips. Watch Contact Updated spots a contact that changed, and Create a Task hands a rep the next step. Nobody has to remember to check the CRM.

A pipeline fed from your other tools. A form or a spreadsheet in another app starts the scenario, Create a Contact files the person in GoHighLevel, and Create an Opportunity opens the deal right behind it.

Campaigns that follow the contact's status. When a lead becomes a client, Delete a Contact from a Campaign takes them out of the prospecting sequence and Add a Contact to a Campaign puts them in the onboarding one.

What Make does not give you here: a module for every corner of GoHighLevel. The 22 modules cover contacts, notes, tasks, opportunities, campaigns and agency accounts. For anything else, Make an API Call reaches the rest of the GoHighLevel API with the same connection. If you are still weighing tools, the n8n vs Make comparison sets the criteria side by side, and the Make pricing page explains how operations are counted. Stuck on a run that fails? Start with Make troubleshooting.

Connect

How do you connect GoHighLevel to Make?

  1. 01

    Add a GoHighLevel module

    In a new scenario, click the +, type GoHighLevel and pick any module, for example Get a Contact. Then click Create a connection. A connection is your GoHighLevel account linked to Make once, and every GoHighLevel module reuses it.

  2. 02

    Name the connection

    Give the connection a name you will recognize later, such as the client it belongs to. The step is optional, but it saves guesswork the day you run several GoHighLevel accounts side by side in Make.

  3. 03

    Authorize and save

    Follow what Make asks next: approve access on the GoHighLevel page that opens, or paste the key GoHighLevel gives you. Click Save. The module now lists the data it can read, and you can fill its fields.

First scenario

Your first scenario with GoHighLevel

GoalWhen a contact is updated in GoHighLevel, Make creates a follow-up task for the team.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the big +. That empty circle becomes your first module, the one that starts everything.

  2. 02

    Set the trigger

    Search GoHighLevel and choose Watch Contact Updated. Pick your connection. This trigger is scheduled: Make checks GoHighLevel for changed contacts each time the scenario runs.

  3. 03

    Add the task

    Click the + on the right of the trigger and add Create a Task. Map the contact that arrived from the trigger into the task fields, so each changed contact gets its own reminder.

  4. 04

    Test with Run once

    Update a test contact in GoHighLevel, then click Run once. Open the bubbles above each module to read the bundles (one bundle is one item, here one contact) and check the task that appeared.

  5. 05

    Schedule and switch on

    Open the clock on the first module. A new scenario runs every 15 minutes by default, and 15 minutes is also the shortest gap on the Free plan. Save, then switch the scenario on.

Triggers

What starts a GoHighLevel scenario

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

GoHighLevel1Watch Contact Updated

Watch Contact Updated

Scheduled trigger

In Make“Triggers when a contact has been updated.”

This trigger picks up contacts that changed in GoHighLevel and sends each one into your scenario as a separate bundle, ready for the next module to act on. It is the simplest way to react to edits your team makes in the CRM.

How it fires
scheduled. Make checks GoHighLevel on the scenario's schedule, every 15 minutes by default, and never faster than 15 minutes on the Free plan.
When to use it
when a change to a contact should lead to something else, like a task, a note or an update in another tool.
Watch out
each contact passed on costs operations downstream, so avoid pairing it with Update a Contact on the same record, or the scenario keeps finding its own edits.
GoHighLevel2Watch Events

Watch Events

Instant trigger

In Make“Triggers when entities are created or updated.”

Watch Events starts your scenario the moment GoHighLevel reports that something was created or updated, so the reaction happens right away instead of waiting for the next scheduled check.

How it fires
instant. GoHighLevel calls Make through a webhook as soon as it happens, and the module shows a lightning badge.
When to use it
when timing matters, for example alerting a rep while the lead is still warm, or when you want to react to more than contact edits.
Watch out
the directory does not say which entities it covers, so run a test with Run once and read the bundle to see what it brings before adding the next module.
Modules

What the GoHighLevel modules do

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

GoHighLevel1

Add a Contact to a Campaign

Action

In Make“Adds a contact to a specified campaign.”

Enrolls an existing contact in the GoHighLevel campaign you choose, so your nurturing starts without anyone opening the contact record by hand.

When to use it
right after a lead fills a form in another app, or once Create a Contact has filed a new person.
Watch out
the contact must already exist; chain Search Contacts or Create a Contact in front of it.
GoHighLevel2

Add an Account

Action

In Make“Adds a new account for agency.”

Opens a new account under your GoHighLevel agency, which turns client onboarding into one step of a scenario rather than a manual setup session.

When to use it
when a signed deal or a paid order in another tool should give the new client their own space right away.
Watch out
this module works at agency level, so check the connection belongs to the agency and not to a single client.
GoHighLevel3

Add a Note to the Contact

Action

In Make“Adds a new note to the contact.”

Writes a note on a contact's record, so the context from another tool, like a call summary or a support ticket, lands where your reps already look.

When to use it
whenever an event outside GoHighLevel says something about a client that the sales team should read before the next call.
Watch out
every run adds a fresh note; if the same event can fire twice, you get two identical notes on the contact.
GoHighLevel4

Create a Contact

Action

In Make“Creates a new contact.”

Adds a brand new person to GoHighLevel from data another module handed over, so leads from ads, forms or spreadsheets stop living outside the CRM.

When to use it
as the landing step for any lead source that GoHighLevel does not capture by itself.
Watch out
nothing in the directory says it checks for an existing record, so put Search Contacts first if duplicates would hurt your follow-up.
GoHighLevel5

Create an Opportunity

Action

In Make“Creates a new opportunity.”

Opens a deal in GoHighLevel so every qualified lead shows up in the sales view with something to close, instead of sitting as a bare contact.

When to use it
after Create a Contact, when a quote request or a booked call means real buying intent.
Watch out
a deal usually hangs on a contact, so build the contact step first and map it into this one.
GoHighLevel6

Create a Task

Action

In Make“Creates a new task.”

Puts a to-do in GoHighLevel for your team, tied to the work a contact needs, so reminders come from the scenario and not from someone's memory.

When to use it
as the action behind Watch Contact Updated or Watch Events, when a change should trigger a call, an email or a check.
Watch out
every bundle that reaches this module becomes one more task, so a busy trigger fills the list quickly and each task costs an operation.
GoHighLevel7

Delete a Contact

Action

In Make“Deletes a contact.”

Removes a contact from GoHighLevel for good, which keeps the database clean when a person asks to be forgotten or a test record slipped in.

When to use it
at the end of a removal request flow, once the contact has been found with Search Contacts.
Watch out
the scenario deletes without asking you first, so try it with Run once on a dummy contact before switching it on.
GoHighLevel8

Delete a Contact from a Campaign

Action

In Make“Deletes a contact from a specified campaign.”

Takes a contact out of a campaign while keeping the contact itself, so people stop receiving a sequence that no longer fits them.

When to use it
when a lead books a call or becomes a client and the prospecting messages should stop right there.
Watch out
it only affects the campaign you pick; pair it with Add a Contact to a Campaign to move the person to the next sequence.
GoHighLevel9

Delete an Opportunity

Action

In Make“Deletes an opportunity.”

Erases a deal from GoHighLevel, which helps when another system is the reference and a cancelled order should not linger in your sales view.

When to use it
when a refund, a cancellation or a duplicate found by Search Opportunities means the deal should not exist.
Watch out
if you only want to close the deal, Update an Opportunity keeps the deal in GoHighLevel; deleting leaves nothing to report on.
GoHighLevel10

Delete a Task

Action

In Make“Deletes a task.”

Clears a task from GoHighLevel, so reps do not chase a follow-up that another event already made pointless.

When to use it
when a client answers or pays before the planned call, and the reminder created earlier by the scenario should go away.
Watch out
to finish a task rather than wipe it, Update a Task is the safer choice, and List Tasks helps you find the right one first.
GoHighLevel11

Get a Contact

Action

In Make“Gets a specified contact.”

Fetches the full record of one contact you point to, so the next modules can use details the trigger did not bring along.

When to use it
in the middle of a scenario, when you already know which contact you need and want its current data before writing somewhere else.
Watch out
it reads a single known contact; when you only have an email or a name, Search Contacts is the module to reach for.
GoHighLevel12

Get an Opportunity

Action

In Make“Gets a specified opportunity.”

Reads one deal in full, which gives the scenario the current version of the deal to send to an invoicing tool, a report or a chat channel.

When to use it
when an earlier module hands you a deal and you want its latest version before acting on it.
Watch out
you need to point to a specific opportunity; to browse several, Search Opportunities returns a list instead.
GoHighLevel13

Get a Task

Action

In Make“Gets a specified task.”

Pulls the details of one task, so the scenario can check what was planned before it updates, closes or reports on it.

When to use it
when a message or an event references a task and you want its current content before telling the client anything.
Watch out
it handles one task you already identified; to look through a contact's tasks, List Tasks does that job.
GoHighLevel14

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Reaches any endpoint of the GoHighLevel API from your scenario, using the same connection, so you are not stuck when the listed modules stop short.

When to use it
when you need a part of GoHighLevel that none of the listed modules touches.
Watch out
you build the request yourself from the GoHighLevel API documentation; test it with Run once and read the response before mapping it.
GoHighLevel15

Update a Contact

Action

In Make“Updates an existing contact.”

Changes the details of a contact already in GoHighLevel, so the CRM reflects what your other tools learned about that person.

When to use it
when a billing app, a form or a support tool learns something new about a client.
Watch out
behind Watch Contact Updated, your own edit counts as a change and can restart the scenario over and over.
GoHighLevel16

Update an Opportunity

Action

In Make“Updates an existing opportunity.”

Edits an existing deal, so its status moves forward as the client signs, pays or goes quiet, without a rep dragging it by hand.

When to use it
when an e-signature tool or a payment app confirms a step that the sales view should show.
Watch out
you need the deal to update; Search Opportunities or Get an Opportunity usually sits right before this module.
GoHighLevel17

Update a Task

Action

In Make“Updates an existing task.”

Rewrites a task that already exists, so the to-do in GoHighLevel matches what just happened outside it.

When to use it
when the client replies by email or books a slot, and the reminder in GoHighLevel should reflect that.
Watch out
find the right task first with List Tasks, otherwise the change lands on the wrong item.
GoHighLevel18

List Tasks

Search

In Make“Retrieves a list of contact tasks.”

Returns the tasks linked to a contact as separate bundles, which lets you review, close or report on a whole to-do list in one scenario.

When to use it
before sending a client summary, or when a deal closes and the open reminders around it need tidying.
Watch out
a search can return zero, one or many items, and every module after it runs once per task, which costs operations.
GoHighLevel19

Search Contacts

Search

In Make“Searches for contacts with a query parameter.”

Looks up contacts that match what you type or map, so the scenario can find an existing person before creating a duplicate.

When to use it
in front of Create a Contact, or anytime you hold an email from another app and need the GoHighLevel record behind it.
Watch out
it can return zero, one or several contacts, and every module after it runs once for each contact found.
GoHighLevel20

Search Opportunities

Search

In Make“Retrieve a list of opportunities.”

Brings back a list of deals as bundles, which helps you report on the sales view or act on several opportunities in one go.

When to use it
to feed a spreadsheet or a dashboard, or to spot the deal that Update an Opportunity should change.
Watch out
each deal it returns runs every following module once, so a wide search costs more operations than it looks.
Need help

Need help automating GoHighLevel with Make?

A person reads every message.

FAQ

GoHighLevel and Make: common questions

01Is the GoHighLevel Make integration free?
Yes, GoHighLevel is a standard app in Make, so its modules work from the Free plan onward. The Free plan has its own limits: 2 active scenarios, at least 15 minutes between two scheduled runs, up to 5 minutes per execution, files up to 5 MB and 512 MB of data transfer. Paid plans lower the gap to 1 minute, remove the cap on active scenarios and allow 40 minutes per execution. Make counts usage in operations, one per module run on one bundle. Your GoHighLevel subscription is a separate matter that Make does not cover.
02What do you need to connect GoHighLevel to Make?
A GoHighLevel account and a Make account. The official documentation for this app lists no prerequisite, so the generic path applies: add any GoHighLevel module, click Create a connection, optionally give it a name, authorize Make on the GoHighLevel page or paste the key the app provides, then click Save. That connection is reused by every GoHighLevel module in your scenarios. If you manage agency accounts with Add an Account, make sure the connection belongs to the agency level.
03Does the GoHighLevel trigger in Make fire in real time?
It depends on the trigger you pick. Watch Events is instant: GoHighLevel calls Make through a webhook as soon as something is created or updated, so the scenario starts right away. Watch Contact Updated is scheduled: Make checks GoHighLevel on the scenario's schedule, every 15 minutes by default. On the Free plan, 15 minutes is the shortest gap; paid plans go down to 1 minute. If timing matters, start from Watch Events.
04What if a GoHighLevel module is missing in Make?
Use Make an API Call. It sends any request to the GoHighLevel API with the connection you already set up, which covers what the listed modules leave out. You write the request from the GoHighLevel API documentation, then check the answer with Run once before mapping it into later modules. The documentation for this app gives no numeric limit, so there is no published quota to plan around from the Make side.
05Should you use Make or n8n for GoHighLevel?
It depends on how you like to build. On Make, GoHighLevel comes with 22 ready modules across contacts, tasks, opportunities, campaigns and agency accounts, one instant trigger, and Make an API Call for the rest, all available on the Free plan. Many apps also have an n8n node, so check whether one exists for GoHighLevel and compare what it covers with this list. Pick the tool whose modules match your scenario and whose editor your team already knows.
Same platform

Other docs you might need on this stack.

Browse all integrations