n8n node

n8n-nodes-jobo-job-search is a community node for n8n that brings Jobo’s job data into any workflow. Two nodes ship together:

Jobo — on-demand operations: Job (Search, Get, Get Many/Feed, Get Expired), Company (Get), Location (Geocode).
Jobo Trigger — polls for newly indexed jobs matching your filters and starts a workflow for each one.

Get the node

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

This page assumes you’ve read the shared Authentication, Cost model, and Polling and watermark semantics sections on the connectors overview — it only covers what’s specific to n8n.

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 and paste your key from enterprise.jobo.world/api-keys. Sign up free first if you don’t have a Jobo account yet — the $5 free starting balance is enough to try the node.The credential test issues a page_size=1 search — deliberately small, since the balance precheck prices the requested page size, and a larger probe would demand a bigger balance just to verify a key.

Add a Jobo node, or a Jobo Trigger

Use the Jobo node for on-demand lookups inside an existing workflow. Use Jobo Trigger to start a workflow whenever a matching job appears.

Set at least one narrowing filter

A query, location, sources, skills, or industries — required on the trigger, and a good idea everywhere else, since usage is billed per job returned after any included jobs.

Leave the trigger's Minimum Interval alone

It defaults to Every Hour. n8n’s own Poll Times field above it defaults to Every Minute and cannot be changed by a node — see Poll Times vs Minimum Interval.

Filters

Every filter field on both nodes suggests values as you type rather than expecting you to know the exact spelling:

Field	Behaviour
Location	A searchable resource picker — start typing and pick from live suggestions resolved through Jobo’s geocoder.
Sources	A dropdown loaded from the current index, so you pick a real ATS platform rather than typing a slug from memory.
Industries	Same — a dropdown of the industries currently represented in the index.
Skills	Free-entry: type a skill and add it as a chip. Skills aren’t a fixed list, so this field doesn’t suggest values, but it does let you add as many as you need.
Work model / Employment type / Experience level	Fixed multi-select lists: remote/hybrid/onsite; full-time/part-time/contract/internship/freelance/temporary; intern/entry/mid/senior/lead/executive.
Salary min / max (USD)	Only matches jobs whose employer published a range — a minority of listings. Applying either narrows results more than it looks like it should.

The Jobo Trigger requires at least one of query, location, sources, skills, or industries before it will save — see Polling and watermark semantics for why.

Operations

Node	Operation	Notes
Jobo	Job → Search	`GET /api/jobs`. Included jobs first, then the pay-as-you-go rate, per job returned.
Jobo	Job → Get	`GET /api/jobs/{id}`. Single job lookup, no credits.
Jobo	Job → Get Many (Feed)	`POST /api/jobs/feed`. Same pricing and pool of included jobs as Search; no per-job charge on Unlimited. Returns up to 1,000 per request and is the stable bulk-sync path.
Jobo	Job → Get Expired	`GET /api/jobs/expired`. Free.
Jobo	Company → Get	`GET /api/companies/{id}`. No key required, no credits.
Jobo	Location → Geocode	`GET /api/locations/geocode`. Flat metered lookup.
Jobo Trigger	Polls for new jobs	Uses `discovered_after` as its watermark.

Poll Times vs Minimum Interval

The Jobo Trigger has two interval settings, and only one of them decides anything. n8n injects a Poll Times field into every polling node, with the default hard-coded to Every Minute. A node cannot narrow that list or change that default, so a trigger nobody configured would call the API 1,440 times a day. The trigger therefore carries its own Minimum Interval — options from 15 minutes to 24 hours, defaulting to Every Hour — and that is the interval Jobo honours. A tick that arrives sooner is skipped before any HTTP request is made.

You set	What happens
Poll Times faster than Minimum Interval	Nothing changes. The extra ticks are skipped with no request and no cost.
Poll Times slower than Minimum Interval	Poll Times wins — n8n simply never fires the tick.
Poll Times unset (the default)	n8n ticks every minute; Jobo polls once per Minimum Interval.

No jobs are missed at any interval. A poll returns everything indexed since the previous one, however long ago that was, and cost is unchanged either way — search is metered per job returned, not per request. The one thing a longer interval does change is how many jobs pile up per window: a filter matching more than 250 new jobs in one interval fails loudly rather than returning an arbitrary subset. See the troubleshooting entry below.

Cost

Search and Feed are billed per job returned; an empty poll costs nothing. A Job Search plan’s included jobs apply before the pay-as-you-go rate. With a correctly persisted watermark, cost does not depend on how often the trigger polls — only new matching jobs bill, at the pay-as-you-go rate of $3.00 per 1,000 jobs. For high-volume or genuinely real-time delivery, use a Jobo Outbound Feed. It uses the same included jobs and pay-as-you-go rate, or is unlimited with Jobs Feed.

Troubleshooting

Problem	Fix
The trigger returned nothing on its first run	By design. The first run records a starting point rather than backfilling the whole index, which would be both surprising and expensive. The next poll returns jobs indexed after that moment.
”This filter matched more jobs than a single poll can safely return”	More than 250 new jobs matched in one interval. Narrow the filter, or shorten Minimum Interval so each window holds fewer. Job search is relevance-ordered with no sort option, so a partial page can’t be resumed safely — the trigger stops rather than silently skipping jobs. For sustained high volume, use an Outbound Feed webhook instead.
The trigger runs less often than Poll Times says	Expected. Minimum Interval on the node is the one that decides; ticks arriving sooner are skipped without a request. See Poll Times vs Minimum Interval.
HTTP 402 from the node	The balance can’t cover the request. It’s checked before the request runs and prices the whole requested page, so retrying fails identically — top up, or lower the limit. See Errors.
Salary filters return almost nothing	They only match jobs whose employer published a range, which is a minority of listings.
The trigger won’t save without a filter	Expected — see Polling and watermark semantics. Add a query, location, sources, skills, or industries filter.

Related: MCP server

For ad-hoc, conversational job search rather than a scheduled workflow, an MCP client may be a better fit.

Get started

How-to guides

Connectors

Changelog

Get the node

Install

Filters

Operations

Poll Times vs Minimum Interval

Cost

Troubleshooting

Related: MCP server

Get the node

​Install

​Filters

​Operations

​Poll Times vs Minimum Interval

​Cost

​Troubleshooting

Related: MCP server

Install

Filters

Operations

Poll Times vs Minimum Interval

Cost

Troubleshooting