Greenhouse jobs to Slack with n8n
Each new role on a company's Greenhouse job board arrives in Slack as one line with the title, company, location and the apply link. Roles already posted are skipped, so the channel only shows openings that are new since the last run.
Put the company's Greenhouse board name in companies in the request body; it is the part after boards.greenhouse.io in the board's address. Each run reads up to 50 roles. Filters for workplace type, employment type and salary sit in the same body.
Built-in nodes only Imports on n8n Cloud and self-hosted n8n 1.80 or later, no community nodes. 11 of 11 checks pass; validated, not executed.
- Source
- Greenhouse job boards
- Destination
- Slack
- Store price
- $0.99 per 1,000 results (pay per event)
- Cost on the Free plan
- about $0.45 a run (start $0.40 + up to 50 results), about $13.48 a month daily, plus platform usage
- Data checked
- 2026-11-12
Method
-
Get an Apify token
Sign in to Apify and copy a personal API token from Console: Settings, API and integrations. The workflow keeps it in an n8n credential, never in the file.
-
Import the workflow
In n8n choose Workflows, Import from file, or paste the JSON onto an empty canvas.
- Run by hand
- Every day
- Run Apify Actor
- Only records not sent before
- Send to Slack
n8n workflowgreenhouse-jobs-to-slack.n8n.json
Show the file (172 lines)
{ "name": "Greenhouse jobs to Slack", "nodes": [ { "id": "506416c6-1fb9-4b7f-ae44-a47aaa72e4d3", "name": "Run by hand", "type": "n8n-nodes-base.manualTrigger", "typeVersion": 1, "position": [ 0, 0 ], "parameters": {} }, { "id": "d8534386-617b-4085-ada6-d3dc83957623", "name": "Every day", "type": "n8n-nodes-base.scheduleTrigger", "typeVersion": 1.2, "position": [ 0, 200 ], "parameters": { "rule": { "interval": [ { "triggerAtHour": 8 } ] } }, "notes": "Activate the workflow to run on this schedule." }, { "id": "eaa20912-12dd-474a-a07f-a2b349247f87", "name": "Run Apify Actor", "type": "n8n-nodes-base.httpRequest", "typeVersion": 4.2, "position": [ 260, 100 ], "parameters": { "method": "POST", "url": "https://api.apify.com/v2/actors/dataspryva~greenhouse-ats-job-board-lookup-by-company/run-sync-get-dataset-items", "authentication": "genericCredentialType", "genericAuthType": "httpHeaderAuth", "sendBody": true, "specifyBody": "json", "jsonBody": "{\n \"mode\": \"companyJobs\",\n \"companies\": [\n \"airbnb\"\n ],\n \"workplaceType\": \"any\",\n \"employmentType\": \"any\",\n \"onlyWithSalary\": false,\n \"salaryCurrency\": \"any\",\n \"sortBy\": \"board\",\n \"content\": false,\n \"descriptionFormat\": \"html\",\n \"includeQuestions\": false,\n \"maxItems\": 50,\n \"maxJobsPerCompany\": 50,\n \"verifyCompanies\": true\n}", "options": { "timeout": 310000 } }, "notes": "Actor: dataspryva/greenhouse-ats-job-board-lookup-by-company. Select a Header Auth credential: name Authorization, value Bearer + your Apify token. Edit the JSON body to change the input.", "notesInFlow": false }, { "id": "49662896-8031-470b-ac31-08d24401549b", "name": "Only records not sent before", "type": "n8n-nodes-base.removeDuplicates", "typeVersion": 2, "position": [ 500, 100 ], "parameters": { "operation": "removeItemsSeenInPreviousExecutions", "logic": "removeItemsWithAlreadySeenKeyValues", "dedupeValue": "={{ $json.applyUrl }}", "options": { "scope": "node", "historySize": 10000 } }, "notes": "Remembers each applyUrl it has passed on (up to 10,000) across runs, so a record is sent once. Needs n8n 1.64 or later." }, { "id": "05d5f9fe-4283-4671-a02e-07f8b7d9eceb", "name": "Send to Slack", "type": "n8n-nodes-base.slack", "typeVersion": 2.3, "position": [ 740, 100 ], "parameters": { "select": "channel", "channelId": { "__rl": true, "value": "", "mode": "list" }, "text": "={{ [$json.title, $json.companyName, $json.location, $json.applyUrl].filter(v => v !== undefined && v !== null && v !== '').join(' | ') }}", "otherOptions": {} }, "notes": "Pick your Slack credential and channel." }, { "id": "3060fec6-3a78-46f9-ae47-906cd336193b", "name": "Setup", "type": "n8n-nodes-base.stickyNote", "typeVersion": 1, "position": [ 0, -370 ], "parameters": { "content": "## Greenhouse ATS Job Board Lookup by Company\n\nSource: [dataspryva/greenhouse-ats-job-board-lookup-by-company](https://apify.com/dataspryva/greenhouse-ats-job-board-lookup-by-company) on Apify.\n\n1. In **Run Apify Actor**, create a Header Auth credential: name `Authorization`, value `Bearer YOUR_APIFY_TOKEN` with your token.\n2. Open **Send to Slack** and connect your Slack account.\n3. Edit the JSON body of **Run Apify Actor** to change the input.\n\nGenerated by recipeforagents.com. Validated, not executed: runs are billed to your Apify account.", "height": 340, "width": 460, "color": 6 } } ], "connections": { "Run by hand": { "main": [ [ { "node": "Run Apify Actor", "type": "main", "index": 0 } ] ] }, "Every day": { "main": [ [ { "node": "Run Apify Actor", "type": "main", "index": 0 } ] ] }, "Run Apify Actor": { "main": [ [ { "node": "Only records not sent before", "type": "main", "index": 0 } ] ] }, "Only records not sent before": { "main": [ [ { "node": "Send to Slack", "type": "main", "index": 0 } ] ] } }, "pinData": {}, "active": false, "settings": { "executionOrder": "v1" }, "meta": { "templateCredsSetupCompleted": false }, "tags": [] }Validated, not executed: 11 of 11 checks pass
- It has a nodes array and a connections object
- Every node has a name, type, typeVersion, position and parameters
- Node names are unique
- Every node type is a known n8n core node (or the Apify node)
- Every node uses a typeVersion that n8n ships
- Every connection points at an existing node
- At least one trigger starts the workflow
- Every working node is reachable from a trigger
- Apify calls use POST and a credential for the token
- Actor input matches the Actor's published input schema
- No token or credential value is embedded
-
Add the Apify credential
Open Run Apify Actor. Under Credential, create a Header Auth credential with the name
Authorizationand the valueBearer, a space and your token. -
Set the input
The request body holds the Actor input: the Actor's Store prefill with maxItems, maxJobsPerCompany set for this recipe. Change maxItems and maxJobsPerCompany to your own.
{ "mode": "companyJobs", "companies": [ "airbnb" ], "workplaceType": "any", "employmentType": "any", "onlyWithSalary": false, "salaryCurrency": "any", "sortBy": "board", "content": false, "descriptionFormat": "html", "includeQuestions": false, "maxItems": 50, "maxJobsPerCompany": 50, "verifyCompanies": true }Every input field is documented on the Greenhouse ATS Job Board Lookup by Company page.
-
Only new records go through
The Only records not sent before node (n8n's Remove Duplicates, set to remove items processed in previous executions) remembers each
applyUrlit has passed on, so a record reaches Slack once even when the next run returns it again. It needs n8n 1.64 or later; clear its history from the node to resend everything. -
Connect Slack
Open Send to Slack, select your Slack credential and pick the channel. Each message shows title, companyName, location, applyUrl.
-
Run once, then turn it on
Click Execute workflow and check the first records in Slack. When they look right, activate the workflow so the daily trigger runs it at 08:00 in your instance's timezone.
Where it breaks
- Only companies that host their jobs on Greenhouse are covered; other applicant tracking systems need a different source.
- Salary appears only when the company publishes it on the board.
- The first run posts every open role up to the limit; after that only new roles arrive. Lower maxItems or filter by department if that first burst is too long.
- The workflow uses Apify's synchronous endpoint, which waits up to 300 seconds. Bigger runs answer HTTP 408: lower the limit or switch to an asynchronous run.
- Each run is billed to your Apify account at the Store price ($0.99 per 1,000 results (pay per event)).
Bigger runs: the long-run workflow starts the run, waits for it and reads the dataset, so it never hits the 300-second limit.
If the workflow fails
Why does the workflow or script stop with HTTP 408?
The synchronous endpoint waits at most 300 seconds. After that it answers 408 while the run keeps going in Apify. Lower the result limit, or start the run asynchronously, wait for it to finish and then read its dataset.
Source: Apify API: run Actor synchronously and get dataset items
What do 400, 401, 402 and 403 from the Apify API mean?
Read error.type in the response body. 400 is invalid Actor input. 401 (user-or-token-not-found) means a token reached Apify but it is wrong or revoked. 402 with x402-payment-required means no token reached Apify at all: the n8n credential or the Authorization: Bearer header is missing, and Apify is offering its pay-per-run x402 route for agents instead; any other 402 is an exhausted usage limit on the account that pays for the run. 403 is a token without permission for that Actor or storage.
Source: Apify API: authentication; Apify documentation: agentic payments with x402; Apify API: run Actor synchronously and get dataset items
n8n says Install this node to use it after import. Why?
The workflow names a node or node version your instance does not have, usually a community node. The workflows here use only built-in nodes at versions n8n has shipped since 1.80, so they import on n8n Cloud and older self-hosted instances without community nodes.
Why does the HTTP Request node time out before Apify answers?
Set the node's Timeout option to at least 300000 ms so n8n waits as long as Apify's synchronous endpoint. The workflows here already set 310000. A failure at exactly 30 seconds points to a proxy in front of n8n.
Same data in an agent
Want Claude, Cursor or ChatGPT to call the Actor directly instead of on a schedule? The Greenhouse ATS Job Board Lookup by Company page has MCP configs for eight clients and a SKILL.md. The Greenhouse job boards MCP server bundles every Greenhouse job boards Actor in one URL.
Questions
How do I find a company's Greenhouse board name?
Open any job at the company and look at the address: the word after boards.greenhouse.io is the board name to put in companies.
Will a role be posted every day?
No. The workflow remembers each apply link it has posted and skips it on later runs, so a role appears once.
More recipes
Website to markdown to Notion
Crawl a documentation site into markdown on a schedule and file each page in Notion, again whenever a page's…
Any public websiteNotionGoogle Trends to Google Sheets
Save Google Trends interest over time and related queries for your terms in a Google Sheet to spot rising…
Google TrendsGoogle SheetsBluesky posts to Slack
Forward new Bluesky posts from a profile or search to Slack for brand and topic monitoring.
BlueskySlackEventbrite events to Google Sheets
List upcoming Eventbrite events for a city or category in a Google Sheet with date, venue, coordinates and…
EventbriteGoogle SheetsGoogle Scholar papers to Notion
File Google Scholar search results in a Notion database with authors, year, citations and link, as a reading…
Google ScholarNotionCrunchbase funding news to Slack
Post new Crunchbase News funding stories to Slack as a daily deal-flow feed.
Crunchbase NewsSlack