Jobo for n8n
Job data as a workflow step.
Two nodes. Jobo runs searches, pulls the bulk feed and looks up companies or locations as part of any workflow. Jobo Trigger starts a workflow when a new job matching your filters is indexed — routing roles into Slack, a spreadsheet, a CRM, or an outreach sequence without anyone watching a job board.
npm install n8n-nodes-jobo-job-searchWhat can you do with the n8n integration?
Search jobs, sync the feed, and trigger workflows when a new role matching your filters is indexed.
Search and feed in one node
Filtered search for targeted queries and bulk feed for volume. Both share one job rate and your Job Search plan's included jobs; Feed is uncapped on the Unlimited plan.
A trigger that does not overspend
The trigger persists a watermark, so cost tracks the number of new jobs rather than how often it polls. Polling every 15 minutes and every hour cost the same.
Refuses to run unfiltered
A trigger with no narrowing filter matches the entire index. The node rejects that configuration rather than quietly billing for it.
Costs are in the run log
Every run logs credits spent and the balance remaining, so a surprise invoice is not the first you hear about it.
Expired jobs, free
Get Expired returns recently closed job IDs so a downstream copy stays in sync. It never consumes credits.
How do you connect n8n to Jobo?
One-time setup. After this, the data keeps itself current.
- 1
Install the node
In n8n, go to Settings → Community nodes → Install and enter the package name. On self-hosted n8n you can also install it from the command line.
bashnpm install n8n-nodes-jobo-job-search - 2
Add your credentials
Create a Jobo API credential and paste your key from enterprise.jobo.world/api-keys. The credential test issues a single-row search to confirm it works.
- 3
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 when a matching job appears.
- 4
Set at least one narrowing filter
A query, location, sources, skills or industries. This is required on the trigger, and a good idea everywhere else — usage is metered per returned job beyond any included jobs. Filter fields suggest valid values as you type, so you never guess at spellings.
What goes wrong with n8n, and how do you fix it?
The things people actually hit when running Jobo in n8n.
- 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”
- The filter is too broad for the poll interval. Narrow it. Job search is relevance-ordered with no sort option, so a partial page cannot be resumed safely — Jobo stops rather than silently skipping jobs. For high volume, use an Outbound Feed webhook instead.
- HTTP 402 from the node
- The balance cannot cover the request. It is checked before the request runs and prices the whole requested page, so retrying fails identically — top up, or lower the limit.
- Salary filters return almost nothing
- They only match jobs whose employer published a range, which is a minority of listings. Applying one narrows results far more than it appears to.
How do you get the most out of n8n?
- Leave the trigger at its default interval. Faster polling costs the same and only magnifies the impact of a misconfiguration.
- Use Get Many (Feed) rather than paging Search when you want volume — it uses the same job pricing but returns up to 1,000 at a time with a stable cursor.
- Route the trigger through a filter node before anything that sends messages, so a widened filter cannot spam a channel.
- For real-time delivery at volume, use Outbound Feed: included jobs, then the pay-as-you-go rate — or uncapped on the Unlimited plan.
Which other Jobo integrations work alongside n8n?
Start pulling live jobs into n8n
One API key covers every integration, and the same job index sits behind all of them.