LinkedIn lead generation: Auto DM system with comment triggers using Unipile & NocoDB

Open on n8n.io

$20/month : Unlimited workflows

2500 executions/month

Try free

THE #1 IN WEB SCRAPING

Scrape any website without limits

Try free

HOSTINGER

Early Deal
DISCOUNT 20%

Self-hosted n8n

Unlimited workflows - from $4.99/mo

Try free

#1 hub for scraping, AI & automation

6000+ actors - $5 credits/mo

Try free

Important notice

This workflow is provided as-is. Please review and test before using in production.

1. Workflow Overview

Short Description This LinkedIn automation workflow monitors post comments for specific trigger words and automatically sends direct messages with lead magnets to engaged users. The system checks c...

Best for

Lead Nurturing automation workflows
Multimodal AI automation workflows
advanced n8n builders looking for reusable templates

Tools used

n8n-nodes-base.httprequest, n8n-nodes-base.splitout, n8n-nodes-base.if, n8n-nodes-base.filter, n8n-nodes-base.code, n8n-nodes-base.nocodb, n8n-nodes-base.splitinbatches, n8n-nodes-base.wait

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Alexandra Spalato.

Original n8n.io source

1.1 Workflow description

Title: LinkedIn lead generation: Auto DM system with comment triggers using Unipile & NocoDB
Workflow name: LinkedIn lead generation: Auto DM system with comment triggers using Unipile & NocoDB

Short Description

This LinkedIn automation workflow monitors post comments for specific trigger words and automatically sends direct messages with lead magnets to engaged users. The system checks connection status, handles non-connected users with connection requests, and prevents duplicate outreach by tracking all interactions in a database.

Key Features

Comment Monitoring: Scans LinkedIn post comments for customizable trigger words
Connection Status Check: Determines if users are 1st-degree connections
Automated DMs: Sends personalized messages with lead magnet links to connected users
Connection Requests: Asks non-connected users to connect via comment replies
Duplicate Prevention: Tracks interactions in NocoDB to avoid repeat messages
Message Rotation: Uses different comment reply variations for authenticity
Batch Processing: Handles multiple comments with built-in delays

Who This Workflow Is For

Content creators looking to convert post engagement into leads
Coaches and consultants sharing valuable LinkedIn content
Anyone wanting to automate lead capture from LinkedIn posts

How It Works

Setup: Configure post ID, trigger word, and lead magnet link via form
Comment Extraction: Retrieves all comments from the specified post using Unipile
Trigger Detection: Filters comments containing the specified trigger word
Connection Check: Determines if commenters are 1st-degree connections
Smart Routing: Connected users receive DMs, others get connection requests
Database Logging: Records all interactions to prevent duplicates

Setup Requirements

Required Credentials

Unipile API Key: For LinkedIn API access
NocoDB API Token: For database tracking

Database Structure

**Table: leads

linkedin_id: LinkedIn user ID
name: User's full name
headline: LinkedIn headline
url: Profile URL
date: Interaction date
posts_id: Post reference
connection_status: Network distance
dm_status: Interaction type (sent/connection request)

Customization Options

Message Templates: Modify DM and connection request messages
Trigger Words: Change the words that activate the workflow
Timing: Adjust delays between messages (8-12 seconds default)
Reply Variations: Add more comment reply options for authenticity

Installation Instructions

Import the workflow into your n8n instance
Set up NocoDB database with required table structure
Configure Unipile and NocoDB credentials
Set environment variables for Unipile root URL and LinkedIn account ID
Test with a sample post before full use

1.2 Logical Blocks

This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.

2. Block-by-Block Analysis

Block 1 - Get Comments from Posts

Type / Role: n8n-nodes-base.httpRequest - httpRequest
Config choices: Version 4.2

Block 2 - Split Out1

Type / Role: n8n-nodes-base.splitOut - splitOut
Config choices: Version 1

Block 3 - Check if we are connected

Type / Role: n8n-nodes-base.if - if
Config choices: Version 2.2

Block 4 - Filter Comments with trigger

Type / Role: n8n-nodes-base.filter - filter
Config choices: Version 2.2

Block 5 - Send DM with Lead Magnet

Type / Role: n8n-nodes-base.httpRequest - httpRequest
Config choices: Version 4.2

Block 6 - Answer to comment

Type / Role: n8n-nodes-base.httpRequest - httpRequest
Config choices: Version 4.2

Block 7 - Create Message Rotation

Type / Role: n8n-nodes-base.code - code
Config choices: Version 2

Block 8 - Create a row

Type / Role: n8n-nodes-base.nocoDb - nocoDb
Config choices: Version 3

Block 9 - Ask For connection

Type / Role: n8n-nodes-base.httpRequest - httpRequest
Config choices: Version 4.2

Block 10 - Loop Over Items1

Type / Role: n8n-nodes-base.splitInBatches - splitInBatches
Config choices: Version 3

Block 11 - Wait

Type / Role: n8n-nodes-base.wait - wait
Config choices: Version 1.1

Block 12 - Split Out2

Type / Role: n8n-nodes-base.splitOut - splitOut
Config choices: Version 1

