A client of ours was running a cold email sequence in GoHighLevel, and we found the emails were landing in spam. That kind of problem gets worse every hour it keeps sending. The sequence had to stop now, not whenever someone could get to a screen.
The obvious move is to unpublish it. That turned out to be impossible from outside the app. But there was another way that did the same job in seconds.
Why You Cannot Just Switch It Off From Outside
GoHighLevel has a behind the scenes connection that other tools can use to read and change things in your account. For sequences (GoHighLevel calls them workflows), that connection only lets you see the list: each sequence's name and whether it is published. It cannot open one, edit one, or change it from published to draft. Only a person clicking inside GoHighLevel can do that.
So "we cannot unpublish it, we have to wait for someone" looks like the only answer. It was the wrong conclusion.
The Real Pause: Empty the Sequence
A sequence only sends to the people inside it. The same connection that cannot unpublish a sequence can take a person out of one. Take everyone out, and every waiting email stops at once. The sequence is still published, but with nobody in it, nothing goes out.
Find every person currently going through the sequence.
Take each person out of that sequence. Their pending emails are cancelled straight away.
Open the sequence list in GoHighLevel and confirm the active count shows zero.
When someone can log in, they switch the sequence off by hand too.
We did exactly this and then checked in GoHighLevel itself: the number of people active in the sequence had dropped to zero. The sending had stopped.
Waiting for someone to unpublish
- The sequence keeps sending until a person logs in
- Every hour of spam makes the problem worse
- The task sits blocked on whoever is free
Emptying the sequence
- Sending stops in seconds
- The sequence itself is untouched and fully reversible
- A blocked task becomes a finished one
Two Things to Know Before You Do It
People lose their place
Taking someone out of a sequence means they no longer remember which step they were on. That was fine for our client, because the plan was to start those people again from the beginning. If each person's place matters to you, get someone to unpublish the sequence instead.
It can fill back up
Because the sequence stays published, whatever normally puts people into it (for example a tag being added to a contact) can put them back in. That is why the hand unpublish still needs to happen once someone is available.
Think about how many people are in the sequence before you clear it. A small group where you know everyone is easy to clear. A large, mixed group on an older sequence deserves an explicit yes from the owner first.
Two More Lessons From the Same Day
Updating tags can wipe the old ones
When you change a contact's tags through that same connection, the new list replaces every tag the contact had. It does not add to them. So always read the contact's current tags first and send back the full set you want, or you quietly lose tags that show where each lead came from.
Do not report numbers you cannot see
The access we had did not include message history, so we could not see opens or delivery for each person. The right move is to say what you can check and name the gap, never to guess an open rate for a client.
A quick test before trusting a computer to click for you: parts of GoHighLevel do not respond to automated clicking. The sequence editor can show up blank, and the sequence list can look normal in a screenshot but ignore clicks. Before spending time, have it click something harmless, like the "Published" filter, and take a screenshot. If nothing changed, the clicks are not getting through. Stop there and give a person the exact steps to click instead.
Common Questions
Can I unpublish a GoHighLevel sequence without logging in to the app?
No. GoHighLevel's outside connection for other tools can list your sequences and show whether each one is published, but it cannot switch one from published to draft. Only a person clicking inside GoHighLevel can do that. What the connection can do is take people out of a sequence, and that is what actually stops the sending.
If I remove everyone from a sequence, can I undo it?
Yes, it is reversible. The sequence itself is untouched and stays published, so you can put people back in later. The one thing you lose is each person's place in the sequence, so it suits a plan where you will start them again from the beginning.
Is emptying a sequence enough on its own?
It stops the emails straight away, but because the sequence is still published, anything that normally puts people into it can put them back in. So once someone can get into GoHighLevel, they should also unpublish it by hand.
Key Takeaways
- GoHighLevel's outside connection can list sequences but cannot unpublish them. Only a person in the app can.
- Taking every person out of a sequence stops all waiting emails at once. That is the real pause.
- Check afterwards in GoHighLevel that the active count shows zero.
- People lose their place, and the sequence can refill, so unpublish it by hand when someone is free.
- Updating tags from outside replaces them all, so read first and send the full set.