Automations
Add an exit workflow
Cleanly pull people out of a sequence when they reply, tag them, and get you notified.
What you'll get
- A small four-step workflow that runs the moment someone replies: it takes them out of the nurture, tags them, writes a note on their record, and pings you.
- No more robot follow-ups landing after a real conversation has started. That single embarrassment is what this exists to prevent.
- A pattern you can attach to any sequence you already have, not just new ones.
Say this
Add an exit workflow to my New Lead Nurture so people drop out when they reply.
Anyone who books a consult should stop getting the follow-up texts.
Build the exit workflow for the sequence we just made.
The pro prompt
The exact ask we run on real client accounts
Proven liveBuild an exit workflow in my [Radiance Med Spa] account called "[New Lead Nurture] Exit". Trigger: when a contact replies to us on any channel while they are in [New Lead Nurture]. Then, in this order: (1) remove them from [New Lead Nurture], (2) add a note on their record saying they replied and when, (3) tag them [warm-lead], (4) notify [me] so a human picks it up. Before you build: confirm the exact workflow you are removing them from by looking it up in my account, and confirm the real user you are notifying. If either one does not exist, stop and tell me instead of guessing.
Click the box to select it, then press ⌘C (or Ctrl+C)
Everything in [brackets] is yours to change. The last paragraph is doing the heavy lifting. Exit workflows that point at the wrong thing fail in total silence.
What Claude builds
TriggerThey reply on any channel
StepRemove from the nurture
StepNote on the contact record: what they said, when
Tagwarm-lead
StepNotify you, so a human takes it from here
What happens when you ask
- Claude looks up the real workflow you want people removed from, and the real person to notify. Not names, actual records.
- It shows you the four steps for approval.
- It builds the exit workflow, then hands you the link to open it in GHL.
Good to know
- Build the main sequence first, then the exit workflow. The exit needs to point at a workflow that already exists.
- Four steps is the whole pattern: remove, note, tag, notify. Longer exits are where they start breaking.
- The notification has to name a real user in that account. GHL used to accept "everyone" and no longer does. Claude picks the user up from the account, so this is handled, but it is why an exit built by hand often fails.
- Needs the full license.
Where people go wrong
| What happened | The fix |
|---|---|
| "People still got the next text after replying." | The main sequence also needs stop-on-reply switched on. The exit removes them; stop-on-reply prevents the message already in flight. Ask for both. |
| "I deleted the nurture and the exit workflow broke." | They are a pair. If you delete or rebuild one, say "update the exit workflow to match" so it does not point at something gone. |
| "The notification never arrived." | It was pointed at a user who is no longer in the account. Run an audit and Claude will find it. |