Block 13 - cursor

Type / Role: n8n-nodes-base.code - code
Config choices: Version 2

Block 14 - Merge1

Type / Role: n8n-nodes-base.merge - merge
Config choices: Version 3.2

Block 15 - Filter1

Type / Role: n8n-nodes-base.filter - filter
Config choices: Version 2.2

Block 16 - Create a row2

Type / Role: n8n-nodes-base.nocoDb - nocoDb
Config choices: Version 3

Block 17 - On form submission

Type / Role: n8n-nodes-base.formTrigger - formTrigger
Config choices: Version 2.2

Block 18 - Get all the rows where the dm is already sent

Type / Role: n8n-nodes-base.nocoDb - nocoDb
Config choices: Version 3

Block 19 - Get all the rows where the connection is already asked

Type / Role: n8n-nodes-base.nocoDb - nocoDb
Config choices: Version 3

Block 20 - If

Type / Role: n8n-nodes-base.if - if
Config choices: Version 2.2

Block 21 - Split Out

Type / Role: n8n-nodes-base.splitOut - splitOut
Config choices: Version 1

Block 22 - If1

Type / Role: n8n-nodes-base.if - if
Config choices: Version 2.2

Block 23 - Sticky Note

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 24 - Sticky Note1

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Showing the first 24 of 32 workflow blocks. Download the JSON for the full node graph.

3. Summary Table

Workflow	LinkedIn lead generation: Auto DM system with comment triggers using Unipile & NocoDB
Complexity	advanced
Nodes	32
Categories	Lead Nurturing, Multimodal AI
Author	Alexandra Spalato
Published	25 Aug 2025

4. Reproducing the Workflow from Scratch

1. Download the workflow JSON

Use the JSON export at /data/workflows/7844/7844.json as the source template for this automation.
2. Import the template into n8n

Open n8n, import the downloaded JSON, and review each node before activating the workflow.
3. Configure credentials and variables

Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
4. Test with sample data

Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
5. Activate and monitor

Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.

Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.

Download workflow JSON Original n8n.io source Lead Nurturing workflows Multimodal AI workflows

Frequently asked questions

What does LinkedIn lead generation: Auto DM system with comment triggers using Unipile & NocoDB do?

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Lead Nurturing, Multimodal AI use case.

Alexandra Spalato

5 workflows

Nodes

n8n-nodes-base.httprequest n8n-nodes-base.splitout n8n-nodes-base.if n8n-nodes-base.filter n8n-nodes-base.code n8n-nodes-base.nocodb n8n-nodes-base.splitinbatches n8n-nodes-base.wait

Complexity

advanced

Published 25 Aug 2025

Likes 0

View on n8n.io Download Workflow

Install path: /data/workflows/7844/7844.json

Share Your Workflow

Have a useful automation to share? Publish it and help the community.

Submit Your Template How to Submit

Related Workflows

Re-engage missed property viewings with Google Calendar, Gemini, Gmail, and WhatsApp

## Quick overview When a buyer misses a scheduled viewing, this workflow automatically sends an AI-personalized follow-up by email and WhatsApp using Google Gemini, then logs the outcome to Google Sheets, recovering leads that would otherwise go cold. ## How it works 1. Triggers every 15 minutes when a Google Calendar event is updated in the selected viewings calendar. 2. Checks the event title/summary and continues only if it contains the tag “no-show”. 3. Extracts the lead’s name, email, phone, property address, and scheduled viewing time from the calendar event details. 4. Sends the lead and viewing context to Google Gemini to generate an email message and a WhatsApp message in JSON format. 5. Parses and cleans the AI output into safe HTML for email and a trimmed plain-text WhatsApp message. 6. Sends the re-engagement email via Gmail and appends the follow-up outcome to a Google Sheets log. 7. If a phone number is available, sends the WhatsApp message and updates a Google Sheets status field to record that WhatsApp was sent. ## Setup 1. Connect credentials for Google Calendar, Gmail, Google Sheets, and a Google Gemini (PaLM) API key. 2. Select the correct Google Calendar (viewings calendar) and ensure missed appointments are consistently tagged with “no-show” in the event summary. 3. Create or choose a Google Sheets document and sheet, then fill in the document ID/URL, sheet name, and the columns expected by the append/update logging steps. 4. Configure WhatsApp credentials in n8n (or disable the WhatsApp branch) and ensure lead phone numbers are stored in the calendar event description in the expected format (e.g., Name: ... | Email: ... | Phone: ... |). ## Requirements - Before running this workflow, create a Google Sheet with these exact column headers: Record ID | Lead Name | Email | Phone | Property Address | Original Viewing Time | Email Sent | WhatsApp Sent | Email Message Text | WhatsApp Message Text | Timestamp ## Customization - Edit the AI prompt in "Draft Re-Engagement Messages" to change tone or language - Add SMS or other channels by duplicating the WhatsApp branch pattern - Adjust the "no-show" tag keyword if your calendar uses different terminology ## Additional info WhatsApp is optional. If you don't have WhatsApp Business Cloud API credentials, disable that branch — the email follow-up will still send normally. This template assumes calendar events are tagged with "no-show" in the title and include lead contact info in the event description (Name: ... | Email: ... | Phone: ... |).

