Skip to main content

LinkedIn auto message router and responder with request detection

Workflow preview

Workflow preview
100%
LinkedIn auto message router and responder with request detection preview
Open on n8n.io

Important notice

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

1. Workflow Overview

Who is this for? Public facing professionals (developer advocates, founders, marketers, content creators) who get bombarded with LinkedIn messages that aren't actually for them support requests whe...

Best for

  • Ticket Management automation workflows
  • AI Summarization automation workflows
  • advanced n8n builders looking for reusable templates

Tools used

n8n-nodes-base.webhook, n8n-nodes-base.if, n8n-nodes-base.noop, n8n-nodes-base.set, n8n-nodes-base.respondtowebhook, n8n-nodes-base.slack, n8n-nodes-base.stickynote, n8n-nodes-base.switch

Source and attribution

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

Original n8n.io source

1.1 Workflow description

Title
LinkedIn auto message router and responder with request detection
Workflow name
LinkedIn auto message router and responder with request detection

Who is this for?

Public-facing professionals (developer advocates, founders, marketers, content creators) who get bombarded with LinkedIn messages that aren't actually for them - support requests when you're in marketing, sales inquiries when you're a devrel, partnership pitches when you handle content, etc.

What problem is this workflow solving?

When you're visible online, people assume you handle everything at your company. You end up spending hours daily playing human router, forwarding messages like "How do I reset my password?" or "What's your enterprise pricing?" to the right teams. This LinkedIn automation workflow stops you from being your company's unofficial customer service representative.

What this workflow does

This AI-powered LinkedIn DM management workflow automatically assesses incoming LinkedIn messages and routes them intelligently:

  1. Automated Message Assessment: Receives inbound LinkedIn messages via UniPile and looks up sender details from both personal and company LinkedIn profiles.

  2. Smart Route Matching: Compares the message content against your message routing workflow table in Notion, which contains:

  • Question: "How can I become an n8n ambassador?"
  • Description: "Route here when a user is requesting to become an n8n ambassador. Also when they're asking how they could do more to evangelize n8n in their city, or to start organizing n8n meetups and events in their city."
  • Action: "Tell the user to open the following notion page which has details on ambassador program including how to apply, as well as perks of the program: https://www.notion.so/n8n-Ambassador-Program-d883b2a130e5448faedbebe5139187ea?pvs=21"
  1. AI Response Generation: When a message matches an existing route, this AI assistant generates a personalized response draft based on the "Action" instructions from your routing table.

  2. Human-in-the-Loop Approval: Sends the draft response to Slack with approve/reject buttons, so you maintain control while saving time. Draft can be edited from within Slack on desktop and mobile.

  3. Automated LinkedIn Responses: Once approved, sends the reply back via LinkedIn and marks the original message as handled.

The result: You stop being a human switchboard and can focus on your actual job while people still get helpful, timely responses through automated customer service. You can also add routes for things you do handle but get asked about daily (like 'How do I join your beta?' or 'What's your content strategy?') to standardize your responses.

Setup

  1. Sign up for a UniPile account and create a webhook under the Messaging section
  2. Set the callback URL to this workflow's production URL
  3. Generate a UniPile API key with all required scopes and store it in your n8n credentials
  4. Create a Slack app and enable interactive message buttons and webhooks

Here is a slack App manifest template for easy deployment in slack:

{
    "display_information": {
        "name": "Request Router",
        "description": "A bot that alerts when a new linkedin question comes in.",
        "background_color": "#12575e"
    },
    "features": {
        "bot_user": {
            "display_name": "Request Router",
            "always_online": false
        }
    },
    "oauth_config": {
        "scopes": {
            "bot": [
                "chat:write",
                "chat:write.customize",
                "chat:write.public",
                "links:write",
                "im:history",
                "im:read",
                "im:write"
            ]
        }
    },
    "settings": {
        "interactivity": {
            "is_enabled": true,
            "request_url": "Your webhook url here"
        },
        "org_deploy_enabled": false,
        "socket_mode_enabled": false,
        "token_rotation_enabled": false
    }
}
  1. Set up your Notion database with the three-column structure (Question, Description, Action)
  2. Configure the AI node with your preferred provider (OpenAI, Gemini, Ollama etc)
  3. Replace placeholder LinkedIn user and organization IDs with your own

How to customize this workflow to your needs

  • Database Options: Swap Notion with Google Sheets, Airtable, or another database
  • Filtering Logic: Add custom filters based on keywords, message length, follower count, or business logic
  • AI Customization: Adjust the system prompt to match your brand tone and response goals
  • Approval Platform: Replace Slack with email, Discord, or another review platform
  • Team Routing: Use Slack metadata to route approvals to specific team members based on message category
  • Enrichment: Add secondary data enrichment using tools like Clearbit or FullContact
  • Response Rules: Create conditional logic for different response types based on sender profile or message content

Perfect for anyone who's tired of being their company's accidental customer service department while trying to do their real job.

This LinkedIn automation template was inspired by a live build done by Max Tkacz and Angel Menendez for The Studio.

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 - Webhook

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

Block 2 - Check if from me

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

Block 3 - Response, No action

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

Block 4 - New Message

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

Block 5 - Global Variables

Type / Role
n8n-nodes-base.set - set
Config choices
Version 3.4

Block 6 - Slack Button Press

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

Block 7 - Parse Webhook

Type / Role
n8n-nodes-base.set - set
Config choices
Version 3.4

Block 8 - Verify Webhook

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

Block 9 - Check if approved

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

Block 10 - Send User Message

Type / Role
n8n-nodes-base.slack - slack
Config choices
Version 2.3

Block 11 - Send Org Message

Type / Role
n8n-nodes-base.slack - slack
Config choices
Version 2.3

Block 12 - Send Nothing Found Message

Type / Role
n8n-nodes-base.slack - slack
Config choices
Version 2.3

Block 13 - Sticky Note

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

Block 14 - Sticky Note11

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

Block 15 - Decide on Message Type

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

Block 16 - User Switcher

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

Block 17 - Isolate Message and Payload

Type / Role
n8n-nodes-base.set - set
Config choices
Version 3.4

Block 18 - Isolate Payload

Type / Role
n8n-nodes-base.set - set
Config choices
Version 3.4

Block 19 - Send webhook to Coworker Workflow

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

Block 20 - Send Message to LinkedIn via Unipile

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

Block 21 - Delete Approved Message from Slack

Type / Role
n8n-nodes-base.slack - slack
Config choices
Version 2.3

Block 22 - Delete Denied Message from Slack

Type / Role
n8n-nodes-base.slack - slack
Config choices
Version 2.3

Block 23 - AI Agent

Type / Role
@n8n/n8n-nodes-langchain.agent - agent
Config choices
Version 1.9

Block 24 - Simple Memory

Type / Role
@n8n/n8n-nodes-langchain.memoryBufferWindow - memoryBufferWindow
Config choices
Version 1.3

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

3. Summary Table

Workflow LinkedIn auto message router and responder with request detection
Complexity advanced
Nodes 52
Categories Ticket Management, AI Summarization
Author Angel Menendez
Published 12 Jun 2025

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/4889/4889.json as the source template for this automation.

  2. 2. Import the template into n8n

    Open n8n, import the downloaded JSON, and review each node before activating the workflow.

  3. 3. Configure credentials and variables

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

  4. 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. 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.

Frequently asked questions

What does LinkedIn auto message router and responder with request detection do?

Who is this for? Public facing professionals (developer advocates, founders, marketers, content creators) who get bombarded with LinkedIn messages that aren't actually for them support requests whe...

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 Ticket Management, AI Summarization use case.