Indeed jobs to Notion with n8n

Method

1. 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.

2. 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
   • Keep main fields
   • Send to Notion

   n8n workflowindeed-jobs-to-notion.n8n.json

   Copy Download Actor on Apify

   Show the file (207 lines)

   {
     "name": "Indeed jobs to Notion",
     "nodes": [
       {
         "id": "706e36f6-65bc-4837-a0b5-61fae3a875fb",
         "name": "Run by hand",
         "type": "n8n-nodes-base.manualTrigger",
         "typeVersion": 1,
         "position": [
           0,
           0
         ],
         "parameters": {}
       },
       {
         "id": "014de7b6-ecda-432d-af66-3ec8eca08eb3",
         "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": "56eb49aa-7f64-439a-a40a-295be803c463",
         "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/vexaloom-labs~indeed-job-search-scraper-with-salary-and-benefits/run-sync-get-dataset-items",
           "authentication": "genericCredentialType",
           "genericAuthType": "httpHeaderAuth",
           "sendBody": true,
           "specifyBody": "json",
           "jsonBody": "{\n  \"searchQueries\": [\n    \"web developer in San Francisco\"\n  ],\n  \"country\": \"US\",\n  \"location\": \"San Francisco\",\n  \"radius\": 25,\n  \"easyApplyOnly\": false,\n  \"maxItems\": 3,\n  \"includeDescriptionHtml\": false,\n  \"includeCompanyRatings\": false,\n  \"includeContacts\": false,\n  \"includeCompanyReviews\": false,\n  \"includeCompanySalaries\": false,\n  \"expandBeyondCeiling\": false\n}",
           "options": {
             "timeout": 310000
           }
         },
         "notes": "Actor: vexaloom-labs/indeed-job-search-scraper-with-salary-and-benefits. Select a Header Auth credential: name Authorization, value Bearer + your Apify token. Edit the JSON body to change the input.",
         "notesInFlow": false
       },
       {
         "id": "8c45f896-fe4c-49cb-a5a0-54023951fca3",
         "name": "Only records not sent before",
         "type": "n8n-nodes-base.removeDuplicates",
         "typeVersion": 2,
         "position": [
           500,
           100
         ],
         "parameters": {
           "operation": "removeItemsSeenInPreviousExecutions",
           "logic": "removeItemsWithAlreadySeenKeyValues",
           "dedupeValue": "={{ $json.jobUrl }}",
           "options": {
             "scope": "node",
             "historySize": 10000
           }
         },
         "notes": "Remembers each jobUrl it has passed on (up to 10,000) across runs, so a record is sent once. Needs n8n 1.64 or later."
       },
       {
         "id": "8facf62e-b319-4e31-a00d-7df45ee5c9a3",
         "name": "Keep main fields",
         "type": "n8n-nodes-base.code",
         "typeVersion": 2,
         "position": [
           740,
           100
         ],
         "parameters": {
           "jsCode": "// Keeps the Actor's main fields as flat, spreadsheet-safe values.\nconst columns = [\"jobTitle\",\"location\",\"applyUrl\",\"jobUrl\",\"company\",\"salaryText\",\"salarySource\",\"workplaceType\",\"companyRating\",\"datePosted\"];\n// A dotted name such as author.name reads the nested value.\nconst read = (obj, key) => (key in obj ? obj[key] : key.split('.').reduce((v, part) => (v && typeof v === 'object' ? v[part] : undefined), obj));\nreturn $input.all().map((item) => {\n  const row = {};\n  const present = columns.filter((key) => read(item.json, key) !== undefined);\n  // A record shaped differently from the published schema keeps its own fields rather than arriving blank.\n  for (const key of present.length >= 2 ? present : Object.keys(item.json)) {\n    const value = read(item.json, key);\n    row[key] = value === null || value === undefined ? '' : typeof value === 'object' ? JSON.stringify(value) : value;\n  }\n  return { json: row };\n});"
         }
       },
       {
         "id": "b0822abe-5e55-47a1-a857-608c25231a0b",
         "name": "Send to Notion",
         "type": "n8n-nodes-base.notion",
         "typeVersion": 2.2,
         "position": [
           980,
           100
         ],
         "parameters": {
           "resource": "databasePage",
           "databaseId": {
             "__rl": true,
             "value": "",
             "mode": "list"
           },
           "title": "={{ [$json.jobTitle].filter((v) => v !== undefined && v !== null && v !== '').join(': ') || 'Untitled' }}",
           "propertiesUi": {
             "propertyValues": []
           },
           "blockUi": {
             "blockValues": [
               {
                 "type": "paragraph",
                 "textContent": "={{ [[\"location\", $json.location], [\"applyUrl\", $json.applyUrl], [\"jobUrl\", $json.jobUrl], [\"company\", $json.company], [\"salaryText\", $json.salaryText], [\"salarySource\", $json.salarySource], [\"workplaceType\", $json.workplaceType], [\"companyRating\", $json.companyRating], [\"datePosted\", $json.datePosted]].filter(([, v]) => v !== undefined && v !== null && v !== '').map(([k, v]) => k + ': ' + (typeof v === 'object' ? JSON.stringify(v) : v)).join(' | ').slice(0, 1900) || ' ' }}"
               }
             ]
           },
           "options": {}
         },
         "notes": "Pick your Notion database. Each page gets the record's main fields as its content; map extra database properties if you want to filter on them."
       },
       {
         "id": "9d28c126-b69e-4a59-afc6-8390eb235a63",
         "name": "Setup",
         "type": "n8n-nodes-base.stickyNote",
         "typeVersion": 1,
         "position": [
           0,
           -370
         ],
         "parameters": {
           "content": "## Indeed Job Search Scraper with Salary & Benefits Data\n\nSource: [vexaloom-labs/indeed-job-search-scraper-with-salary-and-benefits](https://apify.com/vexaloom-labs/indeed-job-search-scraper-with-salary-and-benefits) 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 Notion** and connect your Notion 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": "Keep main fields",
               "type": "main",
               "index": 0
             }
           ]
         ]
       },
       "Keep main fields": {
         "main": [
           [
             {
               "node": "Send to Notion",
               "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

3. Add the Apify credential

   Open Run Apify Actor. Under Credential, create a Header Auth credential with the name Authorization and the value Bearer, a space and your token.

4. Set the input

   The request body holds the Actor input. It starts from the Actor's Store prefill; change searchQueries, country, location to match your search.

   {
     "searchQueries": [
       "web developer in San Francisco"
     ],
     "country": "US",
     "location": "San Francisco",
     "radius": 25,
     "easyApplyOnly": false,
     "maxItems": 3,
     "includeDescriptionHtml": false,
     "includeCompanyRatings": false,
     "includeContacts": false,
     "includeCompanyReviews": false,
     "includeCompanySalaries": false,
     "expandBeyondCeiling": false
   }

   Every input field is documented on the Indeed Job Search Scraper with Salary & Benefits Data page.

5. 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 jobUrl it has passed on, so a record reaches Notion 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.

6. Connect Notion

   Open Send to Notion, select your Notion credential and pick the database. The page title comes from jobTitle and the page body holds the other fields and the long text; map database properties if you want to filter on them.

7. Run once, then turn it on

   Click Execute workflow and check the first records in Notion. When they look right, activate the workflow so the daily trigger runs it at 08:00 in your instance's timezone.

What lands in Notion

The fields this workflow sends, filled from the example record in the Actor's own README (published by the Actor, not a run of ours).

Field	Example value
jobTitle	Senior Software Engineer (AI Products)
location	New York, NY
company	Brillian
salaryText	$200,000 - $240,000 a year
salarySource	EMPLOYER
workplaceType	Hybrid
datePosted	2026-06-10T14:24:55Z

Where it breaks

• Indeed access restrictions or service rate limits can stop collection, and long searches can exceed the synchronous request timeout.
• Missing salaryText or companyRating values leave those details absent; changes to jobTitle or jobUrl can also affect page titles and duplicate filtering.
• Notion database access or write permissions can prevent job pages from being created.
• Duplicate tracking happens before the Notion write, so failed delivery can suppress a later retry; clearing or exhausting its history can allow duplicate job pages.
• 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)).

Make or Zapier: Make or Zapier can connect the Apify source request to persistent jobUrl tracking and Notion page creation, using jobTitle for page titles and separate mappings for searchable database properties.

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.

Source: n8n issue: unrecognized node type after import

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.

Source: n8n HTTP Request node documentation

Every fix in one place

Same data in an agent

Want Claude, Cursor or ChatGPT to call the Actor directly instead of on a schedule? The Indeed Job Search Scraper with Salary & Benefits Data page has MCP configs for eight clients and a SKILL.md. The Indeed MCP server bundles every Indeed Actor in one URL.