Enrich CRM contact data with LinkedIn profiles using GPT & multi-CRM support

1020 views

2/3/2026

GitLab Automation Project Management Issue Tracking DevOps

⚠️ 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 n8n workflow automates the enrichment of CRM contact data with professional insights from LinkedIn profiles. The workflow integrates with both Pipedrive and HubSpot CRMs, finding LinkedIn profiles that match your contacts and updating your CRM with valuable information about their professional background and recent activities.

Key Features

Multi-CRM Support: Works with both Pipedrive and HubSpot
AI-Powered Data Enrichment: Uses an advanced AI agent to analyze and summarize professional information
Automated Triggers: Activates when new contacts are added or when enrichment is requested
Comprehensive Profile Analysis: Captures LinkedIn profile summaries and post activity

How It Works

Triggers

The workflow activates in three scenarios:

When a new contact is created in CRM
When a contact is updated in CRM with an enrichment flag

LinkedIn Data Collection Process

Email Lookup: First tries to find the LinkedIn profile using the contact's email
Advanced Search: If email lookup fails, uses name and company details to find potential matches
Profile Analysis: Collects comprehensive profile information
Post Analysis: Gathers and analyzes the contact's recent LinkedIn activity

CRM Updates

The workflow updates your CRM with:

LinkedIn profile URL
Professional summary (skills, experience, background)
Analysis of recent LinkedIn posts and activity

Setup Instructions

Requirements

Self-hosted n8n instance with the HDW LinkedIn community node installed
API access to OpenAI (for GPT-4o)
Pipedrive and/or HubSpot account
AnySite API key https://AnySite.io

Installation Steps

Install the HDW LinkedIn Node:
```
npm install n8n-nodes-hdw
```
- Follow the detailed instructions at: https://www.npmjs.com/package/n8n-nodes-hdw
Configure Credentials:
- OpenAI: Add your OpenAI API key
- Pipedrive: Connect your Pipedrive account (if using)
- HubSpot: Connect your HubSpot account (if using)
- AnySite LinkedIn: Add your API key from https://AnySite.io
CRM Custom Fields Setup:

For Pipedrive:
- Go to Settings → Data Fields → Contact Fields → + Add Field
- Create the following custom fields:
  - LinkedIn Profile: Field type - Large text
  - Profile Summary: Field type - Large text
  - LinkedIn Posts Summary: Field type - Large text
  - Need Enrichment: Field type - Single option (Yes/No)
Detailed instructions for creating custom fields in Pipedrive: https://support.pipedrive.com/en/article/custom-fields

For HubSpot:
- Go to Settings → Properties → Create property
- Create the following properties for Contact object:
  - linkedin_url: Field type - Single-line text
  - profile_summary: Field type - Multi-line text
  - linkedin_posts_summary: Field type - Multi-line text
  - need_enrichment: Field type - Checkbox (Boolean)
Detailed instructions for creating properties in HubSpot: https://knowledge.hubspot.com/properties/create-and-edit-properties
Import the Workflow:
- Import the "HDW_CRM_Enrichment.json" file into your n8n instance
Activate Webhooks:
- Enable the webhook triggers for your CRM to ensure the workflow activates correctly

Customization Options

AI Agent Prompts

You can modify the system prompts in the "Data Enrichment AI Agent" nodes to:

Change the focus of profile analysis
Adjust the tone and detail level of summaries
Customize what information is extracted from posts

CRM Field Mapping

The workflow is pre-configured to update specific custom fields in Pipedrive and HubSpot. Update the field/property mappings in:

"Update data in Pipedrive" nodes
"Update data in HubSpot" node

Troubleshooting

Common Issues

LinkedIn Profile Not Found: Check if the contact's email is their work email; consider adjusting the search parameters
Webhook Not Triggering: Verify webhook configuration in your CRM
Missing Custom Fields: Ensure all required custom fields are created in your CRM with correct names

Rate Limits

Be aware of LinkedIn API rate limits (managed by AnySite LinkedIn node)
Consider implementing delays if processing large batches of contacts

Best Practices

Use enrichment flags to selectively update contacts rather than enriching all contacts
Review and clean contact data in your CRM before enrichment
Periodically review the AI-generated summaries to ensure quality and relevance

Enrich CRM Contact Data with LinkedIn Profiles using GPT (Multi-CRM Support)

This n8n workflow automates the process of enriching CRM contact data with information extracted from LinkedIn profiles using an AI agent powered by GPT. It supports multiple CRM systems, specifically Pipedrive and HubSpot, by dynamically routing based on the trigger event.

What it does

This workflow streamlines the process of finding and adding LinkedIn profile URLs and other relevant data to your CRM contacts:

Listens for CRM Triggers: The workflow is activated when a new or updated contact event occurs in either Pipedrive or HubSpot.
Identifies CRM Source: It determines which CRM system triggered the workflow (Pipedrive or HubSpot).
Extracts Contact Information: It extracts the contact's name and company from the CRM event.
Searches for LinkedIn Profile: An AI Agent (powered by OpenAI's GPT) is used to search for the contact's LinkedIn profile URL based on their name and company.
Updates CRM Contact:
- If the trigger was from Pipedrive, it updates the corresponding Pipedrive person with the found LinkedIn profile URL.
- If the trigger was from HubSpot, it updates the corresponding HubSpot contact with the found LinkedIn profile URL.

Prerequisites/Requirements

To use this workflow, you will need:

n8n Instance: A running n8n instance.
Pipedrive Account: With appropriate API access configured as an n8n credential.
HubSpot Account: With appropriate API access configured as an n8n credential.
OpenAI API Key: For the AI Agent (GPT) to function. This should be configured as an n8n credential for the "OpenAI Chat Model" node.

Setup/Usage

Import the workflow: Download the JSON provided and import it into your n8n instance.
Configure Credentials:
- Set up your Pipedrive credential in n8n.
- Set up your HubSpot credential in n8n.
- Set up your OpenAI API Key credential in n8n.
Activate Triggers:
- In the "Pipedrive Trigger" node, configure it to listen for the desired events (e.g., "Person updated" or "New Person").
- In the "HubSpot Trigger" node, configure it to listen for the desired events (e.g., "Contact created" or "Contact updated").
Configure AI Agent:
- In the "AI Agent" node, ensure the "OpenAI Chat Model" credential is selected.
- Review the prompt and tools used by the AI Agent to ensure it aligns with your specific LinkedIn search requirements.
Activate the Workflow: Once configured, activate the workflow. It will now automatically enrich your CRM contacts.

Note: The "Sticky Note" node is for documentation purposes within the workflow and does not require configuration.

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.

By 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

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

By Le Nguyen

942