HumationHuman + Automation
Back to Catalog

Export LinkedIn search results to Google Sheets using ConnectSafely.ai API

ConnectSafelyConnectSafely
40 views
2/3/2026
GitHubAutomationSecrets ManagementGistDoppler
Official Page

Who's it for

This workflow is built for sales professionals, recruiters, founders, and growth marketers who need to build targeted prospect lists from LinkedIn without risking their accounts. Perfect for anyone who wants to find decision-makers, build lead lists, or research target audiences at scale.

If you're running outbound campaigns, building ABM lists, sourcing candidates, or doing competitive research, this automation handles LinkedIn searches and exports results directly to your Google Sheet—no browser cookies, no session hijacking, no ban risk.

How it works

The workflow automates LinkedIn people searches by leveraging ConnectSafely.ai's compliant API, then exports structured results to Google Sheets or JSON files.

The process flow:

  1. Define your search parameters (keywords, location, job title, result limit)
  2. Execute the search via ConnectSafely.ai API
  3. Process and normalize the response data
  4. Export to Google Sheets for CRM import or further automation
  5. Optionally save as JSON file for data backup or processing

No LinkedIn cookies required. No browser automation. Platform-compliant searches that won't get your account restricted.

Watch the complete step-by-step implementation guide:

LinkedIn Search Export Automation Tutorial

Setup steps

Step 1: Get Your ConnectSafely.ai API Credentials

