Recruitee Jobs Scraper & Monitor: Open Jobs & Changes avatar

Recruitee Jobs Scraper & Monitor: Open Jobs & Changes

Pricing

from $0.32 / 1,000 job rows

Go to Apify Store
Recruitee Jobs Scraper & Monitor: Open Jobs & Changes

Recruitee Jobs Scraper & Monitor: Open Jobs & Changes

Get open jobs from the Recruitee career boards of employers you track. Filter by title keyword, excluded words, department, location, remote work or posting date, export to CSV or JSON, and see which jobs were added, changed or removed since your last snapshot.

Pricing

from $0.32 / 1,000 job rows

Rating

0.0

(0)

Developer

Cliqto Media

Cliqto Media

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

4 days ago

Last modified

Categories

Features

Limited permissions

Share

Get the open jobs of employers that hire through Recruitee, filter them by title keyword, excluded words, department, location, remote work or posting date, and see which jobs were added, changed or removed since your last check. You enter known company slugs or Recruitee board URLs and get one Dataset row per job with 20 fields, a reusable snapshot and a run summary. The data comes from the public Recruitee careers API (the job offers feed), so you need no login or API key. The prefilled first run (one company, 14 jobs on 2026-10-26) costs about USD 0.025.

Use it to monitor job changes on the career pages of employers you already know. In changes mode, send your saved snapshot and the Actor tells you which jobs were added, updated or removed.

Job cards and a supplied snapshot show added, updated and removed rows

The picture shows the workflow. It is an illustration, not a run result or an alert service.

Table of contents

What it does

The Actor reads published jobs from the public Recruitee feed of each company you name. It turns each valid job into the same 20 fields: title, department, locations, workplace type, employment type, links, dates, salary and an optional plain-text description. Job rows go to the Dataset. The run's Key-value store gets SNAPSHOT, RUN_SUMMARY and OUTPUT.

In changes mode it also writes CHANGES: the difference between the current jobs and the previousSnapshot you send. The Actor does not find earlier runs by itself, keep history or send notifications. It does not discover companies, read applicant records or apply for jobs.

This is an independent data tool. It is not affiliated with Recruitee or the companies whose public boards it reads. The source feed is described in the Recruitee offers reference.

Good fit

  • Keep a clean list of open jobs for a few known employers that use Recruitee.
  • See which jobs were added, changed or closed since your last saved snapshot.
  • Compare published salary ranges, locations and remote/hybrid work across employers.
  • Watch only the jobs you care about, such as engineering roles in Germany without senior titles, or remote jobs posted this week.

๐Ÿ‘‰ Try it now: open the input form

How it works

  1. You give up to four company slugs, such as channable, or their https://<company>.recruitee.com URLs.
  2. For each unique company, the Actor reads the public Recruitee job feed once and checks every job for required fields.
  3. It keeps only the jobs that pass your filters, if you set any, and saves them as Dataset rows, the full list as SNAPSHOT, and per-company results in RUN_SUMMARY.
  4. In changes mode it compares the new jobs with your snapshot and saves CHANGES. It reports removals only when every company was read completely.

๐Ÿ‘‰ Try it now: open the input form

Quick start

Input form: box 1 is the prefilled Recruitee company, box 2 is the filters and settings to leave as they are

  1. Open the Input tab. The form is prefilled with channable in Recruitee companies (box 1 in the picture).

  2. Leave the other fields as they are (box 2): filters empty, descriptions off, Save current jobs on, up to 25 jobs per company.

  3. Click Start.

  4. Open the Output tab or the Dataset (box 4 in the picture). Each row is one job with title, location, workplaceType and url.

    Output table: one row per open Recruitee job with title, location, work type and job link

    The cost in the run header is platform usage, not the Store price per job.

  5. Open RUN_SUMMARY in the Key-value store and check that the company outcome is complete.

  6. To compare later, save the whole SNAPSHOT record.

Expected result: all open Channable jobs (14 on 2026-10-26) and a summary with outcome complete. Job counts change as the employer opens and closes positions. If a company has more jobs than Maximum jobs per company, its outcome is partial and the status message tells you to raise the limit.

๐Ÿ‘‰ Try it now: open the input form

Use cases

  • Track open jobs at the employers you follow, or only new postings with mode: "changes".
  • Compare published pay, remote work and locations across companies.
  • Watch for new engineering, sales or remote openings with filters.
  • Feed job texts to another tool with includeDescription: true.

The table under Output shows the input and fields for each job.

