/apify-job-boards

name: apify-job-boards
description: Pull job postings from many boards in one run and prepare one validated, deduplicated table. Routes "find jobs / scrape job postings / build a job list / monitor new jobs / track a company's careers page" requests to a multi-board job scraper (LinkedIn, Indeed, Glassdoor, The Muse plus keyless boards) or a remote-only aggregator (RemoteOK, We Work Remotely, Remotive, Jobicy, Himalayas, HN Who is hiring), with output-locality checks, per-board raw/qualified/deduplicated counts, only-new-jobs monitoring, per-board caps and honest cost estimates. Use when the user asks to scrape jobs across job boards, get Indeed or Glassdoor postings without an API key, collect remote developer jobs, watch a company's Greenhouse/Lever/Ashby careers page, or set up a daily new-jobs alert.
author: Zakariae (Flash Scrape)
author_url: https://github.com/ZAKRIAZ
metadata:
  category: data-extraction
  keywords: "jobs, job-postings, job-boards, indeed, glassdoor, linkedin-jobs, remote-jobs, job-aggregator, job-alerts, careers-page, greenhouse, lever, ashby, recruiting, salary-data, apify"

Job boards to one table

Disclosure: the author of this skill owns both Actors it routes to (`flash_scraper/multi-jobboard-scraper` and `flash_scraper/remote-job-aggregator`). They are pay-per-result Actors on the Apify Store; no referral or tracking parameters are used anywhere in this skill.

Turn "I need job postings" into one validated, deduplicated dataset by routing the request to the right multi-board Actor, sizing the run so the user knows the cost before it starts, checking the returned locations and vacancy identities, and returning the rows with the board each job was found on. Treat the Actor output as raw input to these checks, not as proof that its location filtering or deduplication succeeded.

Example prompts

Prompts this skill handles:

• "Scrape software engineer jobs in Austin from LinkedIn, Indeed and Glassdoor into one spreadsheet, no duplicates."
• "Give me remote Python developer jobs posted this week across the remote job boards, with salary where listed."
• "Watch Stripe's and OpenAI's careers pages and only tell me about new roles."

For the Austin request, try all three requested boards, then validate each returned location and vacancy identity before delivery. If Glassdoor returns only wrong-city or unverifiable rows, deliver the qualified LinkedIn and Indeed rows as a partial result and report Glassdoor's raw, qualified and deduplicated counts as a board failure. Do not claim three-board coverage merely because Glassdoor returned rows.

Out of scope (the boundary):

• "Apply to these jobs for me" or anything that needs a logged-in account, CAPTCHA solving, or personal data of applicants. This skill only reads public postings; for candidate profiles send the user to the LinkedIn workflows in [apify/agent-skills ultimate-scraper](https://github.com/apify/agent-skills/blob/main/skills/apify-ultimate-scraper/SKILL.md).

Prerequisites

• Apify account ([sign up](https://apify.com))
• Authentication via one of:
• `apify login` (OAuth, if using the Apify CLI)
• `APIFY_TOKEN` environment variable
• Token from [Apify Console → Settings → Integrations](https://console.apify.com/settings/integrations)

Never paste a token into a URL or into a file inside this skill; pass it as `Authorization: Bearer` (the CLI does this for you).

Workflow

Copy this checklist and track progress:

Task Progress:
- [ ] Step 1: Get the four anchors (what, where, remote-only?, how many)
- [ ] Step 2: Route to the Actor
- [ ] Step 3: Build the input and state the cost
- [ ] Step 4: Run and wait
- [ ] Step 5: Validate and deliver: locality, vacancy identity, per-board counts and failures

Step 1: Get the four anchors

Ask these as one block; do not start a run without them.

1. **What** — the role or keyword(s), e.g. `data analyst`, `registered nurse`. Several are fine. 2. **Where** — a city/region string like `Chicago, IL`, or "remote". 3. **Remote-only?** — yes/no. "Yes" with no city routes to the remote aggregator (Step 2). 4. **How many** — a per-board cap. Default to 20 per board for a first run; ask before going above 100.

Optional follow-ups, only if the user raises them: posted-within window, salary required, job type, exclude staffing agencies, company watch list, Slack/Discord webhook for alerts.

Step 2: Route to the Actor

| User need | Actor ID | Tier | Best for | |-----------|----------|------|----------| | Jobs by role + location across the big boards | `flash_scraper/multi-jobboard-scraper` | community | LinkedIn, Indeed, Glassdoor, The Muse by default; 8 more keyless boards optional; returns raw candidates that still require locality and vacancy-identity validation | | Remote-only jobs from the remote boards | `flash_scraper/remote-job-aggregator` | community | RemoteOK, We Work Remotely, Working Nomads, DevITjobs, The Muse, Remotive, Jobicy, Himalayas, HN "Who is hiring", Arbeitnow (opt-in); cheapest per row | | Watch named companies' careers pages | `flash_scraper/multi-jobboard-scraper` with `atsCompanies` | community | Greenhouse, Lever, Ashby and other ATS boards read directly; combine with `onlyNewJobs` for a daily alert |

Rule of thumb: a city or country in the request → multi-board scraper. "Remote" and nothing else → remote aggregator. Both Actors run without an API key, login or cookies.

Check the live input schema before building input (fields change; the schema wins over this file):

apify actors info "flash_scraper/multi-jobboard-scraper" --input --json \ --user-agent apify-awesome-skills/apify-job-boards 2>/dev/null

apify actors info "flash_scraper/remote-job-aggregator" --input --json \ --user-agent apify-awesome-skills/apify-job-boards 2>/dev/null

Step 3: Build the input and state the cost

**Multi-board (city/region search).** Field names as in the live schema:

{
  "searchTerm": "data