Obtain API Key:

  1. Log into ConnectSafely.ai Dashboard
  2. Navigate to Settings → API Keys
  3. Generate a new API key
  4. Copy your API key (you'll need this in the next step)

Add Bearer Auth Credential in n8n:

  1. Go to Credentials in n8n
  2. Click Add Credential → HTTP Bearer Auth
  3. Paste your ConnectSafely.ai API key
  4. Save the credential

Step 2: Configure Search Parameters

Open the Set Search Parameters node and customize your search:

| Parameter | Description | Example | |-----------|-------------|---------| | keywords | Search terms for profiles | CEO SaaS, Marketing Director | | location | Geographic filter | United States, San Francisco Bay Area | | title | Job title filter | Head of Growth, VP Sales | | limit | Maximum results to return | 100 (max varies by plan) |

Pro Tips:

  • Use specific keywords for better targeting
  • Combine title + keywords for precision (e.g., keywords: "B2B" + title: "VP Sales")
  • Start with smaller limits (25-50) for testing

Step 3: Configure Google Sheets Integration

3.1 Connect Google Sheets Account

  1. Go to Credentials → Add Credential → Google Sheets OAuth2
  2. Follow the OAuth flow to connect your Google account
  3. Grant access to Google Sheets

3.2 Prepare Your Google Sheet

Create a new Google Sheet with the following columns (the workflow will auto-populate these):

| Column Name | Description | |-------------|-------------| | profileUrl | LinkedIn profile URL | | fullName | Contact's full name | | firstName | First name | | lastName | Last name | | headline | LinkedIn headline/tagline | | currentPosition | Current job title | | company | Company name (extracted from headline) | | location | Geographic location | | connectionDegree | 1st, 2nd, or 3rd degree connection | | isPremium | LinkedIn Premium member (true/false) | | isOpenToWork | Open to work badge (true/false) | | profilePicture | Profile image URL | | extractedAt | Timestamp of extraction |

3.3 Configure the Export Node

  1. Open the Export to Google Sheets node
  2. Select your Google Sheets credential
  3. Enter your Document ID (from the sheet URL)
  4. Select the Sheet Name
  5. The column mapping is pre-configured for auto-mapping

Step 4: Test the Workflow

  1. Click the Manual Trigger node
  2. Click Test Workflow
  3. Verify:
    • Search executes successfully
    • Results appear in the Format Results output
    • Data exports to your Google Sheet
    • JSON file is generated (optional)

Customization

Search Parameter Combinations

Sales Prospecting:

keywords: "B2B SaaS"
location: "United States"
title: "VP of Sales"
limit: 100

Recruiting:

keywords: "Python Machine Learning"
location: "San Francisco Bay Area"
title: "Senior Engineer"
limit: 50

Founder Networking:

keywords: "Seed Series A"
location: "New York City"
title: "Founder CEO"
limit: 100

Extending the Workflow

Add to CRM: Connect the Format Results output to HubSpot, Salesforce, or Pipedrive nodes

Enrich Data: Add a loop to fetch full profile details for each result using the /linkedin/profile endpoint

Chain with Outreach: Connect to the LinkedIn Connection Request Workflow to automatically send personalized invites to your search results

Schedule Searches: Replace Manual Trigger with a Schedule Trigger to run daily/weekly searches

Output Data Format

Each result includes:

{
  "profileUrl": "https://www.linkedin.com/in/johndoe",
  "profileId": "johndoe",
  "profileUrn": "urn:li:member:123456789",
  "fullName": "John Doe",
  "firstName": "John",
  "lastName": "Doe",
  "headline": "VP of Sales at TechCorp | B2B SaaS",
  "currentPosition": "VP of Sales",
  "company": "TechCorp",
  "location": "San Francisco, California",
  "connectionDegree": "2nd",
  "isPremium": true,
  "isOpenToWork": false,
  "profilePicture": "https://media.licdn.com/...",
  "extractedAt": "2024-01-15T10:30:00.000Z"
}

Use Cases

Sales Prospecting: Build targeted lead lists of decision-makers at companies matching your ICP

Recruiting & Talent Sourcing: Find passive candidates with specific skills and experience levels

Market Research: Analyze competitor employee profiles and organizational structures

Event Planning: Build invite lists for webinars, conferences, or virtual events

Partnership Development: Identify potential partners and integration opportunities

Investor Research: Find founders and executives at companies in specific stages/verticals

Troubleshooting

Common Issues & Solutions

Issue: "No results found" error

  • Solution: Broaden your search parameters; try removing one filter at a time

Issue: Empty company field in results

  • Solution: Company is extracted from headline; some profiles may not include company in their headline format

Issue: API authentication errors

  • Solution: Verify your ConnectSafely.ai API key is valid and has proper permissions; check Bearer Auth credential format

Issue: Google Sheets not updating

  • Solution: Confirm OAuth credentials are valid; check that the sheet has write permissions

Issue: Fewer results than expected

  • Solution: LinkedIn limits search results; try more specific parameters or upgrade your ConnectSafely.ai plan

Issue: Rate limit errors

  • Solution: Add delay between multiple searches; check your API plan limits

Documentation & Resources

Official Documentation

Support Channels

Connect With Us

Stay updated with the latest automation tips, LinkedIn strategies, and platform updates:

Need Custom Workflows?

Looking to build sophisticated LinkedIn automation workflows tailored to your business needs?

Contact our team for custom automation development, strategy consulting, and enterprise solutions.

We specialize in:

  • Multi-channel prospecting workflows
  • AI-powered lead scoring and qualification
  • CRM integration and data synchronization
  • Custom search and enrichment pipelines
  • Bulk outreach automation with personalization

Export LinkedIn Search Results to Google Sheets using ConnectSafely.ai API

This n8n workflow automates the process of extracting LinkedIn search results using the ConnectSafely.ai API and then exporting that data into a Google Sheet. It's designed to streamline data collection for sales, marketing, or research purposes by easily capturing and organizing LinkedIn profile information.

What it does

  1. Manual Trigger: Initiates the workflow manually, allowing you to run it on demand.
  2. HTTP Request (ConnectSafely.ai API): Makes an API call to ConnectSafely.ai to retrieve LinkedIn search results.
  3. Code: Processes the raw JSON data received from the ConnectSafely.ai API, extracting relevant profile information and structuring it for further use.
  4. Edit Fields (Set): Renames and organizes the extracted data fields to ensure consistency and readability before being written to Google Sheets.
  5. Convert to File: Transforms the processed JSON data into a CSV format, which is suitable for direct import or appending to a spreadsheet.
  6. Google Sheets: Appends the CSV data as a new row (or rows) to a specified Google Sheet, effectively exporting the LinkedIn search results.

Prerequisites/Requirements

  • n8n Instance: A running instance of n8n.
  • ConnectSafely.ai API Key: An active account and API key for ConnectSafely.ai.
  • Google Account: A Google account with access to Google Sheets.
  • Google Sheets Credential in n8n: You will need to set up a Google Sheets credential in your n8n instance to allow the workflow to write data to your spreadsheets.

Setup/Usage

  1. Import the Workflow: Import the provided JSON into your n8n instance.
  2. Configure Credentials:
    • HTTP Request Node: Update the "HTTP Request" node with your ConnectSafely.ai API key and any necessary API endpoint details.
    • Google Sheets Node: Configure the "Google Sheets" node with your Google account credentials.
  3. Specify Google Sheet: In the "Google Sheets" node, specify the Spreadsheet ID and Sheet Name where you want the LinkedIn data to be exported.
  4. Customize Code Node (Optional): If the structure of the ConnectSafely.ai API response or your desired output fields change, you might need to adjust the JavaScript code within the "Code" node to correctly parse and extract the data.
  5. Execute Workflow: Click the "Execute workflow" button in the "Manual Trigger" node to run the workflow and export the data.

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