Jobs.ch Swiss Job Listings by Region & Industry: MCP config, n8n workflow and API

jobs.ch job records with listings, descriptions, salary estimates, apply links, contacts, languages, categories, regions and company profiles.

Fastest route, in Claude Code:

claude mcp add --transport http jobs-ch-swiss-job-listings-by-region-and-industry "https://mcp.apify.com/?tools=fetch-actor-details,vexaloom-labs/jobs-ch-swiss-job-listings-by-region-and-industry"

One click, signs in with Apify on first use:

Any other client, one command (writes the config for 25+ agents, including Windsurf, Zed, Cline and Goose):

npx add-mcp "https://mcp.apify.com/?tools=fetch-actor-details,vexaloom-labs/jobs-ch-swiss-job-listings-by-region-and-industry" --name jobs-ch-swiss-job-listings-by-region-and-industry

Every file on this page is generated from the Actor's published schema: 51 of 51 checks pass (validated, not run)
  • MCP configs: 7 of 7 (Uses Apify's hosted MCP endpoint over HTTPS; The tools parameter lists exactly the chosen Actors as owner/name; JSON configs parse and use the client's top-level key and the same URL; Codex TOML has a [mcp_servers.<name>] table with url and bearer_token_env_var; CLI commands quote the same URL and use the streamable HTTP transport; One-click install links decode back to the same URL and carry no token; Only placeholders, no real token)
  • n8n workflow: 11 of 11 (It has a nodes array and a connections object; Every node has a name, type, typeVersion, position and parameters; Node names are unique; Every node type is a known n8n core node (or the Apify node); Every node uses a typeVersion that n8n ships; Every connection points at an existing node; At least one trigger starts the workflow; Every working node is reachable from a trigger; Apify calls use POST and a credential for the token; Actor input matches the Actor's published input schema; No token or credential value is embedded)
  • long-run workflow: 11 of 11 (It has a nodes array and a connections object; Every node has a name, type, typeVersion, position and parameters; Node names are unique; Every node type is a known n8n core node (or the Apify node); Every node uses a typeVersion that n8n ships; Every connection points at an existing node; At least one trigger starts the workflow; Every working node is reachable from a trigger; Apify calls use POST and a credential for the token; Actor input matches the Actor's published input schema; No token or credential value is embedded)
  • example input: 5 of 5 (All 1 required input field is present; Every input key exists in the published input schema; Every value has the type the schema declares; Every choice field uses one of its published options; Numbers respect the published minimum and maximum)
  • code snippets: 4 of 4 (curl calls the documented run-sync-get-dataset-items endpoint for this Actor; Python (apify-client 3.x typed Run) and JavaScript use the official apify-client call() then read the run's dataset; Multi-line shell commands continue every line with a backslash; Token read from APIFY_TOKEN, none embedded)
  • SKILL.md: 13 of 13 (SKILL.md starts with YAML front matter; name is 1-64 lowercase letters, digits and single hyphens; name matches the skill folder name; description is present, at most 1024 characters and has no angle brackets; front matter uses only spec fields; compatibility is at most 500 characters; body has instructions; field descriptions end on whole sentences; no credential values are embedded; the token is read from APIFY_TOKEN; the run command calls this Actor's run-sync endpoint; the example input is valid JSON; the example input matches the published input schema)

What the checks cover

What a run costs

Every run pays a start fee plus a price per result. On the Free plan this Actor's start fee is $0.40 (the start event, $0.10 per GB, times its default 4 GB of memory), $0.12 on Business; results cost $0.99 per 1,000 results (pay per event). Checked 2026-11-12.

Results in one runStartResultsRun total
10$0.40$0.010$0.41
100$0.40$0.10$0.50
1,000$0.40$0.99$1.39

Plus Apify platform usage for the run, which the caller pays. A smaller memory setting lowers the start fee if the Actor still finishes. Prices can change; the Store pricing tab is the source of truth.

MCP config

One URL works in every client: https://mcp.apify.com/?tools=fetch-actor-details,vexaloom-labs/jobs-ch-swiss-job-listings-by-region-and-industry. It exposes this Actor as a tool, plus fetch-actor-details so the agent can read the input schema before calling it. Pick your client:

Claude Code configterminal or .mcp.json

claude mcp add --transport http jobs-ch-swiss-job-listings-by-region-and-industry "https://mcp.apify.com/?tools=fetch-actor-details,vexaloom-labs/jobs-ch-swiss-job-listings-by-region-and-industry"

Run the command in your project folder. Add --scope user to make it available in every project. Full Claude Code setup

Tools your agent gets

Listed by Apify's MCP server 0.21.5 for this exact URL on 2026-11-11 (a tools/list call; nothing was run).

  • fetch-actor-detailsreads the input schema
  • get-actor-runchecks a run's status
  • get-dataset-itemsreads a run's results
  • get-key-value-store-recordreads a stored record such as a file or summary
  • abort-actor-runstops a run that is still going
  • vexaloom-labs--jobs-ch-swiss-job-listings-by-region-and-industryruns the Actor and returns its results

n8n workflow

A manual and a daily trigger call the Actor through the HTTP Request node with your Apify token, then hand each record to the destination you pick. The Actor input sits in the request body, already filled with the example below.

Send the records to
  • Run by hand
  • Every day
  • Run Apify Actor

n8n workflowjobs-ch-swiss-job-listings-by-region-and-industry.n8n.json

Actor on Apify
{
  "name": "Jobs.ch Swiss Job Listings by Region & Industry to n8n only",
  "nodes": [
    {
      "id": "af5a261e-722e-4d4b-ad54-313aecba790b",
      "name": "Run by hand",
      "type": "n8n-nodes-base.manualTrigger",
      "typeVersion": 1,
      "position": [
        0,
        0
      ],
      "parameters": {}
    },
    {
      "id": "a385bce6-b8c4-4601-a2d0-71d4a21f0853",
      "name": "Every day",
      "type": "n8n-nodes-base.scheduleTrigger",
      "typeVersion": 1.2,
      "position": [
        0,
        200
      ],
      "parameters": {
        "rule": {
          "interval": [
            {
              "triggerAtHour": 8
            }
          ]
        }
      },
      "notes": "Activate the workflow to run on this schedule."
    },
    {
      "id": "4678dc3a-cd58-4c9e-a671-384b503a7d0f",
      "name": "Run Apify Actor",
      "type": "n8n-nodes-base.httpRequest",
      "typeVersion": 4.2,
      "position": [
        260,
        100
      ],
      "parameters": {
        "method": "POST",
        "url": "https://api.apify.com/v2/actors/vexaloom-labs~jobs-ch-swiss-job-listings-by-region-and-industry/run-sync-get-dataset-items",
        "authentication": "genericCredentialType",
        "genericAuthType": "httpHeaderAuth",
        "sendBody": true,
        "specifyBody": "json",
        "jsonBody": "{\n  \"mode\": \"search\",\n  \"searchMode\": \"classic\",\n  \"searchQueries\": [\n    \"software engineer\"\n  ],\n  \"employmentGradeMin\": 0,\n  \"employmentGradeMax\": 100,\n  \"sortBy\": \"relevance\",\n  \"includeDetails\": false,\n  \"descriptionFormat\": \"text\",\n  \"maxDescriptionLength\": 0,\n  \"maxItems\": 3,\n  \"maxPages\": 1,\n  \"locale\": \"en\",\n  \"incrementalMode\": false\n}",
        "options": {
          "timeout": 310000
        }
      },
      "notes": "Actor: vexaloom-labs/jobs-ch-swiss-job-listings-by-region-and-industry. Select a Header Auth credential: name Authorization, value Bearer + your Apify token. Edit the JSON body to change the input.",
      "notesInFlow": false
    },
    {
      "id": "eea51cd6-2b2c-475d-ac3f-155ceaea8e93",
      "name": "Setup",
      "type": "n8n-nodes-base.stickyNote",
      "typeVersion": 1,
      "position": [
        0,
        -370
      ],
      "parameters": {
        "content": "## Jobs.ch Swiss Job Listings by Region & Industry\n\nSource: [vexaloom-labs/jobs-ch-swiss-job-listings-by-region-and-industry](https://apify.com/vexaloom-labs/jobs-ch-swiss-job-listings-by-region-and-industry) on Apify.\n\n1. In **Run Apify Actor**, create a Header Auth credential: name `Authorization`, value `Bearer YOUR_APIFY_TOKEN` with your token.\n2. Click **Execute workflow**. Each record arrives as one n8n item.\n3. Edit the JSON body of **Run Apify Actor** to change the input.\n\nGenerated by recipeforagents.com. Validated, not executed: runs are billed to your Apify account.",
        "height": 340,
        "width": 460,
        "color": 6
      }
    }
  ],
  "connections": {
    "Run by hand": {
      "main": [
        [
          {
            "node": "Run Apify Actor",
            "type": "main",
            "index": 0
          }
        ]
      ]
    },
    "Every day": {
      "main": [
        [
          {
            "node": "Run Apify Actor",
            "type": "main",
            "index": 0
          }
        ]
      ]
    }
  },
  "pinData": {},
  "active": false,
  "settings": {
    "executionOrder": "v1"
  },
  "meta": {
    "templateCredsSetupCompleted": false
  },
  "tags": []
}

Import with Workflows, Import from file, or paste into the canvas. Credentials are not included: you select them after import.

All 7 destination variants pass the same checks at build time. Built-in nodes only, at versions n8n has shipped since 1.80: they import on n8n Cloud and older self-hosted instances without community nodes. Prefer Apify's own node? The verified community node @apify/n8n-nodes-apify runs the same Actor with OAuth sign-in on n8n Cloud.

Runs longer than 5 minutes? The synchronous endpoint answers HTTP 408 after 300 seconds. The long-run variant starts the run, checks it every minute until it ends, then reads its dataset (HTTP Request, If and Stop and Error nodes only).

Download the long-run workflow11 of 11 checks pass, not executed

Call it from code

Run the Actor from a script or your own agent framework with the Apify API. The call waits for the run to finish and returns the records. The input is the example below.

curl

API docs on Apify
curl -X POST "https://api.apify.com/v2/actors/vexaloom-labs~jobs-ch-swiss-job-listings-by-region-and-industry/run-sync-get-dataset-items" \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"mode":"search","searchMode":"classic","searchQueries":["software engineer"],"employmentGradeMin":0,"employmentGradeMax":100,"sortBy":"relevance","includeDetails":false,"descriptionFormat":"text","maxDescriptionLength":0,"maxItems":3,"maxPages":1,"locale":"en","incrementalMode":false}'

Example input

These values come from the Actor's Store prefill and required defaults. Change the search, URL or limit before your first run.

Actor inputinput.json

{
  "mode": "search",
  "searchMode": "classic",
  "searchQueries": [
    "software engineer"
  ],
  "employmentGradeMin": 0,
  "employmentGradeMax": 100,
  "sortBy": "relevance",
  "includeDetails": false,
  "descriptionFormat": "text",
  "maxDescriptionLength": 0,
  "maxItems": 3,
  "maxPages": 1,
  "locale": "en",
  "incrementalMode": false
}

FieldTypeWhat it does
mode required string (8 options) What to fetch. search runs classic keyword search (or semantic with searchMode=semantic). browse uses filters only. byCompany resolves company names/IDs. byUrls accepts jobs.ch search or job-detail URLs. The…
searchMode string (2 options) classic uses jobs.ch's exact keyword API with all filters and sort. semantic uses the site's fuzzy, cross-language search page (filters still apply; sort is relevance-only).
searchQueries array One or more free-text keywords (mode=search). Multiple queries are run in order and deduplicated by job ID. Leave empty to browse all jobs matching the filters.
companyNames array Company names to resolve against jobs.ch's company directory (mode=byCompany). Exact names are preferred; unmatched names fall back to a keyword search filtered by company name.
companyIds array jobs.ch company IDs (mode=byCompany). IDs are the most reliable company filter and take priority over names.
startUrls array jobs.ch search URLs or job-detail URLs (mode=byUrls). Search URLs carry their own filters; invalid or non-jobs.ch URLs are skipped.
regions array Filter by one or more Swiss canton/language-regions (multi-value OR). Allowed IDs: 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25. Required for mode=byRegion; optional elsewhere.
industries array Filter by one or more employer industries (multi-value OR). Allowed IDs: 1-24. Required for mode=byIndustry; optional elsewhere.
categories array Filter by one or more occupational fields / job functions (multi-value OR). Allowed IDs: 97-261 (165 jobs.ch categories; labels in README). Required for mode=byCategory.
employmentTypes array Filter by one or more contract types (multi-value OR). Allowed IDs: 1 Temporary, 2 Freelance, 3 Internship, 4 Supplementary income, 5 Permanent position, 6 Apprenticeship. Required for mode=byEmploymentType.
positions array Filter by one or more seniority levels (multi-value OR). Allowed IDs: 1 Executive position, 2 Specialist, 3 Employee.
languageSkills array Filter by one or more required working languages (multi-value OR). Allowed values: de, en, fr, it.
companySegments array Filter by employer segment (multi-value OR). Allowed values: gu (large company), kmu (SME), pdl (personnel-service provider).
location string Optional free-text city/place refinement (e.g. Zürich, Geneva, Basel).
employmentGradeMin integer Lower bound of the workload range in percent.
employmentGradeMax integer Upper bound of the workload range in percent.
publishedSince string (5 options) Only jobs first published within this time window.
sortBy string (2 options) Classic search sort order: relevance or newest-first. Semantic search always uses relevance.
includeDetails boolean Fetch each job's detail page for full description, apply URL/method, salary estimate, contacts, languages, categories, regions, deadline, benefits and company profile/ratings. Adds one request per job plus one cached…
descriptionFormat string (3 options) Format of the enriched description: plain text, original HTML, or both.
maxDescriptionLength integer Truncate descriptions to this many characters (0 = no truncation).
maxItems integer Maximum number of jobs to return. jobs.ch serves 20 rows per page and caps each search at 2,000 rows.
maxPages integer Maximum result pages to request per query/filter combination (jobs.ch caps searches at 100 pages).
locale string (3 options) jobs.ch site language for URLs and translated labels.

2 more optional fields on the Store input tab.

What your agent receives

Each run returns a list of records. The Actor publishes 9 fields, starting with title, companyName, location, workloadText.

Field
title
companyName
location
workloadText
contractType
salaryMin
salaryMax
postedDate
jobUrl

Agent skill

A SKILL.md in the open Agent Skills format. It teaches Claude Code, Codex and other skill-aware agents when to call this Actor, how to build the input and how to read the result, using the API directly.

SKILL.mdjobs-ch-swiss-job-listings-by-region-and-industry/SKILL.md

---
name: jobs-ch-swiss-job-listings-by-region-and-industry
description: "jobs.ch job records with listings, descriptions, salary estimates, apply links, contacts, languages, categories, regions and company profiles. Runs the Apify Actor vexaloom-labs/jobs-ch-swiss-job-listings-by-region-and-industry. Use when the user needs Jobs.ch Swiss Job data with fields such as title, companyName, location, workloadText, contractType, salaryMin 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: "vexaloom-labs/jobs-ch-swiss-job-listings-by-region-and-industry"
  store-url: "https://apify.com/vexaloom-labs/jobs-ch-swiss-job-listings-by-region-and-industry"
---

# Jobs.ch Swiss Job Listings by Region & Industry

Use this skill to fetch Jobs.ch Swiss Job data with the Apify Actor `vexaloom-labs/jobs-ch-swiss-job-listings-by-region-and-industry` 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`, `browse`, `byCompany`, `byUrls`, `byRegion`, `byIndustry`, `byEmploymentType`, `byCategory`, required | What to fetch. `search` runs classic keyword search (or semantic with `searchMode=semantic`). `browse` uses filters only. `byCompany` resolves company names/IDs. `byUrls` accepts jobs.ch search or job-detail URLs. |
| `searchMode` | one of `classic`, `semantic` | `classic` uses jobs.ch's exact keyword API with all filters and sort. `semantic` uses the site's fuzzy, cross-language search page (filters still apply; sort is relevance-only). |
| `searchQueries` | array | One or more free-text keywords (mode=search). Multiple queries are run in order and deduplicated by job ID. Leave empty to browse all jobs matching the filters. |
| `companyNames` | array | Company names to resolve against jobs.ch's company directory (mode=byCompany). Exact names are preferred; unmatched names fall back to a keyword search filtered by company name. |
| `companyIds` | array | jobs.ch company IDs (mode=byCompany). IDs are the most reliable company filter and take priority over names. |
| `startUrls` | array | jobs.ch search URLs or job-detail URLs (mode=byUrls). Search URLs carry their own filters; invalid or non-jobs.ch URLs are skipped. |
| `regions` | array | Filter by one or more Swiss canton/language-regions (multi-value OR). Allowed IDs: 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25. Required for mode=byRegion; optional elsewhere. |
| `industries` | array | Filter by one or more employer industries (multi-value OR). Allowed IDs: 1-24. Required for mode=byIndustry; optional elsewhere. |
| `categories` | array | Filter by one or more occupational fields / job functions (multi-value OR). Allowed IDs: 97-261 (165 jobs.ch categories; labels in README). Required for mode=byCategory. |
| `employmentTypes` | array | Filter by one or more contract types (multi-value OR). Allowed IDs: 1 Temporary, 2 Freelance, 3 Internship, 4 Supplementary income, 5 Permanent position, 6 Apprenticeship. Required for mode=byEmploymentType. |
| `positions` | array | Filter by one or more seniority levels (multi-value OR). Allowed IDs: 1 Executive position, 2 Specialist, 3 Employee. |
| `languageSkills` | array | Filter by one or more required working languages (multi-value OR). Allowed values: de, en, fr, it. |
| `companySegments` | array | Filter by employer segment (multi-value OR). Allowed values: gu (large company), kmu (SME), pdl (personnel-service provider). |
| `location` | string | Optional free-text city/place refinement (e.g. Zürich, Geneva, Basel). |

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

```json
{
  "mode": "search",
  "searchMode": "classic",
  "searchQueries": [
    "software engineer"
  ],
  "employmentGradeMin": 0,
  "employmentGradeMax": 100,
  "sortBy": "relevance",
  "includeDetails": false,
  "descriptionFormat": "text",
  "maxDescriptionLength": 0,
  "maxItems": 3,
  "maxPages": 1,
  "locale": "en",
  "incrementalMode": false
}
```

## Run

```bash
curl -sS -X POST "https://api.apify.com/v2/acts/vexaloom-labs~jobs-ch-swiss-job-listings-by-region-and-industry/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/vexaloom-labs~jobs-ch-swiss-job-listings-by-region-and-industry/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`, `companyName`, `location`, `workloadText`, `contractType`, `salaryMin`, `salaryMax`, `postedDate`, `jobUrl`.

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

  • Claude Code: save it as ~/.claude/skills/jobs-ch-swiss-job-listings-by-region-and-industry/SKILL.md, or .claude/skills/jobs-ch-swiss-job-listings-by-region-and-industry/SKILL.md in a project.
  • Codex and other agents: ~/.agents/skills/jobs-ch-swiss-job-listings-by-region-and-industry/SKILL.md, or .agents/skills/jobs-ch-swiss-job-listings-by-region-and-industry/ in a project.
  • Or let the skills CLI place it for your agent: npx skills add https://recipeforagents.com --skill jobs-ch-swiss-job-listings-by-region-and-industry
  • Set APIFY_TOKEN in the agent's environment.

Troubleshooting

Why does the client say Unauthorized or invalid token?

Every Apify Actor tool needs a signed-in Apify account. Reconnect the server so the OAuth sign-in runs again, or switch to the token variant: an Authorization: Bearer header with an API token from Apify Console, Settings, API and integrations. For a local server the token must be in the server's own env block, not only in your shell.

Source: Apify MCP server README

Why did my agent's tool list change after an update?

Without a tools parameter Apify's server loads its default tool set, which changes between releases. The URLs on this site pin the tools with ?tools=, so the agent always gets the same Actor tool plus fetch-actor-details. Apify's README gives the same advice for production.

Source: Apify MCP server README

What happens when the agent sends input the Actor rejects?

The server answers with the Actor's input schema, so the agent can fix the arguments and call again. The fetch-actor-details tool in every scoped URL lets it read that schema before the first call.

Source: Apify MCP server README

Questions

How do I connect Jobs.ch Swiss Job Listings by Region & Industry to Claude?

In Claude Code run: claude mcp add --transport http jobs-ch-swiss-job-listings-by-region-and-industry "https://mcp.apify.com/?tools=fetch-actor-details,vexaloom-labs/jobs-ch-swiss-job-listings-by-region-and-industry". In Claude Desktop or claude.ai add a custom connector with the URL https://mcp.apify.com/?tools=fetch-actor-details,vexaloom-labs/jobs-ch-swiss-job-listings-by-region-and-industry and sign in to Apify. The agent then gets one tool for this Actor plus a tool that reads its input schema.

What input does Jobs.ch Swiss Job Listings by Region & Industry need?

The published input schema requires mode. The example on this page uses the Actor's own Store prefill.

What does Jobs.ch Swiss Job Listings by Region & Industry cost to run?

The Apify Store lists $0.99 per 1,000 results (pay per event) for this Actor, checked 2026-11-12. Runs are billed to the Apify account whose token or sign-in the agent uses; Apify platform usage can add to that.

Which tools does the MCP config give my agent?

6 tools: fetch-actor-details, get-actor-run, get-dataset-items, get-key-value-store-record, abort-actor-run, vexaloom-labs--jobs-ch-swiss-job-listings-by-region-and-industry. Apify's MCP server listed them for this exact URL on 2026-11-11.