A client asks for something GoHighLevel can't do. Sort the request into four buckets before you say yes, then build it outside GHL and price it as fixed scope.
Short answer: Sort the request into one of four buckets before you quote it: a native feature you have not found yet, a workflow that calls an outside tool through a webhook, a build that needs its own database, or something GoHighLevel should not be asked to do at all. Most custom requests land in the second bucket and are built with n8n, Zapier or a small custom app that talks to GoHighLevel through its API. Keep GoHighLevel as the place your client's staff work, and price the outside piece as its own fixed-scope project with a named owner and an error alert.
Agency owners on the GoHighLevel subreddit keep asking the same thing: what do you do when a client needs a custom automation that GoHighLevel, and sometimes any CRM, can't handle natively? The mistake is answering yes or no to the client's wording. Clients describe an outcome ("when the job closes in our software, text the customer and ask for a review"), and your job is to work out which of four things it really is.
| Bucket | What it looks like | Where you build it |
|---|---|---|
| 1. Native, not found yet | A calendar setting, a workflow action, a custom value, a smart list filter you have not tried | Inside GoHighLevel, tested in a sandbox contact first |
| 2. Webhook and a workflow | A lookup, a rule or a message that depends on another system | A workflow webhook action, n8n or Zapier, then an API call back |
| 3. Needs memory | Running totals, usage counts, history across many records | A small database such as Supabase between GoHighLevel and the other system |
| 4. Wrong tool | The client wants GoHighLevel to be their ERP, dispatcher or full project manager | Not in GoHighLevel. Say so plainly |
Bucket one is more common than agencies like to admit. Before you promise anything custom, rebuild the request by hand on a test contact and see how far native tools get you. Bucket four is where you protect the relationship: if a client wants dispatching, read what we wrote on dispatching and job scheduling in GoHighLevel before you agree to fake it.
For bucket two the pattern is nearly always the same. A GoHighLevel workflow reaches a webhook action and sends the contact's data to an n8n or Zapier URL. That tool does the part GoHighLevel can't: it looks up a record in the client's other software, runs a calculation or checks a rule. It then calls the GoHighLevel API to update a custom field or add a tag, and a second workflow triggered by that field or tag carries on inside GoHighLevel.
The client's staff never leave GoHighLevel. They see a field change and a message go out, and they do not need to know a second tool exists. If you are choosing between tools, our comparison of Zapier, n8n and a custom API for GoHighLevel covers when each is the right call, and the webhook debugging guide covers the first thing you will need when a test does not fire.
A custom field holds one value on one contact. The moment the request involves a running total, a count across many records, a change history or a calculation over a billing period, you need somewhere to store state. We hit exactly this on a usage-based billing system between GoHighLevel and Stripe: GoHighLevel sends the events, a Supabase database counts them, n8n moves the data, and Stripe gets the bill. The case study and the how-to article show the shape of it.
You do not need a database for every request, and adding one early makes the project heavier than it should be. Add it when a field or a tag can no longer represent the truth.
A custom automation rarely fails loudly. A webhook stops firing because someone edited the workflow. An API token expires. A custom field gets renamed during a cleanup and the outside tool keeps writing to a field that no longer exists. Three weeks later the client notices that review requests stopped, and your agency is the one explaining.
Put these into the scope of every custom piece, not into a wish list:
The same thinking applies to the rest of the account, which is why we wrote up how to stop clients breaking workflows after handoff.
Do not fold a custom build into the monthly retainer. A build has a start, a test and a finish, and a retainer hides all three. Quote it as its own project with milestones: discovery and a written spec, the build against test data, a run with real data, then handoff. Each milestone has something the client can see, and "done" means the test contact completes the full path and the alert fires when you break it on purpose.
This is also how we work with agencies. Yotomations prices fixed-scope milestones, with no hourly billing and no mandatory retainer, so you know your cost before you quote your client. Several agency owners in that thread were asking for exactly this kind of per-job help instead of another retainer. You can read more on our page for agencies.
If the request is bucket two, you know n8n or Zapier, and the other system has a documented API, build it yourself and charge for it. Bring in an engineer when the build touches payments, when it has to sync both ways with the client's system of record, when volume is high, or when a failure would mean a customer is billed or messaged wrongly. Those are the jobs where the cost of a silent failure is bigger than the cost of the build.
Also be honest with yourself about what GoHighLevel does not do through its API. We covered one common assumption in can you create GoHighLevel workflows with the API, and the answer shapes how you design these builds.
Send us the client's request in the client's own words, not your summary of it. On a free 30-minute discovery call (book here) we sort it into the four buckets, tell you which tools it needs, and give you a fixed-scope quote with milestones. If it turns out to be a setting you missed, we will say so. When it needs real engineering, that is what our custom integrations service is for.
Yaakov (Koby) Oranski, Founder and CEO of Yotomations
Certified GoHighLevel Admin and Partner. Koby designs CRM migrations, two-way integrations, billing systems and AI agents for service businesses, and writes from the engagements described on this site.
First check whether it is really unsupported, because many requests turn out to be a setting, a custom field or a workflow action nobody has tried. If it is truly outside GoHighLevel, send the data out with a workflow webhook, do the logic in n8n, Zapier or a small app, and write the answer back to a custom field or tag. If it needs a different kind of software altogether, tell the client so.
For many requests, yes. A webhook in, a few steps of logic and an API call back is exactly what n8n and Zapier do well. Move to a custom app or a database when you need counting across many records, heavy volume, two-way sync with a system of record, or tighter control over errors.
Usually not. A custom build has a defined start, a test and a finish, which fits a fixed-scope project with milestones. Retainers hide the cost of the build and make it hard to say when the work is done.
Name one owner, add an alert that fires when the webhook or API call fails, keep a test contact that runs the full path, and write down every custom field and tag the automation depends on. Most breakage comes from a renamed field, an expired token or a workflow someone edited without knowing it was connected.
The question that keeps SaaS founders up at night: you have 50 or 100 sub-accounts on one master snapshot and need to ship an update. A versioning and rollout process that does not break every account.
Learn more
What the HighLevel Certification program actually tests, who should earn it, what it signals when you hire, and how to verify that a partner really holds it.
Learn more
SaaS Pro turns GoHighLevel into software you sell. What SaaS mode, rebilling, the white-label app and the advanced AI actually give you, and the point where the $497 plan pays for itself.
Learn moreBook a 30-minute call. We look at the account live and tell you what is broken, what we would fix first and what it would cost.
No pitch deck. We look at your current setup and tell you what we would do and what it would cost.Need more than GoHighLevel? Yotomations, our parent company, also builds AI agents, custom software and websites.