๐Ÿ‘‰ Try it now: open the input form

Input

Input fields

FieldPlain nameTypeRequiredDefault / prefillAllowed valuesEffectExampleRecommendation
companiesRecruitee companiesarray of stringsyesno default; prefill ["channable"]1โ€“4 slugs or https://<company>.recruitee.com URLsWhich boards to read["channable"]Use the Recruitee slug, not a custom careers domain
keywordsJob title keywordsarray of stringsnoempty (all titles)up to 20 words, 100 characters eachKeeps jobs whose title has a word starting with any term, case-insensitive["engineer", "sales"]Use word starts: engineer matches Engineering Manager, gineer matches nothing
excludeKeywordsExclude title keywordsarray of stringsnoempty (drop nothing)up to 20 words, 100 characters eachDrops jobs whose title has a word starting with any term, case-insensitive["senior", "intern"]senior drops Senior Engineer; ior drops nothing
departmentsDepartmentsarray of stringsnoempty (all departments)up to 20 words, 100 characters eachKeeps jobs whose department has a word starting with any term; jobs without a department are skipped["engineering", "sales"]Run once without it to see the board's department names
locationsLocationsarray of stringsnoempty (all places)up to 20 words, 100 characters eachKeeps jobs whose location, allLocations or country has a word starting with any term["Germany", "Amsterdam"]country is a two-letter code such as NL; nl does not match Helsinki
remoteOnlyRemote jobs onlybooleannofalsetrue, falseKeeps only jobs with workplaceType: "remote"trueHybrid jobs are not remote here
postedWithinDaysPosted within daysintegernoempty (any date)1โ€“365Keeps jobs whose postedAt is within the last N days7Combine with changes mode to see this week's new jobs
includeDescriptionInclude descriptions and requirementsbooleannofalsetrue, falseFills descriptionText with plain textfalseTurn on only when you need texts: rows become larger
maxJobsPerCompanyMaximum jobs per companyintegerno251โ€“100Caps returned rows per unique company, counted after filters100Raise it for large boards; a cap below the matching total makes a board partial
modeSnapshot or comparisonstringno"snapshot"snapshot (Save current jobs), changes (Compare with my previous snapshot)changes also writes CHANGES"snapshot"Use changes only with a saved snapshot
previousSnapshotPrevious snapshotobjectonly for changesnoneThe whole SNAPSHOT record, shaped {"rows": [...]}Baseline for the comparison{"rows": []}Keep the same companies, filters, cap and description choice as the earlier run

Slugs are made lowercase. Duplicate companies share one fetch but still count as input entries. A URL is reduced to its company host; paths are not used as filters. Custom domains, private hosts, HTTP URLs, credentials in URLs, ports, query strings and fragments are rejected. The whole input is limited to 256 KiB.

Filters are optional and all of them must match: keywords, departments and locations each pass when any one word matches, and excludeKeywords drops a job when any one word matches its title. Leave them empty to get every job, as before. There is no salary filter; filter that column in your own tool. There is no hidden state or reset option. To start a new baseline, send previousSnapshot: {"rows": []}.

Interacting settings

WhenInput AInput BEffective behaviorExampleCost/result effect
A board has more jobs than the capmaxJobsPerCompanymode: "changes"The board is partial and removals are suppressed for the runcap 10 on a board with 20 jobsFewer rows charged; removed stays empty
Settings differ from the snapshot runincludeDescription or maxJobsPerCompanypreviousSnapshotRows differ for reasons unrelated to the sourcedescriptions on now, off beforeMany updated rows
Filters are set in changes modekeywords, excludeKeywords, departments, locations, remoteOnly, postedWithinDayspreviousSnapshotOnly previous rows that pass the same filters are compared; others are not reported as removedremoteOnly: true with an unfiltered snapshotA job that leaves the filter window is not removed
Filters and the capfiltersmaxJobsPerCompanyFilters run first; the cap counts matching jobs only3 matching jobs, cap 25Outcome complete; you pay for 3 rows
Run cost limit is too lowmaxJobsPerCompany ร— companiesrun cost limitThe run stops before fetching with RESOURCE_LIMIT4 companies ร— 100 with a limit of USD 0.10Only the start charge

Input examples

First snapshot of one employer

{"companies": ["channable"], "includeDescription": false, "maxJobsPerCompany": 10, "mode": "snapshot"}

