Retrieve a LinkedIn contact’s name from a profile URL with LinkUp

Name: Retrieve a LinkedIn contact’s name from a profile URL with LinkUp
Availability: InStock
Author: Stéphane Heckel

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

Overview

Summary

This workflow retrieves a LinkedIn contact’s full name from their profile URL using the LinkUp AI Search API. It’s a lightweight alternative to web scraping or complex APIs — integrating neatly into your existing n8n automations.

How it works

The workflow reads LinkedIn URLs from a Data Table.
Each URL is sent to LinkUp via an HTTP Request node using natural language.
LinkUp returns the corresponding contact name.
The Data Table is automatically updated with the retrieved name.

How to use

Create a Data Table named LinkedInURL with two fields:

url (String)
name (String)

Add one or more LinkedIn profile URLs, for example: https://www.linkedin.com/in/stephaneheckel/
Store your LinkUp API key in the Settings component. You can get one at https://app.linkup.so/api-keys.
Run the workflow. The name field will populate with the correct LinkedIn names.

Requirements

LinkUp account
n8n version: tested on 1.122.4 (Ubuntu)

Need Help?

Feel free to comment this post. Contact me on LinkedIn or ask in the Forum!

Stéphane Heckel

6 workflows

Complexity

intermediate

Published 10 Mar 2026

Likes 0

View on n8n.io Download Workflow

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

Share Your Workflow

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

Submit Your Template How to Submit

Related Workflows

Qualify and route inbound leads with OpenAI, Trello, Slack and Gmail

## Description This n8n workflow automates a speed-to-lead system, capturing form submissions and quickly routing qualified leads to tools like Trello and Gmail for fast follow-up. ## Good to Know Speed-to-lead focuses on minimizing time from lead capture to sales engagement, boosting conversion rates. ## How it works - Triggers on form submission, feeding data into an AI Agent powered by an OpenAI Chat Model with chat memory. - The AI processes leads via a structured output parser, then a switch (rules mode) decides actions like editing fields or sending messages. - Outputs route to Trello (task creation), Gmail (notifications/emails), and possibly other apps for lead nurturing. ## How to use - Import the workflow into your n8n instance and connect credentials for OpenAI, Trello, Gmail, and your form tool (e.g., Google Forms). - Test by submitting a form; monitor the AI agent for lead qualification and verify outputs in Trello/Gmail. - Activate the workflow to run live, ensuring webhooks or triggers are set for production forms ## Requirements - n8n account (self-hosted or cloud); API keys for OpenAI, Trello, Gmail OAuth2. - Form tool integration (e.g., Google Forms webhook). - For verified creator status: Submit 2-3 approved public workflows via n8n Creator Portal, including this one, to gain the badge and directory listing.

View

Research LinkedIn prospects before sales calls with Bright Data and GPT-5.4

