GoHighLevel Triggers: Every Type and When to Use Which

A trigger is the event that starts a workflow. Choosing the wrong one is the most common cause of automations that fire twice, fire for the wrong people, or quietly never fire at all.

What a trigger is

Every workflow needs at least one trigger, and can have several. The trigger answers "when does this run". Filters attached to the trigger answer "for whom".

That separation matters. People frequently build three near-identical workflows because they think they need one per form, when they actually need one workflow with one trigger and a filter that branches inside it.

The trigger families

Choosing the right one

The rule: pick the most specific trigger that describes the real event. Specific triggers are traceable. Generic ones become mysteries in six months.

Why "contact created" is usually wrong for lead response: contacts are created by imports, by manual entry, by integrations and by every form on the account. A workflow triggered on contact creation will one day fire at two thousand imported contacts, and somebody will have a bad afternoon.

Filters do the real work

Filters narrow which instances of an event count. Nearly every trigger supports them, and using them well means fewer workflows to maintain.

• Form submitted filtered to a specific form, so one workflow does not respond to every form on the site.
• Stage changed filtered to a specific pipeline and stage, so a quote follow-up does not fire on an unrelated pipeline.
• Inbound message filtered by channel, so SMS and Facebook get different handling.
• Tag added filtered to the exact tag, because "any tag added" is chaos.

Re-entry and duplicate sends

Every workflow has a re-entry setting controlling whether a contact already inside can enter again.

Turn it off by default. Allowing re-entry means a contact who submits a form twice receives the whole sequence twice, simultaneously and out of step. Turn it on only where repetition is genuinely intended, such as an appointment reminder workflow that should run for every booking.

Duplicate sends have three common causes, in order of frequency:

1. Two triggers on one workflow matching the same event. Form submitted and contact created both fire on a new lead.
2. Two workflows with overlapping triggers. Often an old one nobody remembered to pause.
3. Re-entry allowed where it should not be.

To diagnose, open the contact and look at their workflow history. It shows which trigger admitted them and when, which is faster than reasoning about it from the builder.

Trigger mistakes

• Using contact created for lead response. It will eventually fire at an import.
• Tag triggers everywhere. Convenient to build, untraceable to debug. Anything can add a tag.
• No filter on a form trigger. Every form on the account now runs the same sequence.
• Re-entry left on. Duplicate sequences running in parallel.
• Old workflows left published. Pause anything you have superseded, do not just stop editing it.
• No quiet hours. A trigger firing at 3am sends at 3am unless the workflow says otherwise.
• Testing with a real contact. Use a test contact with your own number, or your best customer receives the draft.