🧑‍💻 Comeet Job Feed — Any Employer Board

One structured job_record per public job posting on a Comeet employer board. You supply a tenant (or a list of tenants); the actor pulls that employer's current public postings from comeet.com/jobs/{name}/{code}. Public, logged-out, robots-honoured.

Difference: each record carries the posting title, department, structured city/state/country (and remote flag), and employment type from the board's embedded COMPANY_POSITIONS_DATA JSON.

Output is one job_record row per result; billing is pay-per-event, the value event being one job record (a $0.02 start fee per run, then $0.05 per job record).

No login, no API key and no CAPTCHA solving are involved: the source is read logged-out with an identified contact User-Agent.

📊 Sample Output

Real rows from run B5JMpCTB30pafLjfX on build 0.1.10 (2026-09-17), the same input as the Quick start below — every value is as the source published it (emails masked, long text shortened):

tenant	company_name	source_job_id	title	employment_type	posted_at
tripleten	TripleTen	AC.F50	Account Executive EU (B2B)	Full-time	2026-09-14T10:31:57Z
tripleten	TripleTen	AC.F50-43.50C	Account Executive EU (B2B)	Full-time	2026-09-14T10:31:57Z
tripleten	TripleTen	AC.F50-30.40C	Account Executive EU (B2B)	Full-time	2026-09-14T10:31:57Z
tripleten	TripleTen	AC.F50-3F.60E	Account Executive EU (B2B)	Full-time	2026-09-14T10:31:57Z
tripleten	TripleTen	AC.F50-DA.40D	Account Executive EU (B2B)	Full-time	2026-09-14T10:31:57Z
tripleten	TripleTen	AC.F50-3F.60F	Account Executive EU (B2B)	Full-time	2026-09-14T10:31:57Z
tripleten	TripleTen	AC.F50-4F.600	Account Executive EU (B2B)	Full-time	2026-09-14T10:31:57Z
tripleten	TripleTen	AC.F50-DA.40E	Account Executive EU (B2B)	Full-time	2026-09-14T10:31:57Z

The run finished with the status message: CAPPED: delivered 20 of at least 351 unique postings (maxRecords=20). job_record billable=20 [requested_cap=20, delivered=20]

✅ What you get

Each row is flat JSON with these fields (from the dataset schema and the sample run; a field the source does not publish for a given row is null):

• tenant (string/null) — e.g. tripleten
• company_name (string/null) — e.g. TripleTen
• source_platform (string/null) — e.g. comeet
• source_job_id (string/null) — e.g. AC.F50
• title (string/null) — e.g. Account Executive EU (B2B)
• department (string/null) — e.g. Sales
• location (string/null) — e.g. Poland
• city (string/null) — e.g. Warszawa
• state (string/null) — e.g. Województwo mazowieckie
• country (string/null) — e.g. PL
• is_remote (boolean/null) — e.g. True
• employment_type (string/null) — e.g. Full-time
• url (string/null) — e.g. https://www.comeet.com/jobs/tripleten/98.008/account-executive-eu-b2b/AC.F50
• posted_at (string/null) — e.g. 2026-09-14T10:31:57Z
• source_url (string/null) — e.g. https://www.comeet.com/jobs/tripleten/98.008
• record_type (string) — e.g. job_record
• source (string/null) — e.g. comeet-job-feed
• observed_at (string/null) — e.g. 2026-09-17T17:04:43Z
• terminal (string/null) — null in every sample row
• platform (string/null) — null in every sample row
• tenants_requested (integer/null) — null in every sample row
• tenants_ok (integer/null) — null in every sample row
• tenants_blocked (integer/null) — null in every sample row
• tenants_empty (integer/null) — null in every sample row
• tenants_error (integer/null) — null in every sample row
• raw_seen (integer/null) — null in every sample row
• duplicates (integer/null) — null in every sample row
• unique_found (integer/null) — null in every sample row
• delivered (integer/null) — null in every sample row
• reconcile (array/null) — null in every sample row
• per_tenant (array/null) — null in every sample row