View

Quote freight shipments via WhatsApp with Google Gemini, HighLevel, and Warp

## Quick overview Youtube Video: https://youtu.be/kO4LgKT6oME?si=VpUEz2LKuxMujrUp This workflow receives WhatsApp messages, checks the sender in HighLevel, and uses Google Gemini with Redis chat memory to collect shipment details, then requests an LTL quote from the Warp API, applies a commission, and replies with either a conversational prompt or a final freight quote. ## How it works 1. Receives an incoming WhatsApp message and only continues when the text body is not empty. 2. Looks up the sender’s phone number in HighLevel and stops contacts marked as Do Not Disturb from being processed further. 3. Uses a Google Gemini-powered agent with Redis chat memory to ask for missing contact and freight details in a fixed order, optionally creating the HighLevel contact or marking the lead as DND when the user opts out. 4. Parses the agent’s structured JSON output and checks whether the required shipment data collection is complete. 5. If data is incomplete, sends the agent’s conversational reply back to the user via WhatsApp. 6. If data is complete, posts the shipment details to the Warp LTL quote API, adds a configured commission percentage to the returned price, and sends the finalized quote back to the user via WhatsApp. ## Setup 1. Connect WhatsApp credentials for both the WhatsApp Trigger and WhatsApp “send message” actions, and configure the webhook in Meta/WhatsApp so inbound messages reach this workflow. 2. Add a HighLevel OAuth2 credential and confirm your HighLevel account has permission to search contacts, create contacts, and update the DND field. 3. Add a Google Gemini (PaLM) API credential and a Redis credential for chat memory, and ensure Redis is reachable from your n8n instance. 4. Add an HTTP Header Auth credential for the Warp API and verify the quote endpoint URL, headers, and request body fields match your Warp account requirements. 5. Adjust the commission percentage value (and any quoting assumptions like weight per pallet) to match your pricing policy.

View

Qualify web leads and send replies with Groq, Gmail, Sheets and Slack

## Quick Overview This workflow receives new lead form submissions via webhook, uses Groq (OpenAI-compatible Chat Completions) to score and draft a reply, then sends the email via Gmail, logs the lead to Google Sheets as a lightweight CRM, and posts a lead alert to Slack. ## How it works 1. Receives a POST request from your lead/contact form via a webhook. 2. Extracts and normalizes common form fields (name, email, message, service interest, phone, company) and stops if no email is provided. 3. Sends the lead details to Groq’s Chat Completions API to generate a lead score/tier, intent summary, urgency, a drafted reply email, and a Slack note. 4. Parses the Groq JSON response and flags leads as “hot” when the score is 8 or higher. 5. Sends the drafted reply to the lead using Gmail. 6. Appends the lead details and AI outputs to a Google Sheets “Leads-CRM” sheet and posts a formatted alert to a Slack channel. 7. Returns a JSON confirmation response to the original webhook request. ## Setup 1. Configure your form provider to POST submissions to the workflow’s webhook URL (path: `/new-lead`). 2. Add an HTTP Header Auth credential containing your Groq API key for the Groq Chat Completions request. 3. Connect Gmail OAuth2 credentials and set the desired Reply-To address (default is `[email protected]`). 4. Connect Google Sheets OAuth2 credentials and update the target spreadsheet and sheet to match your CRM columns. 5. Connect Slack credentials and choose the destination channel (default: `#leads`).

View

Need Custom Automation?

Get help designing a custom n8n workflow that connects your stack and fits your process.

LinkedIn lead generation: Auto DM system with comment triggers using Unipile & NocoDB

Workflow preview

Important notice

1. Workflow Overview

Best for

Tools used

Source and attribution

1.1 Workflow description

Short Description

Key Features

Who This Workflow Is For

How It Works

Setup Requirements

Required Credentials

Database Structure

Customization Options

Installation Instructions

1.2 Logical Blocks

2. Block-by-Block Analysis

Block 1 - Get Comments from Posts

Block 2 - Split Out1

Block 3 - Check if we are connected

Block 4 - Filter Comments with trigger

Block 5 - Send DM with Lead Magnet

Block 6 - Answer to comment

Block 7 - Create Message Rotation

Block 8 - Create a row

Block 9 - Ask For connection

Block 10 - Loop Over Items1

Block 11 - Wait

Block 12 - Split Out2

Block 13 - cursor

Block 14 - Merge1

Block 15 - Filter1

Block 16 - Create a row2

Block 17 - On form submission

Block 18 - Get all the rows where the dm is already sent

Block 19 - Get all the rows where the connection is already asked

Block 20 - If

Block 21 - Split Out

Block 22 - If1

Block 23 - Sticky Note

Block 24 - Sticky Note1

3. Summary Table

4. Reproducing the Workflow from Scratch

1. Download the workflow JSON

2. Import the template into n8n

3. Configure credentials and variables

4. Test with sample data

5. Activate and monitor

5. General Notes & Resources

Frequently asked questions