Expected behavior: reads one board and saves up to 10 jobs. Channable has more open jobs, so its outcome is partial. Expected output: job rows with title, location, workplaceType, url, salary. Limit or cost note: one start event plus one charge per returned job row.

Start a comparison baseline with descriptions

{
"companies": ["channable", "https://channable.recruitee.com/"],
"includeDescription": true,
"maxJobsPerCompany": 10,
"mode": "changes",
"previousSnapshot": {"rows": []}
}

Expected behavior: the duplicate URL shares one fetch. The empty baseline puts all current jobs in added. Expected output: job rows with descriptionText, and CHANGES with added. Limit or cost note: next time, replace the empty object with the whole saved SNAPSHOT and keep the same settings.

Remote engineering jobs posted this week

{"companies": ["channable"], "keywords": ["engineer", "developer"], "remoteOnly": true, "postedWithinDays": 7}

Expected behavior: reads the whole board and keeps only remote jobs with a matching title posted in the last 7 days. Zero matches is a normal complete result. Expected output: only matching job rows. Limit or cost note: you pay for matching rows only; a run with no matches pays only the start event.

๐Ÿ‘‰ Try it now: open the input form

Output

Output fields

Each Dataset row has all 20 keys. A missing optional value is null; the key stays in the row.

FieldMeaningTypeCan be empty?Example / enumSource / notes
_typeRow typestringnojobFixed
_schemaVersionJob-row format versionstringno1.0Fixed
_sourceData sourcestringnorecruiteeFixed
companyCompany slugstringnochannableNormalized input
jobIdJob IDstringno2751915Source ID, or the canonical job URL when the ID is absent. With company it is the job key
titleJob titlestringnoCustomer Success Manager BeneluxRequired source field
departmentDepartmentstring or nullyesCustomer SuccessSource
teamTeamstring or nullyesnullSource; not copied from department
locationPrimary locationstringnoUtrecht, Utrecht, NetherlandsRequired source field
allLocationsAll locationsarray of stringscan be []["Utrecht, Utrecht, Netherlands"]Distinct, in source order
workplaceTypeWork stylestringnoremote, hybrid, on-siteFrom source flags; remote wins over hybrid
commitmentEmployment typestringnoFull-time, Part-time, Contract, Freelance, Internship, TemporaryUnknown codes are reported as schema drift
countryCountrystringnoNLTwo-letter code when the source gives one, otherwise source country text
urlJob pagestringnohttps://jobs.channable.com/o/...Public URL; can be a custom careers domain
applyUrlApplication pagestringnohttps://jobs.channable.com/o/.../c/newThe Actor does not apply
postedAtPublished atstringno2026-09-18T13:27:28.000ZUTC ISO time
updatedAtUpdated atstringno2026-10-01T14:29:22.000ZUTC ISO time
salaryPublished salaryobject or nullyes{"min":3750,"max":5250,"period":"month","currency":"EUR"}Source only: no estimates or conversion. All four keys present when not null; each can be null
descriptionTextDescription and requirementsstring or nullyesnullPlain text when includeDescription is on
_scrapedAtCollected atstringno2026-10-01T18:38:15.792ZUTC ISO; ignored by the comparison

Required fields are never filled with invented values. A bad source row is skipped and makes its board incomplete.

Output entities and surfaces

SituationDataset/API/KVS/live viewResult shapeUser action
Normal itemDataset, Jobs view; SNAPSHOTOne job row per jobOpen, export or use url and title
Domain-empty resultEmpty Dataset; RUN_SUMMARY outcome domain_emptyNo rowsThe board has no published jobs now; check later
Partial resultDataset rows; outcome partial or parser_schema_driftValid rows only, removedSuppressed: trueRead boardSummaries before trusting removals
Technical failure or retryRUN_SUMMARY, OUTPUT.errorError code and request attemptsRetry later with fewer boards; report the run ID

Storage records:

Record or fieldMeaning
SNAPSHOT.rowsCurrent job rows in the exact shape you can send back as previousSnapshot. A partial snapshot stays partial; keep its summary with it.
CHANGESOnly in changes mode. Same object as OUTPUT.diff.
diff.addedCurrent rows whose company and job ID were absent before.
diff.updatedbefore and after rows for a changed job.
diff.removedEarlier rows absent now. Reported only when coverage is complete.
diff.removedSuppressed, diff.suppressionReasons[]Whether removals were held back, and why (company, outcome, reason).
RUN_SUMMARYCounts, per-company outcomes, request attempts, timings and storage IDs. Also embedded in OUTPUT.
OUTPUTItems, summaries, diff, references and final outcome. Written last, so its final presence marks completed storage.

