See the top GoHighLevel agencies in the USA for 2026: 14 ranked
The Make.com GoHighLevel integration: modules, setup, cost and limits
Yes. Make (make.com) has a GoHighLevel app, marked Verified and maintained by Make. It connects by OAuth 2.0 to a sub-account or an agency, with no API key. Its 22 modules watch HighLevel events and create, update, find or delete contacts, opportunities and tasks, add notes and manage campaigns, plus a Make an API Call module for anything else. Make bills in credits, with 1,000 a month free. HighLevel's API allows 100 requests per 10 seconds per app per sub-account.
Updated
Make.com GoHighLevel facts
| Fact | Detail | Source |
|---|---|---|
| App on Make | GoHighLevel, marked Verified and "supported and maintained by Make" | make.com |
| Connection types | GoHighLevel Location OAuth 2.0 (sub-account) or Company OAuth 2.0 (agency); Events OAuth 2.0 for Watch Events | apps.make.com |
| Modules | 22 in Make's app docs: 3 watch triggers, 12 actions, 6 list/get/search modules and Make an API Call | apps.make.com |
| Deprecated | Watch Opportunities (deprecated) and Watch Contact Updated (to be deprecated); Make points to Watch Events | apps.make.com |
| Make billing unit | Credits; by default 1 operation equals 1 credit | help.make.com |
| Make Free plan | 1,000 credits a month | make.com |
| HighLevel API limits | 100 requests per 10 seconds and 200,000 per day, per app per sub-account or agency | marketplace.gohighlevel.com |
| Make instant triggers | Default rate limit of 100 runs per minute; extra requests queue | help.make.com |
| HighLevel inbound webhook | Premium trigger: 100 free lifetime runs per sub-account, then $0.01 a run without Workflow Pro | help.gohighlevel.com |
Triggers and actions in Make's HighLevel app
Make's HighLevel app has 22 modules across seven groups. The table lists them as named in Make's app documentation.
| Group | Modules |
|---|---|
| Events | Watch Events (instant, by webhook) |
| Contacts | Watch Contact Updated, Search Contacts, Get a Contact, Create a Contact, Update a Contact, Delete a Contact |
| Opportunities | Watch Opportunities (Deprecated), List Opportunities, Get an Opportunity, Create an Opportunity, Update an Opportunity, Delete an Opportunity |
| Tasks | List Tasks, Get a Task, Create a Task, Update a Task, Delete a Task |
| Campaigns | Add a Contact to a Campaign, Delete a Contact from a Campaign |
| Notes | Add a Note to the Contact |
| Other | Make an API Call (any HighLevel API endpoint the connection's scopes allow) |
Make's marketing page for the app counts it differently: 4 triggers (including "Watch Events (legacy)"), 18 actions and 3 searches, and it shows an "Add an Account" action that the app docs don't list. Make labels Watch Opportunities as deprecated and says Watch Contact Updated will be deprecated, recommending Watch Events for both.
The app covers contacts, opportunities, tasks, notes and campaigns. For conversations, calendars, payments or anything else in HighLevel's API, use Make an API Call, which sends a custom request with the same connection. Calendly bookings don't need Make: HighLevel connects to Calendly natively, covered on the Calendly integration page.
How to connect Make to GoHighLevel
Make connects to HighLevel through OAuth, chosen per connection:
- In a Make scenario, add any GoHighLevel module and click Create a connection.
- Pick the connection type: GoHighLevel Location OAuth 2.0 for one sub-account, or GoHighLevel Company OAuth 2.0 for agency-level access.
- Optionally name the connection. Under Advanced settings you can enter your own client credentials instead of Make's.
- Click Save, sign in to HighLevel and approve access.
Watch Events needs more setup, because it receives webhooks. Make's docs say to create a private app in the HighLevel Marketplace, targeted at sub-accounts and installable by the agency only. You select scopes for webhooks and Auth (for example contacts.readonly and opportunities.readonly), publish the app and create a Client ID and Secret. Then you connect them in Make with the Events OAuth 2.0 type and paste Make's webhook URL into the app's Default Webhook URL field.
OAuth, API v2 and Private Integration tokens
Make's HighLevel app uses OAuth 2.0 on HighLevel's API v2. Make's documentation does not mention API keys or Private Integration tokens.
A Private Integration token is HighLevel's other way in. It is a static OAuth2 access token, made in the agency's settings under Private Integrations (turned on under Labs if missing), with scopes you pick. It goes in the Authorization header as a Bearer token. Unlike OAuth access tokens, which expire daily and refresh, it changes only when rotated. HighLevel recommends rotating every 90 days. "Rotate and expire this token later" keeps the old and new tokens working together for 7 days.
What Make costs
Make charges in credits, and by default one operation (one module run) uses one credit. The Free plan includes 1,000 credits a month. The paid self-serve plans are Core, Pro and Teams, with Enterprise on a quote. Make's pricing page says annual payment is cheaper than monthly. Core, Pro and Teams can turn on automatic purchase of 10,000 extra credits.
Each 10,000 credits a month also brings 5 GB of data transfer, 10 MB of data storage and a webhook queue of 667 items (10,000 maximum). Make's start-up plan gives organisations under 20 employees 50% off the Business plan.
Make's app adds no HighLevel charge. HighLevel only bills its own premium steps, such as the Inbound Webhook trigger or Custom Webhook action, at $0.01 a run after 100 free lifetime runs. The Workflow Pro plans run from Starter ($10 a month, 10,000 runs) to Scale ($50 a month, 65,000 runs).
Make vs Zapier vs HighLevel's own workflows
All three can move HighLevel data. The difference is where the automation lives and how it is billed.
| Make | Zapier | HighLevel workflows + webhooks | |
|---|---|---|---|
| What it is | Visual scenario builder, billed in credits | Zap builder, billed in tasks | Workflows inside HighLevel; webhooks send or receive data |
| HighLevel connection | Make's Verified app, OAuth 2.0 | Zapier's HighLevel app | Built in |
| Free tier | 1,000 credits a month | 100 tasks a month, two-step Zaps only, 15-minute polling | 100 lifetime premium runs per sub-account; standard actions are not charged as premium |
| Paid entry point | Core, Pro and Teams plans (prices on Make's pricing page) | Pro from $19.99 a month billed annually for 750 tasks | Workflow Pro Starter, $10 a month for 10,000 premium runs |
| Starting from an outside event | Webhook or watch module | Trigger app | Inbound Webhook trigger (premium), JSON only |
| Sending to an outside app | Any of Make's apps | Any of Zapier's apps | Custom Webhook action (premium), or a built-in integration |
Common Make and GoHighLevel setups
- New contact to Google Sheets. Watch Events in Make, filtered to contact events, then a Google Sheets "add a row" step. HighLevel also has its own Google Sheets workflow actions, which skip Make entirely.
- Outside form or app to HighLevel. A Make trigger from the other app, then Search Contacts and Create a Contact or Update a Contact to avoid duplicates, then Add a Contact to a Campaign.
- Deal to project tool. Watch Events for opportunity changes, then create a card or task in the project app.
- HighLevel workflow to Make. A Custom Webhook action posts to a Make webhook URL. Going the other way, Make posts JSON to an Inbound Webhook trigger, which accepts POST, GET or PUT and needs keys without spaces.
Limits to plan around
- HighLevel burst limit: 100 requests per 10 seconds, counted per Marketplace app per sub-account or agency.
- HighLevel daily limit: 200,000 requests per 24-hour window. Both windows start with the first request and do not reset at midnight.
- 429 errors have no Retry-After header. HighLevel says to read
X-RateLimit-RemainingandX-RateLimit-Daily-Remainingand wait 10 seconds after a burst rejection. - Private Integration tokens share one daily counter per sub-account or agency, separate from Marketplace apps such as Make's.
- Make instant triggers default to 100 runs per minute; extra requests queue.
- Inbound Webhook accepts JSON only. If the URL leaks, delete the trigger and make a new one.
Make doesn't publish the polling interval for each plan on the pages checked. Its help center only says the minimum depends on the plan. For other automation routes, see the GoHighLevel Shopify integration and GoHighLevel internal notifications. To have scenarios built for you, compare GoHighLevel CRM and automation agencies.
Frequently asked questions
Does Make.com integrate with GoHighLevel?
Yes. Make has a GoHighLevel app, marked Verified and maintained by Make. It connects by OAuth 2.0 to a sub-account (Location) or an agency (Company) and can watch events and create, update, find or delete contacts, opportunities and tasks, add notes and manage campaign enrolment.
Do I need a GoHighLevel API key to connect Make?
No. Make's HighLevel app connects through OAuth 2.0 and its documentation does not use API keys. A Private Integration token, created in HighLevel's settings, is a separate option for tools that call HighLevel API v2 directly with a Bearer token.
How do I trigger a Make scenario from a GoHighLevel workflow?
One route is Make's Watch Events module, which needs a private app in the HighLevel Marketplace with webhook scopes and its Default Webhook URL set to the Make webhook. The other route is a Custom Webhook action in a HighLevel workflow that calls a Make webhook URL. Custom Webhook is a premium action: 100 free lifetime runs per sub-account, then $0.01 a run without Workflow Pro.
How much does Make cost for GoHighLevel automations?
Make's Free plan includes 1,000 credits a month, and most module runs use one credit each. Core, Pro and Teams are paid plans priced on Make's pricing page, with cheaper rates for annual billing. HighLevel charges nothing extra for Make's app, but premium workflow steps such as webhooks are billed by HighLevel.
What are the GoHighLevel API rate limits for Make?
HighLevel's API 2.0 allows 100 requests per 10 seconds and 200,000 requests per day by default, counted per app per sub-account or agency. Requests over the limit get a 429 error with no Retry-After header, so a Make scenario that loops through many records should slow down rather than retry at once.
Should I use Make or Zapier with GoHighLevel?
Both connect to HighLevel. Zapier's Free plan has 100 tasks a month and two-step Zaps only, with paid plans from $19.99 a month billed annually. Make's Free plan has 1,000 credits a month, and most module runs use one credit. For steps HighLevel already has built in, such as Google Sheets rows, its own workflows avoid a second subscription.
Sources
All checked November 16, 2026.
- Make app documentation: GoHighLevel (created February 3, 2025; no update date)
- Make: GoHighLevel integration page (undated)
- Make: pricing (undated) and Make help: credits (undated)
- Make help: schedule a scenario (undated)
- HighLevel developer docs: rate limits (undated) and Private Integrations (undated)
- HighLevel help: Inbound Webhook premium trigger (last modified September 16, 2026)
- HighLevel help: workflow premium features and Workflow Pro (last modified September 28, 2026)
- Zapier: pricing (updated November 15, 2026)