Czech Jobs.cz Postings, Salary & Brigady Finder: MCP config, n8n workflow and API

{
  "mode": "search",
  "searchQueries": [
    "python"
  ],
  "salaryMinCzk": 0,
  "hourlyRateMin": "any",
  "datePosted": "any",
  "education": "any",
  "homeOffice": "any",
  "suitableFor": "any",
  "employerType": "any",
  "includeDetails": true,
  "maxItems": 3
}

---
name: czech-jobs-cz-postings-salary-and-brigady-finder
description: "Jobs.cz listings with salary (visible and hidden structured ranges), descriptions, benefits, education, languages, contract, dates, remote type, categories, logo, Atmoskop and public contact details. Runs the Apify Actor xyrelith-data/czech-jobs-cz-postings-salary-and-brigady-finder. Use when the user needs Czech Jobs.cz Postings data with fields such as title, company, location, salaryText, employmentTypes, postedDate and an Apify token is available."
compatibility: "Needs network access, curl, and an APIFY_TOKEN environment variable. Runs are billed to the token owner's Apify account."
metadata:
  actor: "xyrelith-data/czech-jobs-cz-postings-salary-and-brigady-finder"
  store-url: "https://apify.com/xyrelith-data/czech-jobs-cz-postings-salary-and-brigady-finder"
---

# Czech Jobs.cz Postings, Salary & Brigady Finder

Use this skill to fetch Czech Jobs.cz Postings data with the Apify Actor `xyrelith-data/czech-jobs-cz-postings-salary-and-brigady-finder` and work with the returned rows.

## Before running

1. Check that `APIFY_TOKEN` is set in the environment. Never print it or write it to a file.
2. Build `input.json` from the user's request using the fields below. Keep limits small for a first run.
3. Confirm the search terms or URLs with the user if the request is ambiguous.

## Input fields

| Field | Type | Meaning |
| --- | --- | --- |
| `mode` | one of `search`, `byLocation`, `byCategory`, `brigady`, `byUrls`, required | What to fetch. Search by keyword, browse a city/region, browse a profession, browse the separate part-time brigady board, or scrape specific jobs.cz search and job URLs. |
| `searchQueries` | array | One or more free-text keywords, e.g. `python`, `účetní`, `řidič`. Each query is paginated and results are de-duplicated. The old `searchQuery` key is still accepted for saved tasks. |
| `startUrls` | array | jobs.cz search pages, job detail pages, brigady pages, or employer-branded job URLs. Job URLs return full detail when the page publishes it; employer pages return title, company and URL. |
| `location` | string | Curated city/region. Required for mode=byLocation; narrows keyword and category searches; limits brigady to a 10-50 km radius. Pick `(none)` for no restriction. |
| `category` | string | Curated profession/category. Required for mode=byCategory; narrows a city browse. Pick `(none)` for no restriction. Not applied in mode=brigady. |
| `salaryMinCzk` | integer | Only return main-board jobs at or above this gross monthly salary in Czech crowns. jobs.cz filters on each ad's internal salary data, so non-disclosing ads are not excluded and can still match. Ignored in mode=brigady. |
| `hourlyRateMin` | one of `any`, `100`, `200`, `300`, `400`, `500` | Only return brigady gigs at or above this hourly rate. jobs.cz offers exactly these five fixed thresholds. Ignored in every other mode; use `salaryMinCzk` there. |
| `radiusKm` | one of `0`, `10`, `20`, `30`, `40`, `50` | Widen or narrow the distance match around a location. Has no effect without a location. The current jobs.cz search app ignores radius, so these runs use the legacy jobs.cz pages. |
| `datePosted` | one of `any`, `24h`, `3d`, `7d` | Restrict results to jobs posted or updated within this window. Works in every mode, including brigady. |
| `employmentTypes` | array | Full-time, part-time, internship/trainee or temporary work. Leave empty for any. Ignored in mode=brigady. |
| `contractTypes` | array | Type of legal working relationship. Leave empty for any. Ignored in mode=brigady. |
| `education` | one of `any`, `primary`, `high`, `uni` | Required education level. Ignored in mode=brigady. |
| `languageSkills` | array | Only return jobs requiring these languages. Leave empty for any. Ignored in mode=brigady. |
| `homeOffice` | one of `any`, `partial-work-from-home`, `work-mostly-from-home`, `flexible-hours` | Remote-work arrangement. `Flexible hours` is only available on legacy jobs.cz pages, so selecting it switches the run to those pages. Ignored in mode=brigady. |

Example `input.json` (the Actor's published prefill):

```json
{
  "mode": "search",
  "searchQueries": [
    "python"
  ],
  "salaryMinCzk": 0,
  "hourlyRateMin": "any",
  "datePosted": "any",
  "education": "any",
  "homeOffice": "any",
  "suitableFor": "any",
  "employerType": "any",
  "includeDetails": true,
  "maxItems": 3
}
```

## Run

```bash
curl -sS -X POST "https://api.apify.com/v2/acts/xyrelith-data~czech-jobs-cz-postings-salary-and-brigady-finder/run-sync-get-dataset-items" \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d @input.json > results.json
```

The call waits for the run to finish and returns the dataset items as a JSON array. If the run needs more than 300 seconds the API answers with HTTP 408; then start the run with `POST /v2/acts/xyrelith-data~czech-jobs-cz-postings-salary-and-brigady-finder/runs`, poll `GET /v2/actor-runs/{runId}` until `SUCCEEDED`, and read `GET /v2/datasets/{defaultDatasetId}/items`.

## Output

Each item is one record. Published fields include: `title`, `company`, `location`, `salaryText`, `employmentTypes`, `postedDate`, `url`, `salary`, `contractType`, `education`, `languages`, `workLocationType`, `validThrough`, `description`.

Summarise what was found, cite the record URLs when present, and say how many items came back. Do not invent values for empty fields.