RUN_SUMMARY main fields: received, valid, duplicates, processed, results, domain_empty, not_found, technical_failures, parser_schema_drift, unprocessed, retries, rate_limits, transport_attempts, timings, transportMode (direct_public_https), sourceExhausted, removedSuppressed, failedInputReferences[], inputOutcomes[], itemsWritten, boardSummaries[], transportAttempts[], terminalOutcome and exitCode.

Each boardSummaries[] object has company, inputIndexes, outcome (complete, partial, not_found, domain_empty, technical_failure, parser_schema_drift, duplicate_or_conflict, invalid_input, skipped), completeness (complete, partial, unknown), jobCount, errorCode, errorMessage, retryCount, rateLimitCount, sourceExhausted and removedSuppressed.

Each transportAttempts[] object has attempt, status, classification (SUCCESS, TRANSIENT, RATE_LIMITED, TIMEOUT, CONNECTION_RESET, SOURCE_ACCESS, REDIRECT, BODY_LIMIT, CANCELLED), retryScheduled, retryAfterMs and durationMs.

The final terminalOutcome is complete, partial, not_found, domain_empty, invalid_input, resource_limit, cancelled or technical_failure. Exit code is 0, 1 or 2. Error codes: INVALID_INPUT, SOURCE_ACCESS, RATE_LIMITED, TIMEOUT, MALFORMED_RESPONSE, PARSE_OR_NORMALIZATION, RESOURCE_LIMIT, INTERNAL, AUTH_REQUIRED, UNEXPECTED_REDIRECT, RESPONSE_TOO_LARGE, CANCELLED, MAX_JOBS_LIMIT, SCHEMA_DRIFT, DUPLICATE_ID.

Output example

One real Dataset row from the first input example, collected on 1 October 2026 with descriptions off. It is the full row. The listing can change after collection.

{
"_type": "job",
"_schemaVersion": "1.0",
"_source": "recruitee",
"company": "channable",
"jobId": "2751915",
"title": "Customer Success Manager Benelux - Dutch speaking",
"department": "Customer Success",
"team": null,
"location": "Utrecht, Utrecht, Netherlands",
"allLocations": ["Utrecht, Utrecht, Netherlands"],
"workplaceType": "hybrid",
"commitment": "Full-time",
"country": "NL",
"url": "https://jobs.channable.com/o/customer-success-manager-benelux-dutch-speaking-3",
"applyUrl": "https://jobs.channable.com/o/customer-success-manager-benelux-dutch-speaking-3/c/new",
"postedAt": "2026-09-18T13:27:28.000Z",
"updatedAt": "2026-10-01T14:29:22.000Z",
"salary": {"min": 3750, "max": 5250, "period": "month", "currency": "EUR"},
"descriptionText": null,
"_scrapedAt": "2026-10-01T18:38:15.792Z"
}

team: null means the source has no team for this job. descriptionText: null means descriptions were off. A null salary means no published salary, not zero pay. Some boards publish {"min": 0, "max": 0, ...} on an open application row; that is what the source shows, not a real salary range.

Use case โ†’ fields

Buyer jobInput pathOutput entityKey fieldsNext integration
Track open jobs at known employerscompaniesJob rowcompany, jobId, title, url, applyUrlExport to CSV or a spreadsheet
Find new and changed postingsmode: "changes" + previousSnapshotCHANGES recordadded, updated, removed, removedSuppressedYour own alert or workflow step
Compare published paycompaniesJob rowsalary.min, salary.max, salary.period, salary.currencySpreadsheet or BI tool
Scrape remote jobs or jobs in one countrylocations, remoteOnlyJob rowallLocations, country, workplaceTypeSpreadsheet or job board feed
Monitor new engineering or sales openingskeywords, excludeKeywords, departments, postedWithinDays, mode: "changes"Job row and CHANGEStitle, postedAt, addedYour own alert or workflow step
Read job texts in another toolincludeDescription: trueJob rowdescriptionTextText analysis or LLM step
Check what went wronganyRUN_SUMMARYboardSummaries, inputOutcomes, transportAttemptsSupport request with run ID

๐Ÿ‘‰ Try it now: open the input form

Pricing

Pricing unit

