Automation

Jobo for Zapier

New jobs as a trigger, job search as a step.

The Jobo app for Zapier has one trigger and four searches. New Job starts a Zap for each job that matches your filters and is new since the last poll, so a role can go straight into Slack, a sheet, a CRM or an outreach sequence. Find Jobs runs a filtered search as a step; Find Job by ID, Find Company and Geocode Location look up a single record. You connect with a Jobo API key.

Get an API key Zapier — coming soon
Zapier logoZapierWhat the app adds to Zapier
Trigger
New Job
Searches
Find Jobs, Find Job by ID, Find Company, Geocode Location
Connects with
A Jobo API key
New Job is billed
Once per job, however often Zapier polls

What can you do with the Zapier integration?

Start a Zap when a new job matching your filters is indexed, or look up jobs and companies as a step in one.

01

A trigger that bills each job once

Zapier re-reads a recent window on every poll. The trigger reads Jobo's feed, which charges for a job only the first time you receive it in 30 days, so polling more often does not cost more.

02

Refuses to run unfiltered

The trigger needs at least one narrowing filter: a location, sources, companies, industries, job categories or occupations. Find Jobs will not run with no filter set either.

03

Dropdowns with real values

Sources, industries, skills, job categories, occupations, companies and locations load their choices from Jobo, so you pick values the index actually holds.

04

Flat, stable output

Every record comes back with the same snake_case fields, with the job's first location spread into city, region and country, so later steps map fields without code.

05

Free lookups

Find Job by ID and Find Company do not use credits. Geocode Location costs $0.001 per lookup.

How do you connect Zapier to Jobo?

One-time setup. After this, the data keeps itself current.

  1. 1

    Connect your Jobo account

    Add the Jobo app to a Zap and paste an API key from Developers → API Keys in the Jobo dashboard. The connection test does not use credits, and a mistyped key is rejected before any request is made.

  2. 2

    Choose New Job as the trigger

    Or add Find Jobs as a step in an existing Zap when you want a search on demand rather than a stream of new roles.

  3. 3

    Set the filters

    Pick at least one of location, sources, companies, industries, job categories, job subcategories or occupations, then narrow further by work model, employment type, experience level or language. Companies and Location each have a lookup field above them: type a few letters there, then open the dropdown.

  4. 4

    Add the steps that use the job

    Each run carries one job: title, company, location, salary when the posting states one, and the listing and apply URLs. Map those fields into the next step.

What goes wrong with Zapier, and how do you fix it?

The things people actually hit when running Jobo in Zapier.

The trigger has no keyword field
The feed the trigger reads has no keyword, skills or salary filter. Match on job categories or occupations instead, or add a Filter step after the trigger. A job the Filter step drops was still delivered, and billed once.
Turning the Zap on used credits but started no runs
Zapier's first read records what already exists so it only triggers on what comes after. Those jobs are delivered, and billed, once.
The trigger stops with a message that the filters match too many jobs
More than 500 new jobs matched in one window. The trigger fails rather than returning part of them. Narrow the filters, or use an Outbound Feed for that volume.
A sandbox key connects but the trigger fails
A sandbox key serves Find Jobs and Find Job by ID only. The trigger, Find Company, Geocode Location and the dropdowns need a live key.

How do you get the most out of Zapier?

  • Put a Filter step before anything that sends a message, so a widened filter cannot flood a channel.
  • Keep the Zap on. The trigger looks back six hours, so a Zap that is paused for longer misses the jobs posted in the gap.
  • Without a Job Search plan, keep enough balance to cover a full poll of 100 jobs, or the poll is refused before it runs.
  • For continuous delivery at volume, use an Outbound Feed rather than a Zap.

Start pulling live jobs into Zapier

One API key covers every integration, and the same job index sits behind all of them.