Daily Job Matches to Slack: Ashby, Greenhouse & Lever (n8n)
Daily Job Matches to Slack: Ashby, Greenhouse & Lever (n8n)
Regular price
£4.99
Regular price
£4.99
Sale price
Unit price
/
per
⬇
Instant Digital Download
∞
Unlimited Downloads
★
Lifetime Access in Your Account
Couldn't load pickup availability
🔥
128+ Sold
Popular with n8n builders
âš¡
23 people viewing
High interest right now
✅
9 added today
Fast-moving digital product
Daily Job Matches to Slack: Ashby, Greenhouse & Lever (n8n)
Regular price
£4.99
Regular price
£4.99
Sale price
Unit price
/
per
Get daily Slack job alerts matched to Ashby, Greenhouse, and Lever
This n8n workflow automatically checks Ashby, Greenhouse, and Lever job boards every morning, finds postings that match your title and location filters, deduplicates repeats, and posts a single summary of new matches to your chosen Slack channel.
What this workflow does
- Runs daily at 8:00 AM (or you can trigger it manually to test).
- Builds one public API request per board (Ashby, Greenhouse, and Lever) using the configured company slug list.
- Fetches job postings via HTTP, and skips boards that fail to respond.
- Normalizes different API formats into a single list of roles, then applies your title include/exclude and location include/exclude rules.
- Deduplicates across runs using a persistent deduplication key so you only get truly new roles.
- Posts one consolidated message containing the remaining new matches to Slack.
Use cases
- SaaS operators who want a daily feed of relevant engineering and hiring roles without checking each board manually.
- Automation engineers using n8n to standardize multi-source job discovery and deliver results to Slack.
- Job seekers tracking roles across Ashby, Greenhouse, and Lever with consistent keyword matching.
Technical details
- n8n nodes used: set, code, slack, sticky note, HTTP Request, and Manual Trigger.
- Configuration: update the board list and keyword filters (title/location include/exclude) in the configuration node.
- Setup: add a Slack credential, choose the destination channel, run once manually to seed deduplication, then enable the schedule.
Note: The workflow is designed to use public access for Ashby/Greenhouse/Lever boards (no API keys required as stated).