You pay per event. There are two events:

  • Actor start โ€” USD 0.019 per GB of run memory, at least one event. The default 256 MB run counts as one start event. The start fee scales with memory: a 1 GB run still counts one event, a 2 GB run counts two.
  • Job row โ€” one charge per job row written to the Dataset. Price by Apify plan: Free USD 0.00045, Bronze USD 0.000405, Silver USD 0.00036, Gold USD 0.000315.

Platform usage is included: the developer pays it, not you. Summaries, snapshots and CHANGES are not charged. A run that returns zero jobs (empty board, missing board, invalid company) pays only the start event. In changes mode you pay for the current job rows, even when nothing changed. A partial or failed run pays the start event and the rows it actually wrote.

Before fetching, the Actor checks that your run cost limit can cover the full requested cap for every unique company. If it cannot, the run ends with RESOURCE_LIMIT, writes no rows and pays only the start event. Raise the limit or lower the cap.

Cost examples

Free-plan prices at the default 256 MB.

ScenarioInput scopeExpected item/event countBase chargeOptional chargeStop/cap behavior
Empty or missing board1 company0 rowsUSD 0.019noneOutcome domain_empty or not_found
Small first run1 company, cap 1010 rowsUSD 0.019USD 0.0045 (total 0.0235)Cap 10 rows
Prefill runchannable, default cap 2514 rows on 2026-10-26USD 0.019USD 0.0063 (total 0.0253)Board fits the cap
Full board1 company, cap 25up to 25 rowsUSD 0.019up to USD 0.01125Cap 25 rows
Four boards, default cap4 companies, cap 25up to 100 rowsUSD 0.019up to USD 0.045 (total 0.064)Needs a run cost limit of at least USD 0.065
Largest run4 companies, cap 100up to 400 rowsUSD 0.019up to USD 0.18 (total 0.199)Needs a run cost limit of at least USD 0.20
Filtered runany, with filtersmatching rows onlyUSD 0.019USD 0.00045 per matching rowNon-matching jobs are not charged

๐Ÿ‘‰ Try it now: open the input form

Limits

  • Only public Recruitee boards on <company>.recruitee.com. Custom careers domains are not accepted as input; use the Recruitee slug.
  • Up to 4 input entries and 100 jobs per company (default 25), so at most 400 rows per run. Split longer lists into several runs. A live check in October 2026 returned 63 rows from four boards; the largest of them had 48 jobs. A local test covers 400 rows from four 500-job boards, not a live board that large.
  • Recruitee's documentation says this feed will require an authorization token from 10 February 2027. If a board starts asking for one, that company gets AUTH_REQUIRED in RUN_SUMMARY and no rows.
  • The feed response is limited to 16 MiB per company, about 500 jobs with long descriptions; a larger board gets RESPONSE_TOO_LARGE. A previousSnapshot must fit the 256 KiB input limit, about 350 rows without descriptionText. Description and requirements text is limited to 100,000 bytes per job. Descriptions come from the same feed; job pages are not crawled.
  • No company discovery, search across all Recruitee employers, salary filters, history, schedules or notifications inside the Actor. Filters apply only to the boards you name.
  • No login, proxy or bypass of access controls. Redirects to another host, private addresses and login challenges are rejected.
  • A forced stop, storage failure or platform restart can interrupt saving. There is no exactly-once guarantee or resumable queue; check the final run and OUTPUT.

๐Ÿ‘‰ Try it now: open the input form

API, export and integrations

  • API: start a run with POST https://api.apify.com/v2/acts/cliqtomedia~recruitee-jobs-monitor-scraper/runs and the same input JSON. When the run finishes, read /v2/datasets/{defaultDatasetId}/items?format=json and the RUN_SUMMARY record. See the API run reference.
  • Export: in the Dataset choose Export and JSON, CSV or XLSX. Keep JSON for snapshots: CSV and XLSX turn nested fields into cells. See the Dataset guide.
  • Scheduling: an Apify schedule can repeat snapshot runs. A schedule with fixed input does not update previousSnapshot; your own workflow must read the last complete SNAPSHOT and pass it to the next run.
  • Webhooks / no-code: Apify integrations and webhooks can pass the Dataset to your tools. The Actor itself creates no schedules, webhooks or notifications.

Example API call. Keep your token in the environment, never in the URL:

curl -X POST "https://api.apify.com/v2/acts/cliqtomedia~recruitee-jobs-monitor-scraper/runs?memory=256&maxTotalChargeUsd=0.10" \
-H "Authorization: Bearer $APIFY_TOKEN" \
-H 'Content-Type: application/json' \
--data '{"companies":["channable"],"maxJobsPerCompany":10}'

