apify-bulk-job-listings-exportlisted

Export Google Jobs listings to CSV, Excel, Sheets, or JSON in bulk with the Apify Google Jobs Scraper API Pay Per Result Actor (johnvc/google-jobs-scraper---pay-per-result). Output is already flat, one row per opening, so a dataset export drops straight into a spreadsheet or a database load with no reshaping. Covers multi-query batches, exclusion filters that shrink the file and the bill together, and job_id dedupe across runs. Use when the user wants to export google jobs to csv, download job listings as a spreadsheet, build or backfill a job board, load openings into a warehouse or ATS, or bulk export job postings for many roles and cities at a known cost. Pay-per-result billing, MCP-ready for Claude and other AI agents.
johnisanerd/claude-skill-bulk-job-listings-export · ★ 0 · Data & Documents · score 66

Install: claude install-skill johnisanerd/claude-skill-bulk-job-listings-export

# Bulk Job Listings Export With a Cost You Can Budget Pull Google Jobs openings in bulk and hand back a file. The Actor writes flat rows, so CSV, Excel, Sheets, and JSON exports come out clean, and because billing is per result the invoice equals the row count. ## When to use this skill - The user wants to export Google Jobs listings to CSV, Excel, Google Sheets, or JSON. - They are seeding or backfilling a job board, an ATS, a warehouse table, or a research dataset. - They need many roles or many cities in one deliverable file. - They need to quote a data-pull cost up front, before anyone approves the run. Not for: a live low-latency search endpoint inside an app, salary analytics (there is no numeric salary field), or LinkedIn-only listings (use the LinkedIn Jobs API). ## Why per-result billing matters for bulk work Bulk exports are where page-based pricing gets unpredictable, because a page that returns three listings costs the same as a page that returns ten. Here you pay for delivered rows. A 500-row export costs 500 result charges whether Google served them across 50 tidy pages or 80 ragged ones, so the estimate you give before the run is the number on the invoice after it. ## What lands in the file (one flat row per listing) Verified on a live run: `title`, `job_title` (same string as `title`), `company_name`, `location`, `via` (hosting platform), `description` (full posting text), `job_highlights` (array of `{title, items}` blocks such as Qualifications, Resp