This page requires JavaScript to display.
The Nolan Scott Team Sells and buys businesses from $1M to $15M+, and advises on the real estate that comes with them. nolanscottteam.com →
Example 01 / 18 · a sample from our Rolodex of 100+ automations Make.com
Automation Breakdown · Make.com Scenario

LinkedIn Autopilot

Built in Make.com for a client whose LinkedIn now runs itself. Every inbound reply hits a webhook, Claude reads the full conversation and answers in the client’s voice within minutes, hot conversations get escalated by email, and every new lead is created in Close CRM automatically.

48 modules
3 campaign lanes
6 Claude calls
4 systems · HeyReach, Gmail, Close, Data store
True AI automation isn’t one clever workflow. It takes 20 to 40 workflows working together to make a real impact on a business. That’s what we do: a Rolodex of 100+ automations across different CRMs and platforms, ready to be custom-built for your specific CRM and software stack.
The Workflow
Three identical lanes, one per campaign · click any module for its explanation
LANE A
NEW REPLY
SEND
LOG
MARK READ
ESCALATE
MISSING CRM
LANE B
NEW REPLY
SEND
LOG
MARK READ
ESCALATE
STOP SEQ
LANE C
NEW REPLY
SEND
LOG
MARK READ
ESCALATE
STOP SEQ
MISSING CRM
W
Webhooks
HeyReach reply
+
Router
by campaign
HR
HeyReach
get conversation
+
Router
new reply?
A\
Anthropic Claude
classify + draft
+
Router
act on verdict
HR
HeyReach
send message
+
Router
post-send
DB
Data store
log exchange
⊕
HTTP
update HeyReach
⊕
HTTP
mark read
A\
Anthropic Claude
escalation summary
M
Gmail
escalation notification
DB
Data store
log escalation
C
Close CRM
search lead
C
Close CRM
create lead
C
Close CRM
create contact
≫
Skip
done
HR
HeyReach
get conversation
+
Router
new reply?
A\
Anthropic Claude
classify + draft
+
Router
act on verdict
HR
HeyReach
send message
+
Router
post-send
DB
Data store
log exchange
⊕
HTTP
update HeyReach
⊕
HTTP
mark read
A\
Anthropic Claude
escalation summary
M
Gmail
escalation notification
DB
Data store
log escalation
DB
Data store
mark stopped
⊕
HTTP
stop sequence
HR
HeyReach
get conversation
+
Router
new reply?
A\
Anthropic Claude
classify + draft
+
Router
act on verdict
HR
HeyReach
send message
+
Router
post-send
DB
Data store
log exchange
⊕
HTTP
update HeyReach
⊕
HTTP
mark read
A\
Anthropic Claude
escalation summary
M
Gmail
escalation notification
DB
Data store
log escalation
DB
Data store
mark stopped
⊕
HTTP
stop sequence
C
Close CRM
search lead
C
Close CRM
create lead
C
Close CRM
create contact
≫
Skip
done
◈
The scenario at a glance
Click any module on the canvas to see exactly what it does. One webhook fans into three campaign lanes; each lane replies with Claude, escalates hot leads by email, and syncs new people into Close CRM.
Webhook
Router
HeyReach (LinkedIn)
Anthropic Claude
Gmail
Data store
HTTP / API
Close CRM
How It Works

Every reply answered, every lead captured

01 · Intake
Webhook → lane

HeyReach fires a webhook the instant someone replies on LinkedIn. A router sorts the event into one of three lanes, one per outreach campaign, and the lane pulls the full conversation history, not just the last message.

02 · AI Reply
Claude answers in-voice

Claude reads the thread, classifies intent, and writes the reply in the client’s voice. A router then acts on the verdict: send it back through HeyReach, log the exchange to the data store, and mark the conversation read via the HeyReach API.

03 · Escalation
Humans for hot leads

When a conversation turns serious, pricing, a call request, a real objection, a second Claude call summarizes it and a Gmail notification goes straight to the automation’s owner. The AI can also stop the outreach sequence so no automated touch ever collides with a live deal.

04 · CRM Sync
Close, kept current

If the person isn’t in Close CRM yet, the scenario searches, creates the lead, and creates the contact, so by the time the client opens Close, everyone they’re talking to on LinkedIn already exists with the conversation on record.

Next example: LinkedIn Inbox Triage →
AI · nolan scott team
Unpacking...