workflows.fit
Back to n8n workflows
n8n templateFreeBy Oneclick AI Squad

Send personalized LinkedIn auto-reply DMs with smart resource matching

This automated n8n workflow enables intelligent auto-replies to LinkedIn comments by sending personalized direct messages (DMs) with relevant resources. When users comment on your posts, the workflow monitors engageme...

MarketingCommunicationDevelopmentCore NodesSchedule TriggerLinked InFilterMerge
Loading interactive preview...

Template notes

This automated n8n workflow enables intelligent auto-replies to LinkedIn comments by sending personalized direct messages (DMs) with relevant resources. When users comment on your posts, the workflow monitors engagement, filters valid interactions, analyzes comment content using keyword matching, and delivers tailored responses via LinkedIn messaging. It ensures duplicate prevention, tracks all message deliveries, and maintains logs for monitoring and compliance.

Fundamental Aspects

1. Monitor posts: Every 5 minutes, the workflow fetches your 10 most recent LinkedIn posts 2. Collect comments: Retrieves all comments from each post (up to 20 per post) 3. Filter engagement: Removes your own comments and tracks previously contacted users 4. Smart matching: Analyzes comment text using keyword matching to determine the most relevant resource (eBook, webinar, template, tool, or checklist) 5. Personalize message: Creates a custom DM with the commenter's name and selected resource 6. Send and track: Delivers the message via LinkedIn and logs the interaction

Setup steps

1. Connect LinkedIn: Add your LinkedIn OAuth2 credentials to these nodes: - Fetch Recent Posts - Fetch Post Comments - Send DM via LinkedIn

2. Update resource URLs: Open the "Match Resource to Comment" node and replace all https://yourwebsite.com/... URLs with your actual resource links

3. Customize message (optional): Edit the "Build Personalized Message" node to adjust the DM template and tone

4. Test first: Click "Execute Workflow" to test before activating. Check the execution log to verify it works correctly