Branch on tags and fields

What you'll get

• A workflow that splits: one path for people who match, another for everyone else.
• Both paths written out and connected properly, which is the part that is fiddly to do by hand and easy to get subtly wrong.
• A condition based on what you actually know about the person: a tag, a custom field, where they came from.

Say this

If they are tagged vip, send the VIP text. Otherwise send the standard one.

Split the follow-up: existing patients get one message, brand new leads get another.

Add a branch for anyone whose treatment interest field is Botox.

The pro prompt

In my [Radiance Med Spa] account, build a workflow called "[New Lead Split]".
Trigger: when the tag [new-lead] is added.
Then branch on this question: does the contact have the tag [vip]?
If yes: text "[Hi {{first name}}, it is Dana. Since you are one of our regulars I saved you a priority slot this week. Want it?]"
If no: text "[Hi {{first name}}, thanks for reaching out to Radiance. Want me to grab you a free consult this week?]"
Before you build: confirm both tags exist in my account, and show me the two paths side by side so I can check the split reads correctly. Build nothing until I approve.

Everything in [brackets] is yours to change. Ask for the two paths side by side every time. Reading them next to each other is how you catch a branch that is the wrong way round.

What Claude builds

What happens when you ask

1. Claude checks the tag or field you want to branch on actually exists in the account.
2. It shows you both paths, written out, before anything is built.
3. It builds the branch with both sides properly connected, then gives you the link to review in GHL.

Good to know

• Use branches sparingly. Two clean linear sequences with a tag deciding which one someone enters are usually easier to read and to fix later than one workflow with branches inside branches.
• Branch on tags where you can. Tags are simple and visible. Custom-field conditions work too, but you have to keep the field filled in.
• A branch with nothing on one side is legal and almost always a mistake. Say what happens to the people who do not match.
• Needs the full license.

Where people go wrong

Related guides

• Build a nurture sequence
• Audit your workflows