Stop logic for iMessage campaigns.
Re-check HubSpot, GoHighLevel, replies, and APIs before the next message sends.
Campaigns break when they ignore what already happened. Tuco re-checks HubSpot, GoHighLevel, Tuco replies, and external APIs before each message so no one gets a tone-deaf follow-up after they already booked.
Last updated:
Notes can stop the path.
If a rep logs “booked” or “met already”, the follow-up can stop before it fires.
Tags and activity count.
If GHL shows a tag, pipeline event, or recent activity, the wrong message never goes out.
Bring outside truth in.
Use your own endpoints to check status, lifecycle, inventory, credit, or any other yes/no gate.
Re-evaluate the path.
Tuco can check again after a wait period so conditions stay current when the next step is due.
Stop rule check
The path only sends if reality still matches.
48-hour wait finished. Re-checking HubSpot and GoHighLevel before the next message.
HubSpot note contains “demo booked”. Stop rule matched.
Campaign ended cleanly. No follow-up sent. Activity log updated.
Path result
Route or stop on contact properties, owners, lists, notes, and sync state.
Use GHL tags, recent activity, custom fields, and workflow events as campaign logic.
A campaign can pause for time, then check the CRM again right before the next message goes out.
Run the full path against a real lead to see why a branch matched or a stop condition fired.
Logic. From your stack.
Campaigns can stop when a note says booked, do not contact, already handled, or any other real-world outcome.
Use GHL tags and recent activity as live conditions so the branch matches what happened in the funnel, not what you hoped happened.
External APIs can decide whether a step should send, wait, reroute, or stop without forcing your team into spreadsheet hacks.
The simulator explains which rule matched, why the path moved, and where the campaign would stop for a specific lead.
A lead can book or reply while a wait timer is running. Tuco checks again before it sends the next step.
When the lead answers, outbound logic can stop and Knowledge Base can own the conversation from there.
Workflow
How the gate works.
The campaign waits. Then it asks the stack one more time.
Launch the path.
Set the outbound motion, then attach stop rules and branch conditions to each meaningful step.
Wait if needed.
The path can pause for hours, days, or until a signal appears in HubSpot or GoHighLevel.
Re-check live data.
Before the next message sends, Tuco reads notes, tags, properties, activity, and optional custom API data again.
Send, branch, or stop.
If the rule matches, the path stops or reroutes. If it does not, the next message goes out with confidence.
Campaigns should notice reality.
If the CRM knows the lead booked, replied, churned, or moved stages, the campaign should know it too. That is the difference between automation and noise.