How it works
Why triage replies
A LinkedIn reply is more valuable than a passive signal. It should create priority action, not disappear inside an inbox.
n8n recipe
Turn LinkedIn replies into a prioritized processing queue.
This recipe reads conversations or reply signals, classifies intent, and routes each contact to the right next action.
What the workflow covers
Nodes and logic
This page describes the recipe publicly; importable JSON files remain protected by API access.
Detect
Fetch recent conversations or reply signals.
Recommended window: 24 to 72 hours.
Classify
Classify intent before any automated action.
Positive, objection, support, neutral.
Route
Send each reply to the right owner.
CRM task, Slack channel, or support backlog.
Verified facts
What the tool should clarify before being used.
Use caseBuilt to avoid forgotten warm replies when several lists or sequences run in parallel.
Expected outputRead recent LinkedIn replies.
Method proofRecommended window: 24 to 72 hours.
Verification method
How to turn the template into an actionable step.
- 01 Detect Recommended window: 24 to 72 hours.
- 02 Classify Positive, objection, support, neutral.
- 03 Route CRM task, Slack channel, or support backlog.
How it works
Keep human review
The workflow can prioritize and prepare the next step, but sensitive replies should stay reviewed before sending.
