HumationHuman + Automation
Back to Catalog

LinkedIn profile finder via form using Bright Data & GPT-4o-mini

Miquel ColomerMiquel Colomer
7804 views
2/3/2026
AI VisionWebhookGoogle CloudImage AnalysisGoogle Gemini
Official Page

image.png

This n8n workflow template automates the process of finding LinkedIn profiles for a person based on their name, and company. It scrapes Google search results via Bright Data, parses the results with GPT-4o-mini, and delivers a personalized follow-up email with insights and suggested outreach steps.

🚀 What It Does

  • Accepts a user-submitted form with a person’s full name, and company.
  • Performs a Google search using Bright Data to find LinkedIn profiles and company data.
  • Uses GPT-4o-mini to parse HTML results and identify matching profiles.
  • Filters and selects the most relevant LinkedIn entry.
  • Analyzes the data to generate a buyer persona and follow-up strategy.
  • Sends a styled email with insights and outreach steps.

🛠️ Step-by-Step Setup

  1. Deploy the form trigger to accept person data (name, position, company).
  2. Build a Google search query from user input.
  3. Scrape search results using Bright Data.
  4. Extract HTML content using the HTML node.
  5. Use GPT-4o-mini to parse LinkedIn entries and company insights.
  6. Filter for matches based on user input.
  7. Merge relevant data and generate personalized outreach content.
  8. Send email to a predefined address.
  9. Show a final confirmation message to the user.

🧠 How It Works: Workflow Overview

  • Trigger: When User Completes Form
  • Search: Edit Url LinkedIn, Get LinkedIn Entry on Google, Extract Body and Title, Parse Google Results
  • Matching: Extract Parsed Results, Filter, Limit, IF LinkedIn Profile is Found?
  • Fallback: Form Not Found if no match
  • Company Lookup: Edit Company Search, Get Company on Google, Parse Results, Split Out
  • Content Generation: Merge, Create a Followup for Company and Person
  • Email Delivery: Send Email, Form Email Sent

📨 Final Output An HTML-styled email (using Tailwind CSS) with:

  • Matched LinkedIn profile
  • Company insights
  • Persona-based outreach strategy

🔐 Credentials Used

  • BrightData account for scraping Google search results
  • OpenAI account for GPT-4o-mini-powered parsing and content generation
  • SMTP account for sending follow-up emails

❓Questions? Template and node created by Miquel Colomer and n8nhackers.

Need help customizing or deploying? Contact us for consulting and support.

n8n Form to LinkedIn Profile Finder via Bright Data & GPT-4o Mini

This n8n workflow streamlines the process of finding LinkedIn profiles based on user-submitted information through a simple form. It leverages Bright Data for web scraping and GPT-4o Mini for intelligent parsing and extraction of the search results.

What it does

  1. Triggers on Form Submission: The workflow starts when a user submits data via an n8n form.
  2. Processes Form Data: The submitted data is captured and prepared for further processing.
  3. Initiates Bright Data Scrape (Missing in JSON): Based on the directory name, it's highly probable that a Bright Data node would be here to perform a LinkedIn search or scrape. However, this node is not present in the provided JSON.
  4. Parses HTML (Missing in JSON): Again, based on the directory name, it's likely an HTML node would be used to extract relevant information from the Bright Data scrape results. This node is present in the JSON but not connected.
  5. Applies OpenAI (GPT-4o Mini) for Extraction (Missing in JSON): The workflow would then use an OpenAI node (configured for GPT-4o Mini) to intelligently extract specific details (like LinkedIn profile URLs, names, titles, etc.) from the scraped HTML. This node is present in the JSON but not connected.
  6. Filters and Limits Results (Missing in JSON): The Filter and Limit nodes would likely refine the extracted data, ensuring only relevant and a manageable number of results are passed on. These nodes are present in the JSON but not connected.
  7. Merges Data (Missing in JSON): The Merge node would combine different data streams, potentially from multiple scrape attempts or additional data sources. This node is present in the JSON but not connected.
  8. Sends Email (Missing in JSON): Finally, the workflow would send an email containing the extracted LinkedIn profiles or a summary of the findings to a specified recipient. This node is present in the JSON but not connected.

