HumationHuman + Automation
Back to Catalog

Automated LinkedIn lead generation, scoring & communication with AI-Agent

AndreyAndrey
15427 views
2/3/2026
Google SheetsArchiveJSON InputData MovementAutomation
Official Page

Screenshot 20250411 at 00.36.29.png

⚠️ DISCLAIMER: This workflow uses the AnySite LinkedIn community node, which is only available on self-hosted n8n instances. It will not work on n8n.cloud.

Overview

This workflow automates the entire LinkedIn lead generation process from finding prospects that match your Ideal Customer Profile (ICP) to sending personalized messages. It uses AI to analyze lead data, score potential clients, and prioritize your outreach efforts.

Key Features

  • AI-Driven Lead Generation: Convert ICP descriptions into LinkedIn search parameters
  • Comprehensive Data Enrichment: Analyze company websites, LinkedIn posts, and news
  • Intelligent Lead Scoring: Prioritize leads based on AI analysis of intent signals
  • Automated Outreach: Connect with prospects and send personalized messages

Requirements

  1. Self-hosted n8n instance with the AnySite LinkedIn community node installed
  2. OpenAI API access (for GPT-4o)
  3. Google Sheets access
  4. AnySite API key (available at anysite.io)
  5. LinkedIn account

Setup Instructions

1. Install Required Nodes

  • Ensure the AnySite LinkedIn community node is installed on your n8n instance
  • Command: npm install n8n-nodes-hdw (or use this instruction)

2. Configure Credentials

  • OpenAI: Add your OpenAI API key
  • Google Sheets: Set up Google account access
  • AnySite LinkedIn: Configure your API key from AnySite.io

3. Set Up Google Sheet

  • Create a new Google Sheet with the following columns (or copy template):
    • Name, URN, URL, Headline, Location, Current company, Industry, etc.
    • The workflow will populate these columns automatically

4. Customize Your ICP

  • Use chat to provide the AI Agent with your Ideal Customer Profile
  • Example: "Target marketing directors at SaaS companies with 50-200 employees"

5. Adjust Scoring Criteria

  • Modify the lead scoring prompt in the "Company Score Analysis" node to match your specific product/service
  • Tune the evaluation criteria based on your unique business needs

6. Configure Message Templates

  • Update the AnySite LinkedIn Send Message node with your custom message

How It Works

  1. ICP Translation: AI converts your ICP description into LinkedIn search parameters
  2. Lead Discovery: Workflow searches LinkedIn using these parameters
  3. Data Collection: Results are saved to Google Sheets
  4. Enrichment: System collects additional data about each lead:
    • Company website analysis
    • Lead's LinkedIn posts
    • Company's LinkedIn posts
    • Recent company news
  5. Intent Analysis: AI analyzes all data to identify buying signals
  6. Lead Scoring: Leads are scored on a 1-10 scale based on likelihood of interest
  7. Connection Requests: Top-scoring leads receive connection requests
  8. Follow-Up: When connections are accepted, automated messages are sent

Customization

  • Search Parameters: Adjust the AI Agent prompt to refine your target audience
  • Scoring Criteria: Modify scoring prompts to highlight indicators relevant to your product
  • Message Content: Update message templates for personalized outreach
  • Schedule: Configure when connection requests and messages are sent

Rate Limits & Best Practices

  • LinkedIn has connection request limits (approximately 100-200 per week)
  • The workflow includes safeguards to avoid exceeding these limits
  • Consider spacing your outreach for better response rates

Note: Always use automation tools responsibly and in accordance with LinkedIn's terms of service.

n8n Automated Lead Generation and AI Communication Workflow

This n8n workflow automates the process of extracting lead data from Google Sheets, evaluating leads using an AI agent, and potentially initiating communication or further actions based on the AI's assessment. It's designed to streamline lead qualification and interaction, making your sales or outreach efforts more efficient.

What it does

