GoHighLevel tag events
With the GoHighLevel app connected, a tag added to a contact is enough to record an event in SalesControl: no workflow with a webhook, no JSON to paste. You set the “tag → event” rules once and from then on every time the tag is added it does its job: an event in the client’s Timeline or a trial event.
The same plan as the event webhooks (Starter and above) and the GoHighLevel app connected (Admin › Integrations › Calendars › GoHighLevel). You can prepare the rules before connecting it: the card tells you, and the rules start as soon as the app is connected.
Where to set them up
In Admin › Integrations › Webhooks, card GoHighLevel tag events, right below the Custom events card. Only admins see the card; the events it produces are visible to the whole team that can see the client.
The two scopes: who is the contact?
The same tag means different things depending on the sub-account you put it in, so every rule has a scope:
- Clients’ sub-accounts: the tag is on one of your clients’ sub-accounts, where the contacts are their leads. The event goes to the client the sub-account belongs to (the sub-account must be connected in the client’s page). Example: “appointment booked” → event “Appointment booked” in the client’s Timeline.
- Agency’s sub-account: the tag is on your agency’s sub-account, where the contacts are your clients. The event goes to the client linked to that contact; if the contact is not linked yet, SalesControl looks the client up by name. Example: “client active” → event “Activated”.
Creating a rule
- Press New rule and choose the scope.
- Type the tag, one per rule, as you write it in GoHighLevel: it is saved in lowercase. For suggestions pick a client (clients scope) or an agency sub-account (agency scope): the card reads its tags and offers them as you type.
- Choose what happens: Event in the client’s Timeline, with the event name (up to 80 characters), or Counts for the trial. The latter exists only for the clients scope: the trial leads arrive in the clients’ sub-accounts.
- Press Save rule.
Each tag can have only one rule per scope: if one already exists, the card tells you. In the list the switch turns a rule off without deleting it, the arrows change the order, Edit and Delete do what they say (deleting asks for confirmation and leaves the events already recorded alone). Up to 50 rules per agency. Every change ends up in the Activity log.
Every time the tag is added, it counts
An event is recorded when the tag is added to the contact: removing the tag records nothing. To count the same fact again for the same contact (a second appointment, say), have the GoHighLevel workflow remove and re-add the tag: every new addition is a new event. Adding a different tag, with no rule, to the contact does nothing.
For every contact, SalesControl remembers the tags that have a rule. The first time it receives a tag update for a contact it has nothing to compare with: every tag with a rule the contact carries at that moment counts once, even if it was there before. From then on only what gets added counts.
Agency contacts we cannot recognise
For the agency scope, if the contact is not linked to a client and the name is not enough to tell who it is (no client with that name, or more than one), the event is not lost: it goes to Events to match, in the Custom events card, labelled GHL tag · <tag>. If exactly one client has the contact’s name, the row arrives with that client already picked and the note Suggested: <name>, but nothing is matched on its own. Pick (or check) the client and confirm with Assign: the event enters the Timeline with its own date and the contact stays linked, so the next events from that contact arrive on their own. How the queue works is in the Timeline guide.
The tag that counts for the trial
With Counts for the trial every time the tag is added in the sub-account of a client with a running trial, one event counts towards the target; once the trial is closed, or without a trial, nothing counts. Target, window and closing stay those of the service. In the client page’s event log these events carry the GHL tag badge. The trial tag you had set in the Trial events (webhook) card has become a rule of this card: you will find it in the list already.
What about webhooks?
They stay: the Custom events webhook and the Trial events webhook keep working for anyone not using the GoHighLevel app, for Zapier and Make, or for events that do not start from a tag.
If something does not work
- No event: check that the rule is on, that the tag is spelled the same (case aside) and, for the clients scope, that the sub-account is connected in the client’s page.
- The tag was added twice but there is one event: the tag has to be removed between the two additions, otherwise for GoHighLevel it is still the same tag.
- The card says the GoHighLevel app must be reconnected to read the tags: press Reconnect in the GoHighLevel card, the app asked for a new permission.