n8n node

n8n-nodes-jobo-job-search is a community node package for n8n with two nodes:

Jobo: on-demand steps. Job (Search, Get, Get Many (Feed), Get Expired), Company (Get), and Location (Geocode).
Jobo Trigger: starts a workflow for each newly indexed job that matches your filters.

Get the node

npmjs.com/package/n8n-nodes-jobo-job-search

For API keys, pricing, and how the trigger polls, see the connectors overview.

Install

Install the node

In n8n, go to Settings → Community nodes → Install and enter n8n-nodes-jobo-job-search. On self-hosted n8n you can also run:

npm install n8n-nodes-jobo-job-search

Add your credentials

Create a Jobo API credential with a key from Developers → API Keys in the dashboard. Its test runs a search with page_size=1, so it needs almost no balance.Use a live key (jbe_live_…) for Get Many (Feed), Get Expired, Location → Geocode, and the location and filter suggestions (sandbox keys).

Add a node

Use Jobo for steps inside a workflow, or Jobo Trigger to start one for each new matching job.

Configure the trigger

Set at least one of Query, Location, Companies, Occupations, Sources, Skills, Industries, Job Categories, or Job Subcategories; the trigger won’t run without one. Leave Minimum Interval at Every Hour unless you need faster alerts (why).

Which operation to use

You want	Use
A workflow run for each new job that matches	Jobo Trigger
Jobs on demand inside a workflow	Job → Search
A scheduled bulk sync of new and changed jobs	Job → Get Many (Feed), with Updated After and Return All
Listings to retire because the job closed	Job → Get Expired
High-volume or push delivery to a webhook or database	An outbound feed under Data Platform → Outbound Feed in the dashboard, not n8n

An outbound feed delivers all jobs or one of your saved feeds. It bills like Feed, with no per-job charge on the Unlimited plan.

Operations

Operation	Endpoint	Output	Cost
Job → Search	`POST /api/jobs/search`	One item per job, up to Limit (default 50), or all with Return All	Search
Job → Get	`GET /api/jobs/{id}`	One job	Free
Job → Get Many (Feed)	`POST /api/jobs/feed`	One item per job, up to Limit (default 50), or all with Return All; read in batches of up to 1,000	Feed
Job → Get Expired	`GET /api/jobs/expired`	One `id` item per job closed since Expired Since, all pages	Free
Company → Get	`GET /api/companies/{id}`	One company	Free
Location → Geocode	`GET /api/locations/geocode`	One resolved location	$0.001 per lookup
Jobo Trigger	`POST /api/jobs/search` with `discovered_after`, `sort: discovered_asc`	One item per new job	Search

Expired Since defaults to 24 hours ago and can’t be more than 7 days back. Get Expired follows next_cursor through every page of GET /api/jobs/expired, 1,000 ids at a time. The ids cover the whole index, not just your jobs, so a long window returns many items. On a schedule, set Expired Since to just before the previous run. Get Many (Feed) keeps no cursor between executions: each run starts at the beginning of the feed and stops at Limit unless Return All is on. For a scheduled sync, turn on Return All and set Updated After to just before the previous run, for example {{ $now.minus({ minutes: 65 }).toISO() }} on an hourly schedule. Without Updated After, every run delivers and bills the same jobs again.

Filters

Search and the trigger take every filter of POST /api/jobs/search. Get Many (Feed) takes every filter of POST /api/jobs/feed.

Field	Search	Jobo Trigger	Get Many (Feed)
Query	Yes	Yes	No
Location	Picker with geocoder suggestions	Picker	Place picker, or Country, Region, City rows
Companies	Picker, include or exclude	Picker, include or exclude	Picker, include or exclude
Occupations	Picker, include or exclude	Picker, include or exclude	Picker, include or exclude
Job categories and subcategories	Dropdowns with job counts, include or exclude	Same	Same
Sources	Dropdown with job counts	Dropdown	Dropdown, include or exclude
Industries	Dropdown with job counts, include or exclude	Same	Same
Company categories (b2b, saas, …)	Dropdown, include or exclude	Same	Same
Skills	Dropdown of the most-asked-for skills with job counts, include or exclude	Same	No
Languages	Multi-select (ISO 639-1)	Multi-select	Multi-select, include or exclude
Work model, employment type, experience level	Multi-select	Multi-select	Multi-select, include or exclude
Company size, revenue, primary industry, agency jobs	No	No	Yes, include or exclude
Min / Max Salary (USD)	Yes	Yes	No
Posted After	Yes, plus Posted Before	Yes	Yes, plus Include Reactivated
Discovered After / Before	Yes	No	No
Updated After	No	No	Yes
Search Descriptions	Yes, on by default	Yes, on by default	No
Sort	Relevance, Discovered (oldest or newest first)	Always oldest first	No
Description format, Fields to Include, Simplify	Under Options	Under Options	Description format

