Skip to main content
The Jobo app for Zapier has one trigger and four searches.
The app is built and tested but not registered with Zapier yet, so it does not appear in Zapier’s app directory today.
For API keys and pricing, see the connectors overview.

Connect

Add the Jobo app to a Zap and paste a key from Developers → API Keys in the dashboard. The connection test never uses credits, and a mistyped key is rejected before any request. A sandbox key connects and serves Find Jobs and Find Job by ID. New Job, Find Company, Geocode Location, and the dropdowns need a live key.

New Job

Set at least one of Location, Sources, Companies, Industries, Job Categories, Job Subcategories, or Occupations; the trigger won’t run without one. You can narrow further by Work Model, Employment Type, Experience Level, Languages, and Company Categories. The trigger has no keyword, skills, or salary filter, because the feed it reads has none. 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. Companies and Location each have a lookup field above them. Type two or more letters there, then open the dropdown.

How it polls, and what it costs

A Zapier polling trigger keeps no watermark: each poll asks for a recent window and Zapier drops the jobs it has already seen. Search would bill those repeats on every poll, so the trigger reads the feed instead, which bills a job only the first time you receive it in 30 days. The bill follows the number of new matching jobs, not how often Zapier polls. Limits to know:
  • Wallet cover. Without a Job Search plan, each poll needs a balance that covers a full batch of 100 jobs ($0.30), even when it delivers nothing new. A lower balance fails the poll with 402.
  • Gaps. Each poll looks back 6 hours. If the Zap is off for longer, jobs indexed in the gap aren’t delivered. Find Jobs with Discovered After reads them.
  • Volume. If more than 500 jobs match in one window, the trigger fails with a message instead of returning part of them. Narrow the filters, or use an outbound feed under Data Platform → Outbound Feed in the dashboard.

Find Jobs

Every filter of POST /api/jobs/search, plus Maximum Jobs (1 to 100, default 10). The search refuses to run with no filter set, because that would return, and bill, the first page of the whole index.

Output

Every trigger and search returns flat records with snake_case keys and an id. A job’s first location is spread into location, city, region, country, latitude, and longitude, with every location in all_locations. A missing value is null; the key is always present.

Related: n8n node

The n8n trigger persists a watermark, so it can also filter on keywords and skills.