Linkedin Chrome Extensions
Configured with Google Sheets, HTTP Request, Limit, Loop Over Items. Review the connections and setup before adapting this template.
Node categories in this workflow
- Trigger
- Routing
- Transform
- Code
- Data store
- Web / API
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 |
|---|---|---|---|
| When clicking ‘Test workflow’ | Trigger | Manual Trigger | See node parameters |
| Loop Over Items | Routing | Loop Over Items | See node parameters |
| Limit | Transform | Limit | See node parameters |
| Set extension IDs var | Code | Code | See node parameters |
| Load already processed items | Data store | Google Sheets | See node parameters |
| Exclude processed items | Transform | Merge | See node parameters |
| SERP Request | Web / API | HTTP Request | See node parameters |
| Upsert to Google Sheets | Data store | Google Sheets | appendOrUpdate |
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
googleSheetsOAuth2ApihttpHeaderAuth
Workflow notes
Limit
Only process 200 items per run
Resolve Chrome Extensions which are tracked by Linkedin
Resolve Chrome Extensions which are tracked by Linkedin
Linkedin tracks which Chrome extensions are installed in your browser. This workflow uses a huge JSON of chrome extension ids, extracted from Linkedin pages, and builds a pretty Google Sheet with the list of these extensions - with extension names. This workflow web scrapes Google to search for chrome extension id - and extracts the first search result.
-
Clone this Google Sheet template: https://docs.google.com/spreadsheets/d/REPLACE_WITH_DOCUMENT_ID/edit?gid=0#gid=0
-
Get API key for Google SERP API access here: https://rapidapi.com/restyler/api/serp-api1
-
Create n8n header auth for Google SERP API
Some context: https://www.linkedin.com/feed/update/urn:li:activity:7244984812497702912/
Follow the author: https://www.linkedin.com/in/anthony-sidashin/
Linkedin Chrome Extensions
Linkedin Chrome Extensions
Purpose and structure
This folder contains the Linkedin Chrome Extensions workflow. Its executable nodes use code, googleSheets, httpRequest, limit, manualTrigger, merge, splitInBatches. 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
When clicking ‘Test workflow’
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/Limit/1483_Limit_Code_Automation_Webhook.json MIT; preserve source notices.