All documentation
Conditional rules
A field mapping moves a value across as it is. A rule makes a decision. Rules are how you get GoHighLevel to react to something about a job, usually by adding a tag your workflows can trigger from.
You will find them under Sync Settings → Step 4, Advanced. They are entirely optional — most accounts never need one.
How a rule reads
Every rule is the same shape — three dropdowns and a value:
| You pick | Example | |
|---|---|---|
| If | Something on the job card, and what it should be | Job status equals Unsuccessful |
| Then | What should happen in GoHighLevel | Add tag non-buyer |
What you can match on
Anything on the job card — status, category, badge, queue, invoice total, dates, or any other field. The comparisons available:
- equals / does not equal — exact match. Most rules use this.
- contains / does not contain — useful for descriptions and free text.
- starts with / ends with — for reference numbers and the like.
- is one of — match several values at once, separated by commas.
- is greater than / less than (or equal to) — for job values.
- is empty / is not empty — catch missing information.
What a rule can do
Add a tag. The common one. Tags added by rules stack up, so several rules can each add their own without wiping the others.
Set a field to a fixed value. Put a specific value into any GoHighLevel field, including your own custom fields.
Three that earn their keep
| If | Then | Why |
|---|---|---|
| Job status equals Unsuccessful | Add tag non-buyer |
The quote did not land — drop them into long-term nurture instead of losing them. |
| Total invoice amount is greater than 2000 | Add tag high-value |
Big jobs get a personal call, not an automated email. |
| Category name equals EICR | Add tag eicr-renewal |
Certificate work sets up its own renewal reminder five years out. |
Order of play
So a rule can deliberately override something you have mapped. That is useful when you want a general mapping with an exception on top — map the normal case, then write one rule for the case that behaves differently.
As always, run Sync Preview on a real job card and check the rule fires the way you expect before it goes anywhere near GoHighLevel. If the tag does not appear in the preview, the condition is not matching.