Block 1 - ⏰ Schedule: Trigger Every Day
- Type / Role
- n8n-nodes-base.scheduleTrigger - scheduleTrigger
- Config choices
- Version 1.1
This workflow is provided as-is. Please review and test before using in production.
How it works This workflow automates the job curation process by retrieving pending job search inputs from a spreadsheet, querying the JSearch API for relevant job listings, and writing the curated...
n8n-nodes-base.scheduletrigger, n8n-nodes-base.googlesheets, n8n-nodes-base.httprequest, n8n-nodes-base.code, n8n-nodes-base.filter, n8n-nodes-base.stickynote
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Avkash Kakdiya.
Original n8n.io sourceThis workflow automates the job curation process by retrieving pending job search inputs from a spreadsheet, querying the JSearch API for relevant job listings, and writing the curated results back to another sheet. It is designed to streamline job discovery and reduce manual data entry.
1. Trigger & Input
The workflow starts on a defined schedule (e.g., once per day).
It reads a row from the Job Scraper sheet where the status is marked as "Pending".
The selected row includes fields like Position and Location, which are used to build the search query.
2. Job Search & Processing
Sends a search request to the JSearch API using the Position and Location from the spreadsheet.
Parses the API response and extracts individual job listings.
Filters out empty, irrelevant, or invalid entries to ensure clean and relevant job data.
3. Output & Status Update
Writes valid job listings to the Job Listing output sheet with fields such as job title, company name, location, and more.
Updates the original row in the source sheet to mark it as Scraped, ensuring it will not be processed again in future runs.
Reduces manual effort in job research and listing.
Ensures only valid, structured data is stored and used.
Prevents duplicate processing with automatic status updates.
Simple to expand by adding more job sources or filters.
This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.
| Workflow | Automate job search & curation with JSearch API & Google Sheets |
|---|---|
| Complexity | intermediate |
| Nodes | 10 |
| Categories | HR |
| Author | Avkash Kakdiya |
| Published | 06 Aug 2025 |
Use the JSON export at /data/workflows/7040/7040.json as the source template for this automation.
Open n8n, import the downloaded JSON, and review each node before activating the workflow.
Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.
Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.
Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.
How it works This workflow automates the job curation process by retrieving pending job search inputs from a spreadsheet, querying the JSearch API for relevant job listings, and writing the curated...
Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.
Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your HR use case.