This workflow performs the following key steps:

  1. Triggers on a Schedule: The workflow is activated periodically (e.g., daily, hourly) to check for new leads.
  2. Reads Leads from Google Sheets: It fetches lead data from a specified Google Sheet, likely containing prospect information.
  3. Splits Data into Batches: To manage API limits and process leads efficiently, the workflow splits the retrieved data into smaller batches.
  4. Evaluates Leads with AI Agent: For each lead, an AI Agent (powered by OpenAI) is invoked. This agent uses a "Basic LLM Chain" and "Simple Memory" to process lead information and generate a structured output.
  5. Parses AI Output: A "Structured Output Parser" extracts specific, predefined data points from the AI agent's response, such as a lead score, interest level, or suggested next steps.
  6. Conditional Logic (If Node): The workflow includes an "If" node, which suggests that it can apply conditional logic based on the AI's evaluation (e.g., if a lead score is above a certain threshold, proceed to a different branch).
  7. Aggregates Results: After processing individual leads or batches, the "Aggregate" node combines the results, potentially consolidating the AI's assessments.
  8. Limits and Sorts Data: The "Limit" and "Sort" nodes indicate that the workflow can refine the list of leads further, perhaps by prioritizing high-scoring leads or focusing on a specific number of top prospects.
  9. Merges Data: A "Merge" node is present, suggesting that data from different branches or processing steps can be combined back together.
  10. Waits for a Period: A "Wait" node is included, which can be used to introduce delays, for example, to adhere to API rate limits or to space out follow-up actions.
  11. (Optional) Chat Trigger: A "Chat Trigger" node is present but not connected, indicating the potential to initiate the workflow or specific actions based on incoming chat messages, possibly for interactive lead qualification or follow-up.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running n8n instance.
  • Google Sheets Account: Access to a Google Sheet containing your lead data. You will need to configure Google Sheets credentials in n8n.
  • OpenAI API Key: An API key for OpenAI to power the AI Agent and Chat Model. You will need to configure OpenAI credentials in n8n.
  • Understanding of LangChain Concepts: Familiarity with LangChain's "Agents," "Chains," "Language Models," and "Memory" will be beneficial for configuring the AI components.

Setup/Usage

  1. Import the Workflow: Download the provided JSON and import it into your n8n instance.
  2. Configure Credentials:
    • Set up your Google Sheets credentials.
    • Set up your OpenAI credentials.
  3. Configure Google Sheets Node (ID: 18):
    • Specify the Spreadsheet ID and Sheet Name where your lead data is located.
    • Ensure the columns in your sheet match the expected input for the AI Agent.
  4. Configure AI Agent Node (ID: 1119):
    • Connect your OpenAI Chat Model (ID: 1153) and Simple Memory (ID: 1163) to the AI Agent.
    • Define the Agent's instructions and Tools (if any) to guide its lead evaluation process.
  5. Configure Structured Output Parser Node (ID: 1179):
    • Define the schema for the expected output from the AI Agent (e.g., leadScore: number, interestLevel: string, nextStep: string).
  6. Configure If Node (ID: 20):
    • Set up the conditions based on the parsed AI output (e.g., {{ $json.leadScore > 70 }}).
  7. Adjust Schedule Trigger (ID: 839):
    • Set the desired interval for the workflow to run.
  8. Activate the Workflow: Once configured, activate the workflow to start automating your lead generation and AI communication.

Related Templates

Track competitor SEO keywords with Decodo + GPT-4.1-mini + Google Sheets