Note: While the directory name suggests the use of Bright Data and GPT-4o Mini, and the JSON includes nodes for OpenAI, HTML, Filter, Limit, Merge, and Send Email, the provided JSON snippet does not contain any connections between these nodes. This means the workflow, as defined by the JSON, is incomplete and would not execute the described steps. The description above assumes the intended functionality based on the node types and the workflow's directory name.

Prerequisites/Requirements

  • n8n Instance: A running n8n instance.
  • n8n Form: An n8n Form Trigger configured with the necessary input fields (e.g., for person's name, company, job title).
  • OpenAI API Key: An OpenAI API key with access to GPT-4o Mini or a similar model (if the OpenAI node were connected and configured).
  • SMTP Credentials: SMTP server details for sending emails (if the Send Email node were connected and configured).
  • Bright Data Account: (Likely, based on directory name) A Bright Data account with access to web scraping capabilities.

Setup/Usage

  1. Import the Workflow: Import the provided JSON into your n8n instance.
  2. Configure the Form Trigger:
    • Open the "On form submission" node.
    • Define the form fields that users will fill out (e.g., firstName, lastName, company).
    • Activate the form.
  3. Configure Credentials (if connections were present):
    • OpenAI: Set up your OpenAI API key credential in n8n.
    • Email: Configure your SMTP credentials for the "Send Email" node.
    • (Bright Data): If a Bright Data node were added, configure its credentials.
  4. Connect the Nodes: As the provided JSON lacks connections, you would need to manually connect the nodes to achieve the intended functionality:
    • Connect the "On form submission" output to a node that initiates the Bright Data scrape (e.g., an HTTP Request node or a dedicated Bright Data node, which would need to be added).
    • Connect the output of the Bright Data scrape to the "HTML" node for parsing.
    • Connect the "HTML" node's output to the "OpenAI" node for data extraction.
    • Connect the "OpenAI" node's output to the "Filter" and "Limit" nodes for refinement.
    • Connect the processed data to the "Send Email" node to deliver the results.
  5. Activate the Workflow: Once configured and connected, activate the workflow to make it ready for use.
  6. Share the Form: Share the URL of your n8n form with users to collect their requests.

Related Templates

Automate Dutch Public Procurement Data Collection with TenderNed

TenderNed Public Procurement What This Workflow Does This workflow automates the collection of public procurement data from TenderNed (the official Dutch tender platform). It: Fetches the latest tender publications from the TenderNed API Retrieves detailed information in both XML and JSON formats for each tender Parses and extracts key information like organization names, titles, descriptions, and reference numbers Filters results based on your custom criteria Stores the data in a database for easy querying and analysis Setup Instructions This template comes with sticky notes providing step-by-step instructions in Dutch and various query options you can customize. Prerequisites TenderNed API Access - Register at TenderNed for API credentials Configuration Steps Set up TenderNed credentials: Add HTTP Basic Auth credentials with your TenderNed API username and password Apply these credentials to the three HTTP Request nodes: "Tenderned Publicaties" "Haal XML Details" "Haal JSON Details" Customize filters: Modify the "Filter op ..." node to match your specific requirements Examples: specific organizations, contract values, regions, etc. How It Works Step 1: Trigger The workflow can be triggered either manually for testing or automatically on a daily schedule. Step 2: Fetch Publications Makes an API call to TenderNed to retrieve a list of recent publications (up to 100 per request). Step 3: Process & Split Extracts the tender array from the response and splits it into individual items for processing. Step 4: Fetch Details For each tender, the workflow makes two parallel API calls: XML endpoint - Retrieves the complete tender documentation in XML format JSON endpoint - Fetches metadata including reference numbers and keywords Step 5: Parse & Merge Parses the XML data and merges it with the JSON metadata and batch information into a single data structure. Step 6: Extract Fields Maps the raw API data to clean, structured fields including: Publication ID and date Organization name Tender title and description Reference numbers (kenmerk, TED number) Step 7: Filter Applies your custom filter criteria to focus on relevant tenders only. Step 8: Store Inserts the processed data into your database for storage and future analysis. Customization Tips Modify API Parameters In the "Tenderned Publicaties" node, you can adjust: offset: Starting position for pagination size: Number of results per request (max 100) Add query parameters for date ranges, status filters, etc. Add More Fields Extend the "Splits Alle Velden" node to extract additional fields from the XML/JSON data, such as: Contract value estimates Deadline dates CPV codes (procurement classification) Contact information Integrate Notifications Add a Slack, Email, or Discord node after the filter to get notified about new matching tenders. Incremental Updates Modify the workflow to only fetch new tenders by: Storing the last execution timestamp Adding date filters to the API query Only processing publications newer than the last run Troubleshooting No data returned? Verify your TenderNed API credentials are correct Check that you have setup youre filter proper Need help setting this up or interested in a complete tender analysis solution? Get in touch 🔗 LinkedIn – Wessel Bulte

Wessel BulteBy Wessel Bulte
247

🎓 How to transform unstructured email data into structured format with AI agent

This workflow automates the process of extracting structured, usable information from unstructured email messages across multiple platforms. It connects directly to Gmail, Outlook, and IMAP accounts, retrieves incoming emails, and sends their content to an AI-powered parsing agent built on OpenAI GPT models. The AI agent analyzes each email, identifies relevant details, and returns a clean JSON structure containing key fields: From – sender’s email address To – recipient’s email address Subject – email subject line Summary – short AI-generated summary of the email body The extracted information is then automatically inserted into an n8n Data Table, creating a structured database of email metadata and summaries ready for indexing, reporting, or integration with other tools. --- Key Benefits ✅ Full Automation: Eliminates manual reading and data entry from incoming emails. ✅ Multi-Source Integration: Handles data from different email providers seamlessly. ✅ AI-Driven Accuracy: Uses advanced language models to interpret complex or unformatted content. ✅ Structured Storage: Creates a standardized, query-ready dataset from previously unstructured text. ✅ Time Efficiency: Processes emails in real time, improving productivity and response speed. *✅ Scalability: Easily extendable to handle additional sources or extract more data fields. --- How it works This workflow automates the transformation of unstructured email data into a structured, queryable format. It operates through a series of connected steps: Email Triggering: The workflow is initiated by one of three different email triggers (Gmail, Microsoft Outlook, or a generic IMAP account), which constantly monitor for new incoming emails. AI-Powered Parsing & Structuring: When a new email is detected, its raw, unstructured content is passed to a central "Parsing Agent." This agent uses a specified OpenAI language model to intelligently analyze the email text. Data Extraction & Standardization: Following a predefined system prompt, the AI agent extracts key information from the email, such as the sender, recipient, subject, and a generated summary. It then forces the output into a strict JSON structure using a "Structured Output Parser" node, ensuring data consistency. Data Storage: Finally, the clean, structured data (the from, to, subject, and summarize fields) is inserted as a new row into a specified n8n Data Table, creating a searchable and reportable database of email information. --- Set up steps To implement this workflow, follow these configuration steps: Prepare the Data Table: Create a new Data Table within n8n. Define the columns with the following names and string type: From, To, Subject, and Summary. Configure Email Credentials: Set up the credential connections for the email services you wish to use (Gmail OAuth2, Microsoft Outlook OAuth2, and/or IMAP). Ensure the accounts have the necessary permissions to read emails. Configure AI Model Credentials: Set up the OpenAI API credential with a valid API key. The workflow is configured to use the model, but this can be changed in the respective nodes if needed. Connect the Nodes: The workflow canvas is already correctly wired. Visually confirm that the email triggers are connected to the "Parsing Agent," which is connected to the "Insert row" (Data Table) node. Also, ensure the "OpenAI Chat Model" and "Structured Output Parser" are connected to the "Parsing Agent" as its AI model and output parser, respectively. Activate the Workflow: Save the workflow and toggle the "Active" switch to ON. The triggers will begin polling for new emails according to their schedule (e.g., every minute), and the automation will start processing incoming messages. --- Need help customizing? Contact me for consulting and support or add me on Linkedin.

DavideBy Davide
1616

Tax deadline management & compliance alerts with GPT-4, Google Sheets & Slack

AI-Driven Tax Compliance & Deadline Management System Description Automate tax deadline monitoring with AI-powered insights. This workflow checks your tax calendar daily at 8 AM, uses GPT-4 to analyze upcoming deadlines across multiple jurisdictions, detects overdue and critical items, and sends intelligent alerts via email and Slack only when immediate action is required. Perfect for finance teams and accounting firms who need proactive compliance management without manual tracking. 🏛️🤖📊 Good to Know AI-Powered: GPT-4 provides risk assessment and strategic recommendations Multi-Jurisdiction: Handles Federal, State, and Local tax requirements automatically Smart Alerts: Only notifies executives when deadlines are overdue or critical (≤3 days) Priority Classification: Categorizes deadlines as Overdue, Critical, High, or Medium priority Dual Notifications: Critical alerts to leadership + daily summaries to team channel Complete Audit Trail: Logs all checks and deadlines to Google Sheets for compliance records How It Works Daily Trigger - Runs at 8:00 AM every morning Fetch Data - Pulls tax calendar and company configuration from Google Sheets Analyze Deadlines - Calculates days remaining, filters by jurisdiction/entity type, categorizes by priority AI Analysis - GPT-4 provides strategic insights and risk assessment on upcoming deadlines Smart Routing - Only sends alerts if overdue or critical deadlines exist Critical Alerts - HTML email to executives + Slack alert for urgent items Team Updates - Slack summary to finance channel with all upcoming deadlines Logging - Records compliance check results to Google Sheets for audit trail Requirements Google Sheets Structure Sheet 1: TaxCalendar DeadlineID | DeadlineName | DeadlineDate | Jurisdiction | Category | AssignedTo | IsActive FED-Q1 | Form 1120 Q1 | 2025-04-15 | Federal | Income | John Doe | TRUE Sheet 2: CompanyConfig (single row) Jurisdictions | EntityType | FiscalYearEnd Federal, California | Corporation | 12-31 Sheet 3: ComplianceLog (auto-populated) Date | AlertLevel | TotalUpcoming | CriticalCount | OverdueCount 2025-01-15 | HIGH | 12 | 3 | 1 Credentials Needed Google Sheets - Service Account OAuth2 OpenAI - API Key (GPT-4 access required) SMTP - Email account for sending alerts Slack - Bot Token with chat:write permission Setup Steps Import workflow JSON into n8n Add all 4 credentials Replace these placeholders: YOURTAXCALENDAR_ID - Tax calendar sheet ID YOURCONFIGID - Company config sheet ID YOURLOGID - Compliance log sheet ID C12345678 - Slack channel ID tax@company.com - Sender email cfo@company.com - Recipient email Share all sheets with Google service account email Invite Slack bot to channels Test workflow manually Activate the trigger Customizing This Workflow Change Alert Thresholds: Edit "Analyze Deadlines" node: Critical: Change <= 3 to <= 5 for 5-day warning High: Change <= 7 to <= 14 for 2-week notice Medium: Change <= 30 to <= 60 for 2-month lookout Adjust Schedule: Edit "Daily Tax Check" trigger: Change hour/minute for different run time Add multiple trigger times for tax season (8 AM, 2 PM, 6 PM) Add More Recipients: Edit "Send Email" node: To: cfo@company.com, director@company.com CC: accounting@company.com BCC: archive@company.com Customize Email Design: Edit "Format Email" node to change colors, add logo, or modify layout Add SMS Alerts: Insert Twilio node after "Is Critical" for emergency notifications Integrate Task Management: Add HTTP Request node to create tasks in Asana/Jira for critical deadlines Troubleshooting | Issue | Solution | |-------|----------| | No deadlines found | Check date format (YYYY-MM-DD) and IsActive = TRUE | | AI analysis failed | Verify OpenAI API key and account credits | | Email not sending | Test SMTP credentials and check if critical condition met | | Slack not posting | Invite bot to channel and verify channel ID format | | Permission denied | Share Google Sheets with service account email | 📞 Professional Services Need help with implementation or customization? Our team offers: 🎯 Custom workflow development 🏢 Enterprise deployment support 🎓 Team training sessions 🔧 Ongoing maintenance 📊 Custom reporting & dashboards 🔗 Additional API integrations Discover more workflows – Get in touch with us

Oneclick AI SquadBy Oneclick AI Squad
93