What you get

One job_record per live posting, deduplicated on the source-native job id (scoped per tenant). Fields the board does not publish are honest null. A run_receipt row carries the per-tenant counts and, where the platform reports it, a delivered-vs-total reconciliation.

Every run also writes a RUN_RECEIPT record to its key-value store with the source checks it made and the counts it charged — diagnostics never land in the paid dataset.

⚙️ Sample inputs

1. Quick start — the Store example (this is what the sample above came from)

{
  "tenants": [
    "tripleten/98.008"
  ],
  "maxRecords": 20
}

The sample run charged exactly: 1 × $0.02 apify-actor-start + 20 × $0.05 job_record = $1.02 on the Free tier — every delivered row was billed.

2. A smaller, narrowed run

{
  "tenants": [
    "tripleten/98.008"
  ],
  "maxRecords": 5
}

Caps the run at 5 rows — about $0.27 on the Free tier ($0.02 start + 5 × $0.05).

3. A full-size run

{
  "tenants": [
    "tripleten/98.008"
  ],
  "maxRecords": 5000
}

Up to 5000 rows (the schema default for maxRecords) — about $250.02 on the Free tier ($0.02 start + 5000 × $0.05) if the source has that many.

🧾 JSON sample record

One real record from run B5JMpCTB30pafLjfX, exactly as it lands in the dataset (emails masked, long text shortened):

{
  "tenant": "tripleten",
  "company_name": "TripleTen",
  "source_platform": "comeet",
  "source_job_id": "AC.F50",
  "title": "Account Executive EU (B2B)",
  "department": "Sales",
  "location": "Poland",
  "city": "Warszawa",
  "state": "Województwo mazowieckie",
  "country": "PL",
  "is_remote": true,
  "employment_type": "Full-time",
  "url": "https://www.comeet.com/jobs/tripleten/98.008/account-executive-eu-b2b/AC.F50",
  "posted_at": "2026-09-14T10:31:57Z",
  "source_url": "https://www.comeet.com/jobs/tripleten/98.008",
  "record_type": "job_record",
  "source": "comeet-job-feed",
  "observed_at": "2026-09-17T17:04:43Z"
}

🔧 How it works

Transport. Plain HTTPS from the Apify platform, no proxy. robots.txt is read first and a disallowed path is never fetched. Every request carries an identified contact User-Agent.

Terminal states. A run ends NORMAL, CAPPED (your cap was reached), PARTIAL (something was withheld and the message says what), GENUINE_EMPTY (the source was read and truly had nothing in scope) or BLOCKED (the source refused or changed shape — the run FAILS loud and bills nothing). A zero-row run is never reported as a silent success.

Charging. Each job record is charged at the moment it is pushed (job_record); a row that fails to charge is not delivered, so the dataset count always equals the charged count.

How it behaves

Each tenant board is fetched only if its robots allows. A blocked or errored board bills nothing; if every requested board is blocked the run fails loudly. Reachable boards with zero openings are an honest empty (charged nothing). maxRecords caps the count.

What is not done. No login, no cookie or CAPTCHA bypass, no private or personal-account data, no browser automation.

⏰ Set it on a schedule

A single run is a snapshot. The value is the feed: open the actor in Apify Console → Schedules → Create new, add this actor with the input you want, and pick a cadence:

• Daily — 0 7 * * * (07:00 UTC): catch changes within a day.
• Weekly — 0 7 * * 1: a Monday digest.

Each run is independent; keep the same input on the schedule so the results stay comparable. Schedules can also POST results to a webhook (Console → Integrations).

💰 Pricing example

Event	Free	Bronze	Silver	Gold
Actor Start (apify-actor-start)	$0.02	$0.02	$0.02	$0.02
Job Record (job_record)	$0.05	$0.04	$0.04	$0.03

Worked at the live Free-tier price:

• 8 job records: $0.02 start + 8 × $0.05 = $0.42
• 25 job records: $0.02 start + 25 × $0.05 = $1.27
• 5000 job records: $0.02 start + 5000 × $0.05 = $250.02

A run that delivers zero rows charges the $0.02 start fee only. A BLOCKED run (source refused) fails loud and charges no value event. The start fee is charged once per GB of run memory; the default run memory is 1024 MB.

Yield on the sample run: CAPPED: delivered 20 of at least 351 unique postings (maxRecords=20). job_record billable=20 [requested_cap=20, delivered=20]. maxRecords is a hard ceiling on what is delivered and billed, never a target.

⚖️ Legal & ToS

This actor reads public data only. It collects only what the source publishes to any visitor, keeps to the source's robots rules (checked on every run), identifies itself with a contact User-Agent, and does not access accounts, private data or anything behind authentication. Use the output in line with the source's terms and your local law; the intended use is B2B research and monitoring.

❓ FAQ

Q: Do I need an API key or a login?
A: No. the input schema has no key field and the actor carries no secrets.

Q: Why did my run return 0 rows?
A: Read the run's status message. GENUINE_EMPTY means the source was read and had nothing in scope for your input; BLOCKED means the source refused and the run failed without billing a value event — retry later or narrow the input. A zero-row run bills the start fee only.

Q: How many rows can one run return?
A: Up to maxRecords (default 5000). Raise the cap for a bigger run; you pay per delivered row.

Q: How fresh is the data?
A: Every run reads the source live at run time; nothing is cached between runs. Put it on a schedule for a continuous feed.

Q: What formats can I export?
A: The dataset downloads as JSON, CSV, Excel, XML or RSS from the run's Dataset tab or the Apify API, and any run can push to a webhook or integration.

Q: How is this different from the other ATS job feeds actors?
A: Same output shape and billing model; this one covers Comeet Job Feed — Any Employer Board. The siblings under Related Actors cover the other sources or slices — run several on one schedule for a combined feed.

Q: Are there rate limits?
A: The actor paces itself against the source and honours its robots rules; there is no per-buyer limit beyond your Apify plan's concurrency.

🆘 Troubleshooting

• Run FAILED with BLOCKED → the source refused the request or changed its page shape → nothing was billed beyond the start fee; retry after a while, and if it persists open an Issue with the run id.
• Status says CAPPED → your cap (maxRecords) was reached → raise it for a bigger run.
• Input validation error on start → a field is outside the schema's allowed values → start from the Quick start block and change one field at a time.
• Run TIMED-OUT → a very wide request on a slow day → raise the run timeout in Run options or narrow the input; what was delivered before the timeout is still in the dataset.

🔗 Related Actors

• BambooHR Job Feed — Any Employer Board — Scrape jobs from any BambooHR employer careers board. One structured record per public posting — title, department, location, link. No API key; pay p…
• BreezyHR Job Feed — Any Employer Board — Scrape jobs from any BreezyHR employer careers board. One structured record per public posting — title, location, type, link. No API key; pay per job
• CATS ATS Jobs Scraper — One structured jobrecord per record from the official public source, logged-out. Public, robots-honoured
• Flair Hosted Jobs — One structured jobrecord per record from the official public source, logged-out. Public, robots-honoured
• HireBridge Jobs Scraper — One structured jobrecord per LIVE job posting from a public, logged-out ATS board. Public, robots-honoured
• JazzHR Job Feed — Any Employer Board — Scrape jobs from any JazzHR employer careers board. One structured record per public posting — title, location, link. No API key; pay per job
• 🏢 About NexGenData — NexGen Watch is NexGenData's fleet of 256 public monitoring and lookup actors built on official sources, pay-per-result. Browse the catalog at apify.com/nexgenwatch.

⭐ Found this useful?

If this actor saved you a manual check, a quick review on the Apify Store helps other teams find it. Feature request or a source that changed? Open it from the Issues tab — every one is read.