Qualify and book AI sales calls with GPT-4o-mini and LeadConnector CRM
Needs changesWhat this workflow does
This AI workflow has 29 nodes and runs when an HTTP POST request hits its webhook URL (plus 1 other trigger). Along the way it connects OpenAI Chat Model, HTTP Request, Supabase and Postgres Chat Memory. It also calls services.leadconnectorhq.com over HTTP.
How it runs
Trigger: When an HTTP POST request hits its webhook URL (plus 1 other trigger).
- Switch: routes items into 2 branches
- Edit Fields (Edit Fields (Set)): sets 2 fields: startDate, endDate
- Get Appointments by Contact (HTTP Request): calls an HTTP API
- Supabase: get many
- Get Free Slots (HTTP Request): calls an HTTP API
- Set Event (Edit Fields (Set)): sets 1 field: events
- Get Chat History (Code): runs custom JavaScript code
- If: checks a condition and branches into true / false
- Update Event ID (HTTP Request): calls an HTTP API (PUT)
- Format Responses (Code): runs custom JavaScript code
…plus 4 more steps. See the full node list below.
Services it uses
HTTP calls to: services.leadconnectorhq.com
Before you upgrade to n8n 3.0
2 things in this workflow are removed in n8n 3.0. Fix them before you upgrade:
- HTTP Request Tool (legacy) in update_lead_dispostiotn, update_businesses_type, update_weekly_inquery…: replace with HTTP Request node connected to the AI Agent's Tool input.
- AI Agent v1 (old agent modes) in AI Agent (v1.6): replace with Latest AI Agent node (Tools Agent). For SQL Agent, use a Postgres or MySQL tool with a recent AI Agent.
Rather not rewrite it? Many of these flows can be rebuilt in Make (free plan).
| Removed in 3.0 | Replace with |
|---|---|
| HTTP Request Tool (legacy) update_lead_dispostiotn, update_businesses_type, update_weekly_inquery, update_current_response_times, update_team_sizes, update_operation_bottleneck, update_monthly_revenues, get_availability, reschedule_appointment, schedule_appointment, update_previous_experience_with_aIso | HTTP Request node connected to the AI Agent's Tool input |
| AI Agent v1 (old agent modes) AI Agent (v1.6) | Latest AI Agent node (Tools Agent). For SQL Agent, use a Postgres or MySQL tool with a recent AI Agent. |
Nodes used (12)
- HTTP Request
n8n-nodes-base.httpRequest - OpenAI Chat Model
@n8n/n8n-nodes-langchain.lmChatOpenAi - HTTP Request Tool
@n8n/n8n-nodes-langchain.toolHttpRequest - AI Agent
@n8n/n8n-nodes-langchain.agent - Webhook
n8n-nodes-base.webhook - Edit Fields (Set)
n8n-nodes-base.set - If
n8n-nodes-base.if - Respond to Webhook
n8n-nodes-base.respondToWebhook - Switch
n8n-nodes-base.switch - Supabase
n8n-nodes-base.supabase - Code
n8n-nodes-base.code - Postgres Chat Memory
@n8n/n8n-nodes-langchain.memoryPostgresChat
From the author
Quick Overview This workflow receives inbound lead messages from HighLevel (LeadConnector), pulls prior conversation history from Supabase/Postgres, uses OpenAI to generate a short reply, and updates HighLevel custom fields (qualification data, lead…