# Teamtailor Jobs Scraper — Any Teamtailor Career Site | $1/1K (`steadyrow/teamtailor-jobs`) Actor Scrape every open job from any Teamtailor career site, including ones on a company's own domain: paste the URL or the account name. Official public RSS feed, no proxy. Department, locations, workplace type, filters by keyword and location, and a monitor mode for new jobs. - **URL**: https://apify.com/steadyrow/teamtailor-jobs.md - **Developed by:** [Steadyrow](https://apify.com/steadyrow) (community) - **Categories:** Jobs, Automation - **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks - **User rating**: No ratings yet ## Pricing from $1.00 / 1,000 jobs This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events. Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event ## What's an Apify Actor? An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes. In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours, and optionally produces a well-defined JSON output, datasets with results, or files in key-value store. In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server. Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md. ## How to integrate an Actor? If asked about integration, you help developers integrate Actors into their projects. You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready. Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run. For examples already wired to this Actor's own input schema, see the [API](#api) section below. Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`). # README ## Teamtailor Jobs Scraper — Any Teamtailor Career Site | $1/1K **Paste a Teamtailor career site, get every open job as clean JSON. $1 per 1,000 jobs.** Teamtailor career sites are used by many companies, especially in the Nordics and the rest of Europe — either on `.teamtailor.com` or on the company's own domain (for example `careers.oatly.com`). Every site serves a public RSS feed of its jobs; Teamtailor's help centre describes it as publicly available data. This Actor reads that feed (100 jobs per page, all pages) and returns each job with title, department, role, all locations, workplace type, publish date and the full description. - ✅ **Any Teamtailor career site** — including ones on a **company's own domain** - ✅ **Workplace type** — onsite / hybrid / remote when the company sets it - ✅ **Monitor mode** — schedule it daily and only pay for jobs you have not received before - ✅ **No browser, no proxy, no login** — plain HTTPS requests to the public feed - ✅ **Filters** — keywords, excluded words, location, remote, department, posted within N days - ✅ **No personal data** — no recruiter names or contacts; e-mail addresses inside descriptions are removed > Need Greenhouse, Lever, Ashby, Workday, Personio and more in the same run? Use the combined [ATS Jobs API](https://apify.com/steadyrow/ats-jobs). This Actor is the Teamtailor-only version with inputs built for Teamtailor. ### What can I use it for? - **Nordic and European job boards** — pull the Teamtailor companies you track into one feed - **Job alerts** — daily monitor run → Slack, e-mail or Google Sheets with only the new roles - **Hiring signals for sales and recruiting** — where and in which departments a retailer, gym chain or manufacturer is hiring - **Labour-market research** — roles by country, department and workplace type - **AI agents** — a typed job feed your agent can call through the Apify API or MCP ### Input ```json { "careerSites": [ "https://sats.teamtailor.com/jobs", "https://careers.oatly.com", "teamtailor:polestar" ], "keywords": [ "manager", "coach" ], "excludeKeywords": [ "trainee" ], "locations": [ "Norway", "Sweden" ], "departments": [ "Gym" ], "postedWithinDays": 30, "maxItemsPerSource": 200, "monitorMode": false } ``` | Field | What it does | |---|---| | `careerSites` | **Required.** One per line: a career site URL (`https://sats.teamtailor.com/jobs`, or a custom domain such as `https://careers.oatly.com`), a job URL, the account name (`sats` or `teamtailor:sats`) or `teamtailor:careers.oatly.com` for a custom domain. Entries that belong to another ATS are skipped with a note in the log. | | `keywords` | Keep jobs whose **title** contains any of these words (whole word, case-insensitive). Turn on `searchInDescription` to search the description too. | | `excludeKeywords` | Drop jobs whose title contains any of these words. | | `locations` | Keep jobs whose location or country contains one of these words. `remote` matches remote jobs. | | `departments` | Keep jobs whose department or team contains one of these strings. | | `postedWithinDays` | Only jobs published in the last N days. | | `maxItemsPerSource` / `maxItems` | Limits per site / per run (0 = no limit). | | `includeDescription`, `includeDescriptionHtml` | Plain-text and/or HTML description. | | `monitorMode`, `monitorStateName` | Output only jobs not delivered before; name of the store that remembers them. | #### Finding the career site If the career site is on `.teamtailor.com`, use that or just the name. If it is on the company's own domain, paste the address (for example `https://careers.oatly.com`): the Actor recognises Teamtailor-hosted pages and reads the same `/jobs.rss` feed. If that detection fails, force it with the prefix `teamtailor:careers.example.com`. A site that is not hosted by Teamtailor is not supported. ### Output One item per job: ```json { "job_id": "teamtailor:sats:b1dc029f-54c3-430f-bf6c-c099aa1b9ddb", "ats": "teamtailor", "company": "SATS", "company_board_id": "sats", "title": "Åpen søknad: Salg- og servicemedarbeider til SATS Oslo", "department": "Gym", "team": "Customer Care", "location": "Oslo, Norway", "locations": [ "Oslo, Norway", "Asker, Norway", "Bekkestua, Norway" ], "country": "Norway", "remote": false, "workplace_type": "onsite", "employment_type": null, "posted_at": "2026-10-15T09:43:52.000Z", "updated_at": null, "salary_min": null, "salary_max": null, "salary_currency": null, "salary_period": null, "salary_source": null, "description_text": "🤸🏼‍♀️ Vil du inspirere folk til å bli sunnere og gladere?…", "apply_url": "https://careers.sats.com/jobs/8550814-apen-soknad-salg-og-servicemedarbeider-til-sats-oslo", "source_url": "https://careers.sats.com/jobs/8550814-apen-soknad-salg-og-servicemedarbeider-til-sats-oslo", "input": "https://sats.teamtailor.com/jobs", "scraped_at": "2026-10-20T17:29:58.586Z" } ``` Teamtailor-specific notes: - **`employment_type` is always `null`** — the Teamtailor feed does not publish it. - `job_id` is `teamtailor::` and stays the same between runs. For a custom domain `` is the domain (`careers.oatly.com`). - `department` is the Teamtailor department and `team` its role field; both are `null` when the company leaves them empty. `locations` lists every location of the job; `country` is the country of the first one (the example is truncated to 3 of 13 locations). - `workplace_type` comes from Teamtailor's remote status: `remote`, `hybrid`, `onsite`; it is `null` when the company has not set it (and for the temporary-remote value). `remote` follows it. - `posted_at` is the job's publish date; `updated_at` is always `null`. Teamtailor has no salary field, so `salary_*` is filled only when a range is written in the description. - Jobs are listed in the language the company wrote them in (the example is Norwegian). - A run summary (per site: listed / output / errors) is saved as `SUMMARY` in the default key-value store. An unknown site is reported there and in the log; the other sites still run. ### Monitor mode: only new jobs 1. Turn on **Monitor mode** and save the input as a task. 2. Add a schedule (for example every morning). 3. The first run returns all matching jobs. Every later run returns only jobs not delivered before — and you pay only for those. Delivered IDs are kept per site in the named key-value store `teamtailor-jobs-monitor` (change it with `monitorStateName` if you run several independent monitors). In our tests a second run on the same sites returned 0 jobs, and after forgetting 9 delivered jobs a third run returned exactly those 9. ### Pricing Pay per event: | Event | Price | |---|---| | Job in the dataset | **$0.001** ($1 per 1,000 jobs) | | Actor start | $0.002 per run | Examples: 1,000 jobs ≈ $1. A daily monitor on 20 sites that finds 30 new jobs ≈ $0.03 + $0.002 per day. Jobs removed by your filters or already delivered in monitor mode are not charged. Set **Maximum cost per run** and the Actor stops cleanly at the limit. ### FAQ **How many jobs can it get?** All jobs of a site; the feed is read 100 jobs per request. In our tests SATS listed 57 open jobs, Oatly 19 and Polestar 17. **Is it legal?** The Actor reads the public RSS feed of Teamtailor career sites, without logging in and without bypassing any protection. No recruiter or candidate data is collected. You are responsible for how you use the data. **A site returns "not found".** The name is probably wrong, or the company has left Teamtailor. Open `https://.teamtailor.com/jobs` in a browser to check. **Does it work with internal or hidden jobs?** No — only jobs that appear on the public career site. # Actor input Schema ## `careerSites` (type: `array`): One per line. Paste a career site URL (https://sats.teamtailor.com/jobs or a custom domain such as https://careers.oatly.com), the account name (`sats` or `teamtailor:sats`), or `teamtailor:careers.oatly.com` for a custom domain. ## `keywords` (type: `array`): Keep jobs whose title contains at least one of these words (whole-word, case-insensitive). Leave empty to keep all. ## `searchInDescription` (type: `boolean`): By default keywords are matched against the job title only. ## `excludeKeywords` (type: `array`): Drop jobs whose title contains any of these words (e.g. Senior, Intern). ## `locations` (type: `array`): Keep jobs whose location, any of their locations, or country contains one of these words (whole-word, case-insensitive; e.g. London, Germany, US). Use `remote` to match remote jobs. ## `remote` (type: `string`): Filter by remote eligibility. ## `departments` (type: `array`): Keep jobs whose Teamtailor department or role contains one of these strings (e.g. Gym). ## `postedWithinDays` (type: `integer`): Only jobs published in the last N days. 0 = no limit. ## `maxItemsPerSource` (type: `integer`): Stop after this many jobs from one board. 0 = all jobs. ## `maxItems` (type: `integer`): Stop the whole run after this many jobs. 0 = no limit. ## `includeDescription` (type: `boolean`): Adds `description_text` (the full job text as plain text). ## `includeDescriptionHtml` (type: `boolean`): Adds `description_html` (cleaned original HTML). ## `monitorMode` (type: `boolean`): Remembers every job already delivered (per board) and outputs only jobs you have not received before. The first run outputs all matching jobs. Ideal for a daily schedule — you only pay for new jobs. ## `monitorStateName` (type: `string`): Name of the key-value store that keeps the list of delivered jobs. Use a different name per task if you run several independent monitors. ## `maxConcurrency` (type: `integer`): Detail requests run in parallel up to this number. Requests to one ATS host are additionally limited to about 4 per second. ## Actor input object example ```json { "careerSites": [ "https://sats.teamtailor.com/jobs", "https://careers.oatly.com" ], "searchInDescription": false, "remote": "any", "postedWithinDays": 0, "maxItemsPerSource": 20, "maxItems": 0, "includeDescription": true, "includeDescriptionHtml": false, "monitorMode": false, "monitorStateName": "teamtailor-jobs-monitor", "maxConcurrency": 4 } ``` # Actor output Schema ## `results` (type: `string`): All Teamtailor job postings collected in this run, one row per job. # API You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup. ## JavaScript example ```javascript import { ApifyClient } from 'apify-client'; // Initialize the ApifyClient with your Apify API token // Replace the '' with your token const client = new ApifyClient({ token: '', }); // Prepare Actor input const input = { "careerSites": [ "https://sats.teamtailor.com/jobs", "https://careers.oatly.com" ], "maxItemsPerSource": 20 }; // Run the Actor and wait for it to finish const run = await client.actor("steadyrow/teamtailor-jobs").call(input); // Fetch and print Actor results from the run's dataset (if any) console.log('Results from dataset'); console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`); const { items } = await client.dataset(run.defaultDatasetId).listItems(); items.forEach((item) => { console.dir(item); }); // 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs ``` ## Python example ```python from apify_client import ApifyClient # Initialize the ApifyClient with your Apify API token # Replace '' with your token. client = ApifyClient("") # Prepare the Actor input run_input = { "careerSites": [ "https://sats.teamtailor.com/jobs", "https://careers.oatly.com", ], "maxItemsPerSource": 20, } # Run the Actor and wait for it to finish run = client.actor("steadyrow/teamtailor-jobs").call(run_input=run_input) # Fetch and print Actor results from the run's dataset (if there are any) print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}") for item in client.dataset(run.default_dataset_id).iterate_items(): print(item) # 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start ``` ## CLI example ```bash echo '{ "careerSites": [ "https://sats.teamtailor.com/jobs", "https://careers.oatly.com" ], "maxItemsPerSource": 20 }' | apify call steadyrow/teamtailor-jobs --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com/?tools=fetch-actor-details,steadyrow/teamtailor-jobs" } } } ``` The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer ` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations). ## OpenAPI specification Download the OpenAPI definition: https://api.apify.com/v2/actors/GeqPisCgjMvMvfvpH/builds/O8XgeWrOD0RhkO9t8/openapi.json