The response gives a run id. Poll /v2/actor-runs/{id} until the status is final, then read the Dataset. The start response is not the finished output.

Use with AI agents (MCP)

  • MCP server with only this Actor: https://mcp.apify.com?tools=cliqtomedia/recruitee-jobs-monitor-scraper. See Apify MCP.
  • Smallest useful input: {"companies": ["channable"]}.
  • Key output fields: title (job title), location and workplaceType (where and how), url (job page), salary (published pay or null). RUN_SUMMARY.boardSummaries[].outcome says whether each company was read completely.
  • A one-company run with 10 rows finished in about 4 seconds and cost USD 0.0235 on the Free plan.
  • Optional filters: keywords (title words), excludeKeywords, departments, locations, remoteOnly, postedWithinDays.
  • Limits: 1โ€“4 companies per run, at most 100 jobs each (default 25), Recruitee slugs only. The Actor has no company search: the agent must already know the company.

๐Ÿ‘‰ Try it now: open the input form

Troubleshooting

Input rejected before the run starts

Symptom: the run does not start or ends with INVALID_INPUT. Likely reason: no companies, more than four entries, a cap outside 1โ€“100, a filter list longer than 20 words, postedWithinDays outside 1โ€“365, a custom domain or unsafe URL, or a malformed previousSnapshot. Check: the run status message and OUTPUT.error give the error code and reason. Action: use a Recruitee slug and the whole saved SNAPSHOT record, then run a small snapshot.

Zero jobs

Symptom: empty Dataset, outcome domain_empty or not_found. Likely reason: the board has no published jobs, or the slug does not exist on Recruitee. Check: open https://<company>.recruitee.com in a browser. Action: correct the slug or check later. An empty board is not a source error.

Fewer jobs than expected or MAX_JOBS_LIMIT

Symptom: outcome partial. Likely reason: the board has more jobs than maxJobsPerCompany. Check: boardSummaries[].jobCount and errorCode. Action: raise the cap up to 100. If more than 100 jobs match, removals stay suppressed.

Zero jobs with filters

Symptom: outcome complete but no rows. Likely reason: no job on the board matches every filter you set. Check: run once without filters and look at title, department, location, country and workplaceType. Action: terms match the start of a word, so use word starts (engineer, not gineer), the source's spelling of the place, or fewer filters. The run status message also says when filters removed every job.

RESOURCE_LIMIT

Symptom: the run ends before fetching, with no rows. Likely reason: the run cost limit cannot cover the requested cap. Check: the status message and OUTPUT.error. Action: raise the run cost limit or lower the cap or the number of companies.

SCHEMA_DRIFT, RATE_LIMITED, TIMEOUT or SOURCE_ACCESS

Symptom: a board ends with parser_schema_drift or technical_failure. Likely reason: the source changed a required value, limited requests or did not respond. Check: transportAttempts[] and the error code. Action: try later with fewer boards. If it repeats, report the run ID and error code.

No removals although jobs disappeared

Symptom: removed is empty and removedSuppressed is true. Likely reason: at least one board was incomplete, so removals would be unsafe. Check: suppressionReasons[]. Action: fix the incomplete board and compare again with the same settings.

๐Ÿ‘‰ Try it now: open the input form

FAQ

Do I need a Recruitee account or API key?

No. The Actor reads the public job feed that each company publishes. You need only the company's Recruitee slug.

Does the Actor remember my last run?

No. Every run saves a fresh SNAPSHOT. To see changes, send that snapshot back as previousSnapshot with mode: "changes".

Does a run with zero jobs cost anything?

It pays the start event only (USD 0.019 at 256 MB). Job-row charges apply only to rows written.

Why is removed empty?

Removals are reported only when all boards were read completely. Check removedSuppressed and its reasons.

How fresh is the data?

Each run reads the live feed at run time. postedAt and updatedAt come from the source; _scrapedAt is the collection time.

Can I export to Excel?

Yes. Choose XLSX in Dataset Export. Keep JSON when you need the exact snapshot shape.

๐Ÿ‘‰ Try it now: open the input form

๐Ÿ‘‰ Try it now: open the input form

Support

For a bug, question or feature request, open the Actor's Issues tab on Apify. Include the run ID, the company slug, the error code and what you expected. Never send your API token, cookies, applicant data or a full private payload.

Job data belongs to its publishers. Check your use of public data and keep private information out of shared exports.

๐Ÿ‘‰ Try it now: open the input form