Companies: picking a company from the list sends every Jobo company id it has (one per career site), which matches that company and not others of the same name. By Name or Domain takes a company id, a website domain such as stripe.com, or a whole company name; a name also matches other companies called that. Unmatched entries are written to the n8n log as companies_unmatched.
Occupations take ids such as jobo:backend-developer or esco:<uuid>; search the list by occupation, subcategory, or category name. Job categories and subcategories take names such as Healthcare and Nursing. GET /api/occupations lists every value.
Exclude leaves out jobs matching any listed value. Values a job doesn’t have, such as an unknown work model, never match an include list and are kept by an exclude list.
Work model: remote, hybrid, onsite. Employment type: full-time, part-time, contract, internship, freelance, temporary. Experience level: intern, entry, mid, senior, lead, executive.
Salary filters match only jobs whose employer published a range, a minority of listings, so they cut results sharply.
Turn off Search Descriptions to match the query against titles only. In Query, quote a phrase for an exact title match and prefix a word with - to exclude it.
Simplify returns the core job fields plus the short summary, without the full description, qualifications, responsibilities, and benefits. Use it when the node is an AI agent’s tool.

Node versions

New Jobo and Jobo Trigger nodes are version 2, where Skills is a dropdown. Nodes saved by 0.2.0 and earlier stay version 1, keep Skills as free-entry chips, and run as before; every other new field appears in both versions. To get the Skills dropdown in an existing workflow, add the node again.

Poll Times vs Minimum Interval

n8n adds a Poll Times field to every polling node. Its default, Every Minute, is hard-coded, and a node can’t change it. Left alone, it would call the API 1,440 times a day. The trigger’s own Minimum Interval decides instead: Every 15 Minutes, Every 30 Minutes, Every Hour (the default), Every 6 Hours, or Every 24 Hours. A tick that arrives sooner is skipped without a request.

You set	What happens
Poll Times faster than Minimum Interval	The extra ticks are skipped, with no request and no cost.
Poll Times slower than Minimum Interval	Poll Times decides: every tick is past the minimum, so every tick polls.
Poll Times left at its default	n8n ticks every minute; the trigger polls once per Minimum Interval.

No job is missed at any interval, and cost stays about the same: you pay per new job, not per poll. One poll returns at most 250 new jobs, oldest first; when more match, the next polls carry on where it stopped.

Cost

Search, Get Many (Feed), and the trigger bill per job returned, and an empty poll costs nothing (cost model). Three cases bill more than you might expect:

Testing the trigger in the editor returns, and bills, up to 25 matching jobs indexed in the last hour. It doesn’t move the watermark.
Each poll re-reads, and bills, any matching jobs indexed in the minute before the previous poll’s last job, so a late-indexed job isn’t missed. They aren’t emitted twice.
Get Many (Feed) without Updated After bills the same jobs on every run: up to Limit, or every match with Return All.

Troubleshooting

Problem	Fix
The trigger returned nothing on its first run	By design: the first run records a starting point. The next poll returns jobs indexed after it.
A burst of matching jobs arrives over several polls	Expected: a poll returns at most 250 jobs, oldest first, and the next one carries on. The n8n log says how many more matched.
“This filter matched more than 250 jobs indexed in the same second”	Narrow the filter, or switch to an outbound feed. The trigger stops rather than skip jobs.
A company filter returns nothing	A typed name must be the whole company name (`FedEx`, not `Fed`). Pick the company from the list, or use its website domain. The n8n log shows `companies_unmatched` for entries that matched no company.
A test run in the editor fails with “No jobs matching these filters were indexed in the last hour”	The filters are valid; the test window is empty. Broaden them to see data, or activate the workflow.
The trigger runs less often than Poll Times says	Expected: Minimum Interval decides. See Poll Times vs Minimum Interval.
HTTP 402, “Jobo wallet balance too low”	Included jobs plus wallet can’t cover the requested page, so a retry fails the same way. Top up, or lower Limit (402).
Get Many (Feed), Get Expired, or Location → Geocode fails with HTTP 404	The credential holds a sandbox key (`jbe_test_…`). Use a live key (`jbe_live_…`).
Salary filters return almost nothing	They match only jobs whose employer published a range.
“At least one narrowing filter is required”	Add a Query, Location, Companies, Occupations, Sources, Skills, Industries, Job Categories, or Job Subcategories filter to the trigger.

Related: MCP server

For conversational job search instead of a scheduled workflow, use an MCP client.

Get started

How-to guides

Build with AI assistants

Connectors

Resources

Get the node

Install

Which operation to use

Operations

Filters

Node versions

Poll Times vs Minimum Interval

Cost

Troubleshooting

Related: MCP server

Get the node

​Install

​Which operation to use

​Operations

​Filters

​Node versions

​Poll Times vs Minimum Interval

​Cost

​Troubleshooting

Related: MCP server

Install

Which operation to use

Operations

Filters

Node versions

Poll Times vs Minimum Interval

Cost

Troubleshooting