# Build AI-powered pre-call intelligence briefs from LinkedIn profiles Automatically scrape LinkedIn profiles for upcoming sales calls, analyze the data with AI, score prospect readiness, and send structured pre-call briefs to your inbox. This workflow reads upcoming call records from Google Sheets, scrapes each prospect's LinkedIn profile with Bright Data, extracts useful talking points and rapport hooks, and uses GPT-5.4 to generate a structured pre-call intelligence brief. It then applies confidence and readiness thresholds to decide whether to send a full brief, a shorter limited-data brief, or log the result for later review. ## How it works 1. A schedule trigger runs the workflow automatically. 2. The workflow reads upcoming prospect records from a Google Sheet tab called `upcoming_calls`. 3. Each LinkedIn profile URL is sent to the Bright Data dataset API for scraping. 4. The Bright Data response is validated to catch empty results, API errors, and async snapshot responses. 5. A code step extracts useful sales context such as: - career trajectory - role tenure - skills and tech affinity - education signals - recent activity themes - rapport hooks 6. GPT-5.4 analyzes the enriched profile data and returns a structured JSON brief with: - career trajectory summary - recent activity summary - 5 tailored talking points - likely pain points - readiness score - recommended approach - risk factors - self-evaluation metadata 7. The workflow parses the AI response and checks whether confidence is at least `0.7`. 8. If confidence is too low, the result is written to a `low_confidence_briefs` sheet for manual review. 9. If confidence is high enough, the workflow checks whether the readiness score is at least `70`. 10. High-readiness prospects receive a full email brief and are logged to the `call_briefs` sheet. 11. Lower-readiness prospects receive a shorter email brief and are also logged to the `call_briefs` sheet. ## Setup Create a Google Sheet with these tabs: - `upcoming_calls` - `call_briefs` - `low_confidence_briefs` The `upcoming_calls` tab should include at least: - `url` - `meeting_date` - `our_product` - `alert_email` (optional) Then configure the workflow: 1. Replace `YOUR_SPREADSHEET_ID` in the Google Sheets nodes with your sheet ID. 2. Connect Google Sheets via OAuth2. 3. Add your Bright Data credentials to the HTTP Header Auth used in the LinkedIn scraping node. 4. Connect your OpenAI account in the GPT-5.4 chat model node. 5. Connect Gmail via OAuth2 for sending the brief emails. 6. Optionally set a fallback alert email using the `ALERT_EMAIL` variable. ## Requirements - Google Sheets OAuth2 credentials - Gmail OAuth2 credentials - Bright Data account - OpenAI API access for GPT-5.4 ## Notes - This is a demo workflow intended for template and educational use. - The Bright Data response validator is built to handle empty results, API errors, and async responses gracefully. - The AI node is instructed to return raw JSON only, making the output easier to parse and route. - The confidence gate helps prevent unreliable AI output from being emailed. - The readiness score gate helps prioritize prospects that are more likely to lead to productive calls. - You can adjust the confidence threshold (`0.7`) and readiness threshold (`70`) to match your process. - The Gmail steps currently send plain-text summaries, which makes the workflow easy to customize. ## Good fit for - sales teams - founders doing outbound - agencies preparing for discovery calls - account executives who want better call prep - RevOps teams building lightweight pre-call research systems Note: This demo uses the synchronous Bright Data request because it is easier to understand in a template. In real workflows, it is often better to use the async approach. Bright Data’s sync endpoint has a 1 minute timeout, and longer jobs return a snapshot_id instead of final data. A simple way to build the async HTTP node in n8n is to copy Bright Data’s cURL example from your account or docs and convert it into an n8n HTTP Request setup

View

Automate social fan-out, marketplace outreach, and CRM alerts with Salesforce

⚠️ Heads up: this is satire. The "Hell Yeah!" workflow is a parody of "automate your whole life with AI agents" grindset content. The API endpoints are fictional and the function nodes are illustrative stubs. It's published as a template because the patterns underneath the joke — multi-channel social fan-out, marketplace scraping with follow-up sequences, CRM sync with chat alerts, cron-triggered daily chains — are genuinely useful starting points for n8n agencies building real lead-gen flows. Swap the jokes for your actual integrations and you've got a working skeleton. How it works A Rise and Grind cron kicks off a parallel "daily lifestyle" routine every morning A gambling → flex chain runs arbitrage math against a fake sportsbook and fans the "wins" out to Instagram, TikTok, Facebook, Threads, LinkedIn, and Twitter in one blast (this is the reusable multi-channel social posting pattern) A Facebook Marketplace lowball engine scrapes listings, filters them, fires templated lowball offers, and runs a relentless follow-up sequence (reusable pattern: scraper → filter → outreach → nurture) An eBay arbitrage loop finds profitable items, relists them, and logs every transaction to Google Sheets A Salesforce + Telegram branch handles "deal alerts" — the standard CRM-sync-with-chat-notification pattern every agency ships Extra satirical branches (Tinder auto-booking, Uber Black to the casino, steak delivery, playing Alice in Chains) are there for the bit — delete or replace them Set up steps Takes about 15–20 minutes if you're just importing to read through the patterns Takes 1–2 hours if you're stripping out the satirical branches and wiring the reusable patterns (social fan-out, marketplace outreach, CRM+Telegram) to your real credentials Replace every fictional HTTP endpoint with your actual API before activating Add credentials for whichever real nodes you keep: Salesforce, Telegram, Google Sheets, WhatsApp, Facebook Graph Detailed notes for each section live in the sticky notes inside the workflow itself

View

Need Custom Automation?

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

Retrieve a LinkedIn contact’s name from a profile URL with LinkUp

Workflow preview

Overview

Summary

How it works

How to use

Requirements

Need Help?