This workflow automates competitor keyword research using OpenAI LLM and Decodo for intelligent web scraping. Who this is for SEO specialists, content strategists, and growth marketers who want to automate keyword research and competitive intelligence. Marketing analysts managing multiple clients or websites who need consistent SEO tracking without manual data pulls. Agencies or automation engineers using Google Sheets as an SEO data dashboard for keyword monitoring and reporting. What problem this workflow solves Tracking competitor keywords manually is slow and inconsistent. Most SEO tools provide limited API access or lack contextual keyword analysis. This workflow solves that by: Automatically scraping any competitor’s webpage with Decodo. Using OpenAI GPT-4.1-mini to interpret keyword intent, density, and semantic focus. Storing structured keyword insights directly in Google Sheets for ongoing tracking and trend analysis. What this workflow does Trigger — Manually start the workflow or schedule it to run periodically. Input Setup — Define the website URL and target country (e.g., https://dev.to, france). Data Scraping (Decodo) — Fetch competitor web content and metadata. Keyword Analysis (OpenAI GPT-4.1-mini) Extract primary and secondary keywords. Identify focus topics and semantic entities. Generate a keyword density summary and SEO strength score. Recommend optimization and internal linking opportunities. Data Structuring — Clean and convert GPT output into JSON format. Data Storage (Google Sheets) — Append structured keyword data to a Google Sheet for long-term tracking. Setup Prerequisites If you are new to Decode, please signup on this link visit.decodo.com n8n account with workflow editor access Decodo API credentials OpenAI API key Google Sheets account connected via OAuth2 Make sure to install the Decodo Community node. Create a Google Sheet Add columns for: primarykeywords, seostrengthscore, keyworddensity_summary, etc. Share with your n8n Google account. Connect Credentials Add credentials for: Decodo API credentials - You need to register, login and obtain the Basic Authentication Token via Decodo Dashboard OpenAI API (for GPT-4o-mini) Google Sheets OAuth2 Configure Input Fields Edit the “Set Input Fields” node to set your target site and region. Run the Workflow Click Execute Workflow in n8n. View structured results in your connected Google Sheet. How to customize this workflow Track Multiple Competitors → Use a Google Sheet or CSV list of URLs; loop through them using the Split In Batches node. Add Language Detection → Add a Gemini or GPT node before keyword analysis to detect content language and adjust prompts. Enhance the SEO Report → Expand the GPT prompt to include backlink insights, metadata optimization, or readability checks. Integrate Visualization → Connect your Google Sheet to Looker Studio for SEO performance dashboards. Schedule Auto-Runs → Use the Cron Node to run weekly or monthly for competitor keyword refreshes. Summary This workflow automates competitor keyword research using: Decodo for intelligent web scraping OpenAI GPT-4.1-mini for keyword and SEO analysis Google Sheets for live tracking and reporting It’s a complete AI-powered SEO intelligence pipeline ideal for teams that want actionable insights on keyword gaps, optimization opportunities, and content focus trends, without relying on expensive SEO SaaS tools.

Ranjan DailataBy Ranjan Dailata
161

Generate song lyrics and music from text prompts using OpenAI and Fal.ai Minimax

Spark your creativity instantly in any chat—turn a simple prompt like "heartbreak ballad" into original, full-length lyrics and a professional AI-generated music track, all without leaving your conversation. 📋 What This Template Does This chat-triggered workflow harnesses AI to generate detailed, genre-matched song lyrics (at least 600 characters) from user messages, then queues them for music synthesis via Fal.ai's minimax-music model. It polls asynchronously until the track is ready, delivering lyrics and audio URL back in chat. Crafts original, structured lyrics with verses, choruses, and bridges using OpenAI Submits to Fal.ai for melody, instrumentation, and vocals aligned to the style Handles long-running generations with smart looping and status checks Returns complete song package (lyrics + audio link) for seamless sharing 🔧 Prerequisites n8n account (self-hosted or cloud with chat integration enabled) OpenAI account with API access for GPT models Fal.ai account for AI music generation 🔑 Required Credentials OpenAI API Setup Go to platform.openai.com → API keys (sidebar) Click "Create new secret key" → Name it (e.g., "n8n Songwriter") Copy the key and add to n8n as "OpenAI API" credential type Test by sending a simple chat completion request Fal.ai HTTP Header Auth Setup Sign up at fal.ai → Dashboard → API Keys Generate a new API key → Copy it In n8n, create "HTTP Header Auth" credential: Name="Fal.ai", Header Name="Authorization", Header Value="Key [Your API Key]" Test with a simple GET to their queue endpoint (e.g., /status) ⚙️ Configuration Steps Import the workflow JSON into your n8n instance Assign OpenAI API credentials to the "OpenAI Chat Model" node Assign Fal.ai HTTP Header Auth to the "Generate Music Track", "Check Generation Status", and "Fetch Final Result" nodes Activate the workflow—chat trigger will appear in your n8n chat interface Test by messaging: "Create an upbeat pop song about road trips" 🎯 Use Cases Content Creators: YouTubers generating custom jingles for videos on the fly, streamlining production from idea to audio export Educators: Music teachers using chat prompts to create era-specific folk tunes for classroom discussions, fostering interactive learning Gift Personalization: Friends crafting anniversary R&B tracks from shared memories via quick chats, delivering emotional audio surprises Artist Brainstorming: Songwriters prototyping hip-hop beats in real-time during sessions, accelerating collaboration and iteration ⚠️ Troubleshooting Invalid JSON from AI Agent: Ensure the system prompt stresses valid JSON; test the agent standalone with a sample query Music Generation Fails (401/403): Verify Fal.ai API key has minimax-music access; check usage quotas in dashboard Status Polling Loops Indefinitely: Bump wait time to 45-60s for complex tracks; inspect fal.ai queue logs for bottlenecks Lyrics Under 600 Characters: Tweak agent prompt to enforce fuller structures like [V1][C][V2][B][C]; verify output length in executions

Daniel NkenchoBy Daniel Nkencho
601

Automate invoice processing with OCR, GPT-4 & Salesforce opportunity creation

PDF Invoice Extractor (AI) End-to-end pipeline: Watch Drive ➜ Download PDF ➜ OCR text ➜ AI normalize to JSON ➜ Upsert Buyer (Account) ➜ Create Opportunity ➜ Map Products ➜ Create OLI via Composite API ➜ Archive to OneDrive. --- Node by node (what it does & key setup) 1) Google Drive Trigger Purpose: Fire when a new file appears in a specific Google Drive folder. Key settings: Event: fileCreated Folder ID: google drive folder id Polling: everyMinute Creds: googleDriveOAuth2Api Output: Metadata { id, name, ... } for the new file. --- 2) Download File From Google Purpose: Get the file binary for processing and archiving. Key settings: Operation: download File ID: ={{ $json.id }} Creds: googleDriveOAuth2Api Output: Binary (default key: data) and original metadata. --- 3) Extract from File Purpose: Extract text from PDF (OCR as needed) for AI parsing. Key settings: Operation: pdf OCR: enable for scanned PDFs (in options) Output: JSON with OCR text at {{ $json.text }}. --- 4) Message a model (AI JSON Extractor) Purpose: Convert OCR text into strict normalized JSON array (invoice schema). Key settings: Node: @n8n/n8n-nodes-langchain.openAi Model: gpt-4.1 (or gpt-4.1-mini) Message role: system (the strict prompt; references {{ $json.text }}) jsonOutput: true Creds: openAiApi Output (per item): $.message.content → the parsed JSON (ensure it’s an array). --- 5) Create or update an account (Salesforce) Purpose: Upsert Buyer as Account using an external ID. Key settings: Resource: account Operation: upsert External Id Field: taxid_c External Id Value: ={{ $json.message.content.buyer.tax_id }} Name: ={{ $json.message.content.buyer.name }} Creds: salesforceOAuth2Api Output: Account record (captures Id) for downstream Opportunity. --- 6) Create an opportunity (Salesforce) Purpose: Create Opportunity linked to the Buyer (Account). Key settings: Resource: opportunity Name: ={{ $('Message a model').item.json.message.content.invoice.code }} Close Date: ={{ $('Message a model').item.json.message.content.invoice.issue_date }} Stage: Closed Won Amount: ={{ $('Message a model').item.json.message.content.summary.grand_total }} AccountId: ={{ $json.id }} (from Upsert Account output) Creds: salesforceOAuth2Api Output: Opportunity Id for OLI creation. --- 7) Build SOQL (Code / JS) Purpose: Collect unique product codes from AI JSON and build a SOQL query for PricebookEntry by Pricebook2Id. Key settings: pricebook2Id (hardcoded in script): e.g., 01sxxxxxxxxxxxxxxx Source lines: $('Message a model').first().json.message.content.products Output: { soql, codes } --- 8) Query PricebookEntries (Salesforce) Purpose: Fetch PricebookEntry.Id for each Product2.ProductCode. Key settings: Resource: search Query: ={{ $json.soql }} Creds: salesforceOAuth2Api Output: Items with Id, Product2.ProductCode (used for mapping). --- 9) Code in JavaScript (Build OLI payloads) Purpose: Join lines with PBE results and Opportunity Id ➜ build OpportunityLineItem payloads. Inputs: OpportunityId: ={{ $('Create an opportunity').first().json.id }} Lines: ={{ $('Message a model').first().json.message.content.products }} PBE rows: from previous node items Output: { body: { allOrNone:false, records:[{ OpportunityLineItem... }] } } Notes: Converts discount_total ➜ per-unit if needed (currently commented for standard pricing). Throws on missing PBE mapping or empty lines. --- 10) Create Opportunity Line Items (HTTP Request) Purpose: Bulk create OLIs via Salesforce Composite API. Key settings: Method: POST URL: https://<your-instance>.my.salesforce.com/services/data/v65.0/composite/sobjects Auth: salesforceOAuth2Api (predefined credential) Body (JSON): ={{ $json.body }} Output: Composite API results (per-record statuses). --- 11) Update File to One Drive Purpose: Archive the original PDF in OneDrive. Key settings: Operation: upload File Name: ={{ $json.name }} Parent Folder ID: onedrive folder id Binary Data: true (from the Download node) Creds: microsoftOneDriveOAuth2Api Output: Uploaded file metadata. --- Data flow (wiring) Google Drive Trigger → Download File From Google Download File From Google → Extract from File → Update File to One Drive Extract from File → Message a model Message a model → Create or update an account Create or update an account → Create an opportunity Create an opportunity → Build SOQL Build SOQL → Query PricebookEntries Query PricebookEntries → Code in JavaScript Code in JavaScript → Create Opportunity Line Items --- Quick setup checklist 🔐 Credentials: Connect Google Drive, OneDrive, Salesforce, OpenAI. 📂 IDs: Drive Folder ID (watch) OneDrive Parent Folder ID (archive) Salesforce Pricebook2Id (in the JS SOQL builder) 🧠 AI Prompt: Use the strict system prompt; jsonOutput = true. 🧾 Field mappings: Buyer tax id/name → Account upsert fields Invoice code/date/amount → Opportunity fields Product name must equal your Product2.ProductCode in SF. ✅ Test: Drop a sample PDF → verify: AI returns array JSON only Account/Opportunity created OLI records created PDF archived to OneDrive --- Notes & best practices If PDFs are scans, enable OCR in Extract from File. If AI returns non-JSON, keep “Return only a JSON array” as the last line of the prompt and keep jsonOutput enabled. Consider adding validation on parsing.warnings to gate Salesforce writes. For discounts/taxes in OLI: Standard OLI fields don’t support per-line discount amounts directly; model them in UnitPrice or custom fields. Replace the Composite API URL with your org’s domain or use the Salesforce node’s Bulk Upsert for simplicity.

Le NguyenBy Le Nguyen
942