n8n Workflow Templates

What the workflow does

1. 1

   Start by hand

   You run the workflow when the sheet has new companies. Nothing runs on a schedule.

2. 2

   Your settings

   One Set node holds the Google Sheet, the tab name, how many companies to enrich per run and a spend limit per run.

3. 3

   Find rows to enrich

   Google Sheets reads the rows. Rows with a LinkedIn company URL in the url column and an empty name column are kept, so companies already filled in are skipped.

4. 4

   Scrape the company pages

   The Apify node runs LinkedIn Company Scraper on your Apify account for those URLs. No LinkedIn account or cookies are involved.

5. 5

   Write back to the sheet

   Name, website, industry, company size, employee count, follower count, headquarters and description are written to each company’s own row, matched on its URL.

Import it

Paste this URL into n8n’s Import from URL, or download the workflow JSON.

https://www.logicalscrapers.com/n8n/enrich-companies-with-linkedin-data.json

Set it up

1. Install the Apify community node, @apify/n8n-nodes-apify, in n8n and connect your Apify account in the Apify node.
2. Connect your Google account in both Google Sheets nodes.
3. Create a sheet with this header row: url, name, website, industry, companySize, numberOfEmployees, followersCount, headquarters, description.
4. Put LinkedIn company page URLs in the url column, for example https://www.linkedin.com/company/microsoft/.
5. Open the "Set sheet and limits" node and enter the sheet URL.

Scraper inputs the workflow sets

The workflow runs Scrape LinkedIn Company Details with these parameters. The scraper’s page documents every field it returns; its price is on the Apify listing.

Limitations

• The url column must hold LinkedIn company page URLs (linkedin.com/company/…). Rows with anything else are skipped.
• A row counts as enriched once its name column is filled in. A company page the scraper cannot read stays empty and is tried again on the next run.
• Each run enriches at most the number of companies in the settings node, 25 by default. Every company is one billed result.
• The spend limit per run is applied by version 0.7.0 and later of the Apify node. On earlier versions the companies-per-run setting is what bounds a run.

What the workflow does

1. 1

   Schedule

   A Schedule Trigger starts the workflow every morning at 08:00.

2. 2

   Your settings

   One Set node holds the keywords or hashtags, the search tab to read, how many days back to keep posts from, the posts to keep per keyword, a spend limit per run and the Google Sheet to write to.

3. 3

   Search Threads

   The Apify node runs Threads Search Scraper on your Apify account. It reads the Top, Recent and Tags tabs of public Threads search and keeps the posts published inside your date window. No Threads account or cookies are involved.

4. 4

   Write to the sheet

   The query, author, text, like, reply and repost counts, media type, date and URL of each post are appended to the sheet. A post already in the sheet is updated instead, matched on its URL, so daily runs do not duplicate rows.

Import it

Paste this URL into n8n’s Import from URL, or download the workflow JSON.

https://www.logicalscrapers.com/n8n/monitor-threads-keyword-mentions.json

Set it up

1. Install the Apify community node, @apify/n8n-nodes-apify, in n8n and connect your Apify account in the Apify node.
2. Connect your Google account in the Google Sheets node.
3. Create a sheet with this header row: searchQuery, username, text, likeCount, replyCount, repostCount, mediaType, createdAt, url.
4. Open the "Set search and sheet" node and enter your keywords and the sheet URL.

Scraper inputs the workflow sets

The workflow runs Threads Search Scraper with these parameters. The scraper’s page documents every field it returns; its price is on the Apify listing.

Limitations

• Threads shows a logged-out visitor one page per search tab, roughly 15 to 35 posts, and no further pages. Reading all three tabs is the most a keyword can return in one run.
• Threads search mixes old and new posts. The workflow keeps posts from the last 7 days by default, so a quiet keyword can add no rows on a given day.
• The spend limit per run is applied by version 0.7.0 and later of the Apify node. On earlier versions the posts-per-keyword setting is what bounds a run.
• The Google Sheets step matches on the column named `url`; renaming that column in the sheet makes every run append duplicates.

What the workflow does

1. 1

   Schedule

   A Schedule Trigger starts the workflow every morning at 08:00.

2. 2

   Your settings

   One Set node holds the job title or keywords, the location, the postings to fetch per run, a spend limit per run and the Google Sheet to write to.

3. 3

   Search LinkedIn jobs

   The Apify node runs LinkedIn Jobs Scraper on your Apify account, which reads public LinkedIn job search results. No LinkedIn account or cookies are involved.

4. 4

   Write to the sheet

   The job ID, title, company, location, employment type, seniority, industry, posting and expiry dates and the job URL are appended to the sheet. A posting already in the sheet is updated instead, matched on its LinkedIn job ID.

Import it

Paste this URL into n8n’s Import from URL, or download the workflow JSON.

https://www.logicalscrapers.com/n8n/save-linkedin-job-postings.json

Set it up

1. Install the Apify community node, @apify/n8n-nodes-apify, in n8n and connect your Apify account in the Apify node.
2. Connect your Google account in the Google Sheets node.
3. Create a sheet with this header row: linkedinJobId, title, company, location, employmentType, seniorityLevel, industry, postedAt, validThrough, jobUrl.
4. Open the "Set search and sheet" node and enter your keywords, location and the sheet URL.

Scraper inputs the workflow sets

The workflow runs LinkedIn Jobs Scraper with these parameters. The scraper’s page documents every field it returns; its price is on the Apify listing.

Limitations

• Searches by keyword and location, the same as the LinkedIn jobs search bar. One workflow covers one search; duplicate it for a second role or location.
• Each run fetches the first postings LinkedIn returns for the search, 25 by default. It does not keep a position between runs or page back through older postings.
• The workflow writes the ten columns listed in the setup. Salary is not among them.
• The spend limit per run is applied by version 0.7.0 and later of the Apify node. On earlier versions the postings-per-run setting is what bounds a run.