Guardrails · n8n template
Pause Automations When A Human Replies
The moment a real team member messages a contact, every automated sequence for that contact stops — so leads never get a human reply and a bot nudge in the same minute.
The problem
This is the failure that makes clients distrust automation entirely. A salesperson has a real conversation going, and the follow-up sequence keeps firing underneath it. The lead sees a personal message followed by an obviously templated one, concludes the whole thing was a bot, and disengages.
What this workflow does
The workflow inspects every outbound message event and distinguishes human-sent messages from workflow, campaign, bulk and API sends. When a human takes over, the contact is pulled out of every active sequence, tagged so reporting can see it, and the handoff is logged to a sheet for review.
How it works
- Your CRM posts every outbound message event to the webhook.
- A Code node classifies the source — a message only counts as human if it has a user ID and did not come from an automated source.
- Non-human sends are ignored so the workflow stays cheap to run.
- Human sends remove the contact from all active sequences and tag them human-took-over.
- The handoff is appended to a Google Sheet so you can audit how often bots are being overridden.
What it connects
- n8n
- GoHighLevel
- Google Sheets
Get the template
The download is the raw n8n JSON. Import it via Workflows → Import from File, replace the YOUR_* placeholders with your own IDs, and connect your own credentials. Nothing is pre-filled and no account of ours is referenced.