{"slug":"ghl-conversation-ai-pipeline-filter","title":"GHL Conversation AI: Filter Bot to Only Respond to Engaged Pipeline Leads","tags":["ghl","conversation-ai","pipeline","workflow"],"agent_summary":"How to configure GoHighLevel's conversation AI bot to only respond to leads in a specific pipeline stage (e.g., 'Engaged') using Find Opportunity node and If/Else conditions, since the bot trigger doesn't natively filter by pipeline stage.","trigger_phrases":["conversation ai only respond to certain leads","filter ghl bot by pipeline stage","conversation ai engaged leads only","ghl bot pipeline filter setup","limit conversation ai to specific stage","if else pipeline stage conversation ai"],"runnable":true,"markdown":"## Filtering GHL Conversation AI by Pipeline Stage\n\n### Problem\nThe GHL Conversation AI bot triggers on all inbound SMS messages. You need it to ONLY respond to leads in the \"Engaged\" pipeline stage, not every contact.\n\n### Solution Architecture\n\n1. **Find Opportunity Node Required** — The If/Else condition in the conversation AI workflow does NOT have pipeline stage as a filter option by default. You must add a \"Find Opportunity\" action BEFORE the If/Else to unlock the opportunities condition folder.\n\n2. **Workflow Structure:**\n ```\n Chat Initiated (trigger)\n → Find Opportunity (most recently created)\n → If/Else: Pipeline Stage = \"Sales Pipeline\" > \"Engaged\"\n → True: Continue to bot logic (intent splitter, etc.)\n → False: End workflow\n ```\n\n3. **Critical Gotcha:** If you delete the Find Opportunity node, you lose access to the pipeline stage conditions in If/Else. The error message says: \"Please add an opportunities trigger or find opportunities action to enable this condition.\"\n\n### Tag-Based Alternative (If Pipeline Filter Fails)\n\nIf native pipeline filtering doesn't work reliably:\n\n1. Create tag: `bot-eligible`\n2. In your SMS classification workflow (N8N), when a lead is classified as \"interested\" and pushed to \"Engaged\" stage, also add the `bot-eligible` tag via GHL API\n3. In conversation AI workflow: If/Else → Contact has tag `bot-eligible` → True continues, False ends\n4. Create a separate cleanup workflow: When pipeline stage changes AWAY from Engaged, remove the `bot-eligible` tag\n\n### Auto Follow-Up Configuration\n\n- GHL conversation AI supports max **5 auto follow-up touches**\n- Minimum interval is **1 day** (24 hours) — cannot do hours\n- Recommended cadence: Day 1, Day 2, Day 4, Day 7, Day 10\n- Follow-ups only fire when the lead **ghosts mid-conversation**\n- Randomize timing slightly (don't send at exactly the same time daily) to avoid spam patterns\n\n### Bot Goals\n\n- Configure under Bot Goals tab → Appointment Booking\n- When bot successfully books, the existing native GHL automation moves them to \"Booked\" pipeline stage automatically\n- No need for the bot to handle pipeline movement\n\n### Key Settings to Enable\n\n- **Image recognition**: ON (lets bot understand photos leads send)\n- **Voice note reading**: ON (lets bot transcribe and understand voice messages)\n- **Human handover**: Not needed for cold outreach leads (they're responding to direct outreach, not banging down the door)\n","html":"

Filtering GHL Conversation AI by Pipeline Stage

\n

Problem

\n

The GHL Conversation AI bot triggers on all inbound SMS messages. You need it to ONLY respond to leads in the \"Engaged\" pipeline stage, not every contact.

\n

Solution Architecture

\n
    \n
  1. \n

    Find Opportunity Node Required — The If/Else condition in the conversation AI workflow does NOT have pipeline stage as a filter option by default. You must add a \"Find Opportunity\" action BEFORE the If/Else to unlock the opportunities condition folder.

    \n
    2. \n
  2. \n

    Workflow Structure:

    \n
    Chat Initiated (trigger)\n→ Find Opportunity (most recently created)\n→ If/Else: Pipeline Stage = \"Sales Pipeline\" > \"Engaged\"\n  → True: Continue to bot logic (intent splitter, etc.)\n  → False: End workflow\n
    \n
    3. \n
  3. \n

    Critical Gotcha: If you delete the Find Opportunity node, you lose access to the pipeline stage conditions in If/Else. The error message says: \"Please add an opportunities trigger or find opportunities action to enable this condition.\"

    \n
    4. \n
\n

Tag-Based Alternative (If Pipeline Filter Fails)

\n

If native pipeline filtering doesn't work reliably:

\n
    \n
  1. Create tag: bot-eligible
    2. \n
  2. In your SMS classification workflow (N8N), when a lead is classified as \"interested\" and pushed to \"Engaged\" stage, also add the bot-eligible tag via GHL API
    3. \n
  3. In conversation AI workflow: If/Else → Contact has tag bot-eligible → True continues, False ends
    4. \n
  4. Create a separate cleanup workflow: When pipeline stage changes AWAY from Engaged, remove the bot-eligible tag
    5. \n
\n

Auto Follow-Up Configuration

\n\n

Bot Goals

\n\n

Key Settings to Enable

\n\n"}