Fetch daily job postings from JSearch to Google Sheets and Telegram
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 14 nodes and runs on a schedule (every day at 22:00). Along the way it connects Google Sheets and Telegram.
How it runs
Trigger: On a schedule (every day at 22:00).
- Load Existing Job IDs (Google Sheets): uses Google Sheets
- Set Search Parameters (Edit Fields (Set)): sets or maps fields
- Combine API Results with Existing IDs (Merge): merges the data from its input branches
- Build Search Query (Code): runs custom JavaScript code
- Filter Out Existing Jobs (Code): runs custom JavaScript code
- Fetch Jobs from JSearch API (HTTP Request): calls an HTTP API
- Count New Jobs (Code): runs custom JavaScript code
- Loop Over New Jobs (Loop Over Items (Split in Batches)): loops over the items in batches
- Split API Results (Split Out): splits a list into separate items
- Combine Count and Save Results (Merge): merges the data from its input branches
…plus 3 more steps. See the full node list below.
Services it uses
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (10)
- Schedule Trigger
n8n-nodes-base.scheduleTrigger - HTTP Request
n8n-nodes-base.httpRequest - Split Out
n8n-nodes-base.splitOut - Google Sheets
n8n-nodes-base.googleSheets - Merge
n8n-nodes-base.merge - Code
n8n-nodes-base.code - Loop Over Items (Split in Batches)
n8n-nodes-base.splitInBatches - Wait
n8n-nodes-base.wait - Telegram
n8n-nodes-base.telegram - Edit Fields (Set)
n8n-nodes-base.set
From the author
This workflow automatically fetches job postings from the JSearch API once per day, filters out duplicates, and saves only new jobs to a Google Sheet. It also sends a Telegram summary with the number of newly added jobs. What this workflow does • Builds a…