Extract LinkedIn from Apollo info

AI-Powered LinkedIn Username Extractor This workflow automates the data cleaning process for a lead list sourced from Apollo and stored in a Google Sheet. Its primary function is to take a full LinkedIn profile URL, extract the unique username from it, and update the lead's record in the sheet. This creates a clean, consistent data point that is crucial for subsequent outreach or scraping automations. Technologies Used - n8n: The automation platform coordinating the entire process. - Google Sheets: Acts as the database and trigger source for the lead list. - OpenAI: Provides the AI model (GPT-3.5-Turbo) used for intelligent data extraction. What it Automates This workflow automates a tedious and repetitive data enrichment task. Instead of a user manually copying a LinkedIn URL, removing the standard parts to get the username, and pasting it back into a spreadsheet, this system does it automatically. It creates a scalable, hands-off process for: - Lead List Monitoring: Continuously watches a Google Sheet for new leads that need processing. - Data Extraction & Cleaning: Intelligently parses URLs to extract a specific piece of information. - Data Entry & Status Management: Updates the spreadsheet with the cleaned data and marks the task as complete, ensuring each lead is processed only once. This saves significant time, reduces human error, and prepares data for other automated systems that might use the LinkedIn username as an input. How AI Integrates into the Flow The OpenAI node is the core of this workflow's intelligence. It is used to perform a specific data transformation task that can be tricky with traditional text functions or regular expressions. - The Task: An OpenAI model (gpt-3.5-turbo) is given a full LinkedIn profile URL (e.g., https://www.linkedin.com/in/username123/). - The Instruction: It is given a simple, direct prompt in plain English: "remove the http or https://www.linkedin.com/in/ from this...". - The Value: Using AI for this task provides significant value. It's more resilient than a rigid formula, easily handling variations like http://, https://, www. or no www., and trailing slashes.