Skip to content
← SaaS, CRM & Operations

Draft — in editorial review, not yet published. Content has not been approved by a human reviewer.

Lesson 28 / 50 · Version 2.2.0

GoHighLevel Funnels and Workflows

Level
Beginner–Intermediate
Duration
15 min learn + 15 min apply
Prerequisites:
Lessons 11 and 27

Why it matters: All-in-one tools make it easy to launch follow-up fast, and just as easy to message people too often or create duplicate opportunities. Clear definitions and enrollment rules prevent both.

By the end you can:

  • Distinguish funnel, contact, opportunity, pipeline, and workflow
  • Design a consent-aware follow-up sequence
  • Set enrollment and re-enrollment rules
  • Test safely

Learn (15 min)

1. Roles of the pieces (5 min)

  • Funnel: the ordered pages a prospect sees (landing page → form → booking → thank-you).
  • Contact: the person's record.
  • Opportunity: a potential sale, moving through a pipeline of stages.
  • Workflow: an automation that starts on an event, applies conditions, waits, and acts. Keep these separate: page views, people, and deals are different things.

2. Design the workflow (5 min)

Define before enabling: trigger (form submitted), enrollment (who qualifies), re-enrollment (can the same person run it again?), conditions, waits, actions, and exit rules.

Trigger: Form "Team Headshots Inquiry" submitted
If: consent = yes AND phone/email present
Actions: create/update contact → create opportunity (Pipeline: Corporate, Stage: New)
         → assign owner → send confirmation (permitted channel) → task for owner
Wait 2 days: if no booking → send one helpful follow-up
Exit: booked, unsubscribed, or replied

3. Prevent bad automation (5 min)

Check consent and communication preferences before any message, and provide a clear stop/unsubscribe path. Decide whether one contact may have multiple open opportunities. Test with internal records, review the execution log, and check CRM state before opening it to real leads.

Apply (15 min)

Worked example (3 min). Prospect submits a team inquiry and books a call. Workflow stops the follow-up sequence on booking, moves the opportunity to "Consult booked," and creates a prep task. If the booking is canceled, the opportunity returns to "Follow up" with a task for the owner. Repeat submissions update the existing opportunity (no new one within 30 days).

Lab (7 min): Draw the workflow.

  1. Write the trigger, enrollment condition, and re-enrollment rule.
  2. List actions in order with waits and exit conditions.
  3. Add a consent check and an unsubscribe handling rule.
  4. List three internal test records and expected results.

Deliverable: A workflow diagram or list. You're done when: A duplicate submission can't create a second opportunity or a second message.

Check yourself (5 min)

  1. Contact vs. opportunity?
  2. What does a pipeline represent?
  3. Why define re-enrollment?
  4. Scenario: A prospect gets three identical emails in one day. What setting did you miss?
  5. How do you test safely?

Reference

Common mistakes

SymptomLikely causeFix
Repeated messagesRe-enrollment allowedDefine once-only or cooldown
Duplicate opportunitiesNo duplicate ruleUpdate existing within a window
Messaging without permissionNo consent checkGate on recorded consent

Cheat sheet: Funnel event → identify contact → dedupe → opportunity/pipeline → consent-aware follow-up → monitor.

Key terms: funnel, contact, opportunity, pipeline, workflow, enrollment.

Interview prompts: How would you prevent duplicate follow-ups in an automated funnel?

Go deeper: HighLevel pipelines & opportunities · Creating pipelines · Pipeline-stage trigger · Create Opportunity action

Next: Lesson 29 — a flexible database.