Jobo for Make
Job data as modules in a scenario.
The Jobo app for Make adds eight modules. Watch new jobs starts a scenario for each job that matches your filters and has appeared since the last run. Search jobs runs a filtered search; Get a job, Get a company and Search companies look up single records; List expired job IDs keeps a downstream copy current; Geocode a location resolves a place name; and Make an API call reaches any other endpoint with the same connection. You connect with a live Jobo API key.
- Trigger
- Watch new jobs
- Searches
- Search jobs, Search companies, List expired job IDs
- Actions
- Get a job, Get a company, Geocode a location, Make an API call
- Connects with
- A live Jobo API key
What can you do with the Make integration?
Watch for new jobs matching your filters, search the index, and look up jobs and companies as modules in a scenario.
A trigger that bills each job once
Make re-reads from its watermark by design, and rolls it back when a run fails. Watch new jobs reads Jobo's feed, which charges for a job only the first time you receive it in 30 days, so a re-read costs nothing.
A limit on every billed module
Watch new jobs and Search jobs both require a Limit, which defaults to 10. The trigger never requests a larger batch than its Limit.
Refuses to run unfiltered
Watch new jobs needs at least one narrowing filter. Without one it stops with a configuration error before any billed request is made.
Dropdowns with real values
Sources, skills, industries, job categories and occupations load from Jobo, ranked by live job count. Company and location fields have a search button.
Free lookups and expiry sync
Get a job, Get a company, Search companies and List expired job IDs do not use credits. Geocode a location costs $0.001 per lookup.
How do you connect Make to Jobo?
One-time setup. After this, the data keeps itself current.
- 1
Create a connection
Add a Jobo module to a scenario and create a connection with an API key from Developers → API Keys in the Jobo dashboard. The connection check does not use credits. Use a live key: the app rejects a sandbox key with an explanation.
- 2
Start with Watch new jobs
Or add Search jobs to an existing scenario when you want a search on demand rather than a stream of new roles.
- 3
Set the filters and the Limit
Pick at least one narrowing filter on the trigger, such as a location, sources, companies, industries, job categories or occupations. Limit is the most jobs one run reads, from 1 to 1,000.
- 4
Add the modules that use the job
Each bundle is one job: title, company, locations, compensation when the posting states it, and the listing and apply URLs. Map those fields into the next module.
What goes wrong with Make, and how do you fix it?
The things people actually hit when running Jobo in Make.
- Watch new jobs has no keyword field
- The feed the trigger reads has no keyword, skills or salary filter. Match on job categories or occupations instead, or put a filter after the trigger. A job the filter drops was still delivered, and billed once.
- The connection rejects my key
- Sandbox keys are not accepted. The lookups behind the dropdowns, the feed, expired job IDs and geocoding are not available to a sandbox key, so the app asks for a live one.
- Search jobs returned a few more jobs than its Limit
- Above a Limit of 100 the search reads equal pages, so it can return, and bill, up to one job more per page after the first. Set the Limit to a multiple of the page count if the exact figure matters.
- A module stops with an insufficient credits error
- The balance cannot cover the request. The check prices the whole requested batch, so re-running fails the same way. Top up, or lower the Limit.
How do you get the most out of Make?
- Leave the trigger's Limit low until the filters are right. It is the most a single run can cost.
- Put a filter before anything that sends a message, so a widened filter cannot flood a channel.
- Schedule List expired job IDs to remove closed roles from wherever the scenario writes jobs. It is free.
- For continuous delivery at volume, use an Outbound Feed rather than a scenario.
Which other Jobo integrations work alongside Make?
Start pulling live jobs into Make
One API key covers every integration, and the same job index sits behind all of them.













