Simple LinkedIn profile collector
Configured with Convert To File, HTTP Request, Noco Db, Open Ai, and additional nodes. Review the connections and setup before adapting this template.
Node categories in this workflow
- Trigger
- Web / API
- Transform
- AI & models
- Data store
Icons describe general node roles, inferred from node types. Inspect the parameters for the configured action.
Drag to pan; use + and − to zoom. Reconstructed from the exported node positions; nothing runs here. Dashed lines represent non-main connections. Full node names and notes appear below.
How it works
The exported workflow contains the following configured nodes. Their connections are shown above; inspect the JSON for the complete logic, expressions, and external actions.
| Node | Category | Type | Operation |
|---|---|---|---|
| Manual Trigger | Trigger | Manual Trigger | See node parameters |
| Google search w/ SerpAPI | Web / API | HTTP Request | See node parameters |
| Edit Fields | Transform | Edit Fields | See node parameters |
| Discard meta data | Transform | Edit Fields | See node parameters |
| LinkedIn profiles in Excel for download | Transform | Convert To File | xlsx |
| Search parameter | Transform | Edit Fields | See node parameters |
| Turn search results into individual items | Transform | Split Out | See node parameters |
| Company name & followers | AI & models | Open Ai | See node parameters |
| Generate final data via merge | Transform | Merge | See node parameters |
| Store data in a NocoDB table | Data store | Noco Db | create |
Setup
- Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
- Connect your own credentials through n8n’s credential store. Replace
REPLACE_WITH_*values with your resource identifiers. - Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
- Run with synthetic data and harmless destinations. Enable triggers only after checking the actual outputs.
Requirements
An n8n instance with the listed node types and compatible versions. Service-connected workflows may require accounts, credentials, or paid APIs.
Credential types declared in the source
nocoDbApiTokenopenAiApiserpApi
Workflow notes
Adaptation required
Adaptation required
Get a free tier for serpAPI (Google Search) at serpapi.com
Set up the credentials for serpAPI
Explanations in the n8n docs
NO adaptation required
NO adaptation required
The search metadata is being discarded and only the "organic results" being preserved as individual list items as they are containing the relevant data
NO adaptation required
NO adaptation required
Discard irrelevant search result (meta)data
Adaptation required
Adaptation required
This node does the following:
- Identify where possible the company name the LinkedIn profile is working in.
- Turn the number of followers into a real number, e.g. "3.3k+" → 3300
Set up
- Get API credentials from openai.com
- Set up credentials in n8n
- Select the OpenAI model you want to use, e.g. GPT-4o
- The prompt is already included but can be improved
n8n documentation for more explanations
What problem does this solve?
What problem does this solve?
It fetches LinkedIn profiles based on a keyword and location via Google search and stores them in an Excel file for download and in a NocoDB database. It tries to avoid using costly services and should be n8n beginner friendly. It uses the SerpAPI.com to avoid being blocked by Google Search and to process the data in an easier way.
NO adaption required
NO adaption required
This node discards irrelevant OpenAI metadata
Setting the parameters for Google search via SerpAPI
Setting the parameters for Google search via SerpAPI
Searching LinkedIn profiles by setting the following parameters for the Google query in the next node
- Keyword on what to look for
- Location or region to look into
- Number of search results
- Host language
- Geolocation
- Search engine
More on search parameters: https://serpapi.com/blog/google-search-parameters/ or in the n8n docs
What does it do?
What does it do?
- Based on criteria input, it searches LinkedIn profiles
- It discards unnecessary data and turns the follower count into a real number
- The output is provided as an Excel table for download and in a NocoDB database
Step-by-step instruction
Step-by-step instruction
-
Import the Workflow: Copy the workflow JSON from the "Template Code" section below. Import it into n8n via "Import from File" or "Import from URL".
-
Set up a free account at serpapi.com and get API credentials to enable good Google search results
-
Set up an API account at openai.com and get API key
-
Set up a nocodb.com account (or self-host) and get the API credentials
-
Create the credentials for serpapi.com, opemnai.com and nocodb.com in n8n.
-
Set up a table in NocoDB with the fields indicated in the note above the NocoDB node
-
Follow the instructions as detailed in the notes above individual nodes
-
When the workflow is finished, open the Excel node and click download if you need the Excel file
NO adaption required
NO adaption required
This node creates the final data output
NO adaption required
NO adaption required
This node creates stores all the data in an Excel file which can be downloaded.
- Open the node
- Click on download button
Adaption required
Adaption required
- This node creates stores all the data in an NocoDB database for further utilization.
- In case the database is not needed, just delete this node.
Set up part 1
- Create an NocoDB account, either via nocodb.com or self-hosted
- Create the credentials in n8n along the n8n documentation
- Set up a table with a name of your choice
Set up part 2
Create the following fields in this table:
- NameInLinkedinProfile (type: Single line text): name of the person
- NameOfCompany: the name of the company as generated by OpenAI
- linkedinUrl (type: url): the link to the LinkedIn profile
- Followers: the number of followers as text and indicated by LinkedIn
- followers_number (type: Number): the number of followers as a number
- Keyword: the keyword used for searching LinkedIn profiles
- Location: the location used for searching LinkedIn profiles
- Rich snippet (type: Long text):
- snippet_highlighted_words (type: Long text):
Adaptations in the node itself
- Make sure that the right table is selected
- Select "row" in the "Resources" field
- Select "create" in the field "Operation"
- Select "Auto map ...." in the field "Data to Send"
How does it do it?
How does it do it?
- Based on criteria input, it uses serpAPI.com to conduct Google search of the respective LinkedI profiles
- With OpenAI.com the name of the respective company is being added
- With OpenAI.com the follower number e.g., 300+ is turned into a real number: 300
- All unnecessary metadata is being discarded
- As an output an Excel file is being created
- The output is stored in a nocodb.com table
Simple LinkedIn profile collector
Simple LinkedIn profile collector
Purpose and structure
This folder contains the Simple LinkedIn profile collector workflow. Its executable nodes use convertToFile, httpRequest, manualTrigger, merge, nocoDb, openAi, set, splitOut. The table and connection map below are derived from the JSON, not an inferred guarantee of behavior.
Setup
Import inactive. Configure your own credentials and replace REPLACE_WITH_* values. Review external destinations and Code nodes before running.
Entry points
Manual Trigger
Verification
Sanitized source candidate; not runtime-tested. This overview is generated from node metadata. Read the folder README for the connection map, credential types, and license.
Attribution
https://github.com/Zie619/n8n-workflows/blob/94007c1445d9258a7da116646b79473e7c7c3282/workflows/Splitout/1742_Splitout_Nocodb_Automation_Webhook.json MIT; preserve source notices.