Connectors overview

A connector calls the Jobo API for you from a WordPress site, an n8n workflow, a spreadsheet, or an AI assistant. It handles the key, filters, and paging in that platform’s own UI. To call the API yourself, start with the quickstart or an SDK.

---

​

Authentication

WordPress, n8n, and Sheets use an API key. Create one under Developers → API Keys in the dashboard. New accounts get a $5 free starting balance, no credit card required. That’s enough to try any connector (sign up). Live keys look like jbe_live_… and are 74 characters long. Each connector checks the key when you save it, so a typo fails at setup instead of on the first sync. People who can only view the site, workflow, or spreadsheet never see the key. For key format, rotation, and storage, see Authentication.

​

Sandbox keys

A sandbox key (jbe_test_…) returns fictional jobs for free. Of the endpoints connectors call, it serves only search and job and company lookups; the rest answer 404 with not_available_in_sandbox (Sandbox).

---

​

Cost model

Connectors have no fee of their own: you pay for the jobs their API calls deliver. Empty results, failed requests, and rate-limited requests cost nothing. Search and Feed jobs use a Job Search plan’s included jobs first, then the pay-as-you-go rate of $3.00 per 1,000 jobs. “Covered” means no per-job charge. Billing has the plans, the wallet, and the free endpoints. Jobo prices a full page (page_size or batch_size) before each Search or Feed request, so a large page can fail with 402 while your balance is above zero. Lower the page or batch size, or top up (request flow).

---

​

Polling and watermark semantics

Only the n8n trigger and the WordPress plugin poll. The Sheets add-on imports once per click, and the MCP server answers each tool call. For both, cost tracks how many new or changed jobs match your filters, not how often the connector runs.

​

Jobo Trigger

• The first run records a starting point instead of backfilling, and billing, the whole index.
• It refuses to run without a narrowing filter: a query, location, companies, occupations, sources, skills, industries, job categories or job subcategories.
• One poll returns at most 250 new jobs, oldest first (sort: discovered_asc). When more match, the next polls carry on where it stopped, so a burst arrives over several polls instead of failing. Only more than 250 matching jobs indexed in the same second stop the trigger (n8n troubleshooting).
• Each poll returns everything indexed since the previous one, so no job is missed at any interval. n8n’s own Poll Times field doesn’t set the interval; see Poll Times vs Minimum Interval.

​

WordPress plugin

Each run resumes the saved cursor, so a run that stops part-way loses nothing. After the first import, a sync asks only for jobs new or changed since the previous scan began. Changing filters, Resync everything, and a sync stalled for more than 6 days deliver and bill every matching job again. See WordPress cost.

---

​

Autocomplete on filter fields

Location, source, and industry fields suggest real values as you type. Locations come from Jobo’s geocoder; sources and industries come from the live index. In the n8n node, skills, companies, job categories, and occupations also suggest values, with live job counts where the index has them; elsewhere skills are free entry: type one and press Enter to add it as a chip. Pick from the suggestions where a field offers them. An unrecognized value matches nothing and returns no error (search recipes). Each connector’s Filters table shows which fields suggest values.

---