| Step | Where to Click in GHL | What to Do |
|---|---|---|
| Step 1 | Create a Helper Trigger (Custom Field or Tag) | Since HighLevel's 'Contact Changed' trigger only monitors contact fields, add a custom dropdown named 'Add Collaborator' (listing your teammates) or use role tags like 'assign-specialist' on the contact record. |
| Step 2 | Configure the Assignment Workflow | Set the workflow trigger to 'Contact Changed' (filter: Add Collaborator is not empty) or 'Tag Added'. Under Actions, add 'Add Contact Follower' and select the matching team member. |
| Step 3 | Fire the Instant Internal Notification | Immediately after the Add Follower action, add 'Send Internal Notification'. Choose In-App Notification and SMS, set Recipient to 'Contact Followers' (or Particular User), and include the direct link ({{contact.url}}). Optionally add a final step to clear the trigger field so it can be reused. |
Build a Contact Follower Notification workflow in our GoHighLevel sub-account:
1. Trigger on 'Contact Changed' when custom field 'Add Collaborator' is updated, or on Tag Added 'assign-reviewer'.
2. Add an action 'Add Contact Follower' to assign the selected user to the contact.
3. Send an immediate High-Priority In-App Internal Notification to Contact Followers: 'You have been added as a collaborator on {{contact.name}}. Tap to view contact: {{contact.url}}'.
4. Clear the 'Add Collaborator' field so subsequent team assignments can re-trigger cleanly.
# 1. MCP Tool Call (ghl-crm-mcp)
{
"tool": "workflows_create_from_recipe",
"arguments": {
"location_id": "<YOUR_LOCATION_ID>",
"recipe": "contact_follower_instant_alert",
"clear_trigger_on_complete": true,
"dry_run": true
}
}
# 2. Or run via ghl-crm Rust CLI
ghl-crm workflows apply-recipe --location-id <YOUR_LOCATION_ID> --recipe follower-alert --dry-run
Fetch a real sample request inside your Inbound Webhook Trigger (never use the 'Test Workflow' button), add a native Format Data -> Format Phone Number (E.164) step first, and map the formatted phone and email into Create/Update Contact.
PLAYBOOK T24 · Workflows & AutomationThe native 'Stop on Response' toggle only stops the specific workflow that sent the message—it never removes leads from overlapping nurture or blast campaigns. Fix it by building a dedicated global Safety Net workflow triggered on Customer Replied with an explicit Remove from Workflow action.
PLAYBOOK T10 · Workflows & AutomationUse HighLevel's built-in Format Data, Math Operation, Goal Events, and Inbound/Outbound Webhook steps inside a single native workflow so contact history and error logs stay in one place.
PLAYBOOK T03 · Unified Inbox & ChatTrigger HighLevel DND immediately on opt-out keywords (STOP, CANCEL, UNSUBSCRIBE) and place an `ai-conv-paused` tag check before every Conversation AI workflow step.
Connect Claude Code, Cursor, or OpenAI Codex to our ghl-tools MCP Server & Rust CLI for 30-second sub-account checks and --dry-run previews—or start/upgrade your GoHighLevel plan through our partner link to unlock up to $612+ in ready-to-import kits (including GHL Workflow Recipe Pack ($47 — or Free with Trial)) and our weekly live clinics.