# Teamtailor Jobs Lookup — Live Postings by Company (`accountable_eel/teamtailor-jobs-lookup`) Actor Look up any company's live Teamtailor job board and get every open role — title, location, apply link. Filter by job title, location, remote, or posted date, or get only the postings that are new since your last run. Charged once per company checked, however many roles it has open. - **URL**: https://apify.com/accountable\_eel/teamtailor-jobs-lookup.md - **Developed by:** [Adrian Voss](https://apify.com/accountable_eel) (community) - **Categories:** Jobs, Lead generation - **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks - **User rating**: No ratings yet ## Pricing from $2.00 / 1,000 successful lookups This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events. Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have. Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event ## What's an Apify Actor? Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows. 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. Actors are written with capital "A". ## 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. The best way to integrate Actors is as follows. - **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use). - **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`. - **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`. - **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`. - **Any other language** — the [REST API](https://docs.apify.com/api/v2.md). For usage examples, see the [API](#api) section below. For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt). # README ## Teamtailor Jobs Lookup — Live Postings by Company You paste a list of companies. For each one, this actor looks up their live **Teamtailor** job board and returns every open role — title, location, and apply link — as one row per posting (or one row per company, your choice). No API key, no HTML scraping: it reads Teamtailor's own public job feed directly. Optional filters narrow the roles you get back by title, location, or posting date, and an optional delta mode returns only the postings that appeared since your last run, so you can put a company list on a schedule and get a hiring alert instead of a full re-dump every time. ### Who it's for The accountable\_eel catalogue sells company intelligence columns for outbound. Each actor takes a list of domains or company identifiers and returns one flat, stably-named row per input — firmographics, registry IDs, tech stack, email route, hiring activity — the shape a Clay table, an n8n workflow, or an AI agent can consume without post-processing. Pricing is pay-per-event and per-company: a few tenths of a cent for a row that was actually found, and nothing for a miss, so a list that doesn't enrich costs you next to nothing. Here, the "identifier" is a Teamtailor subdomain token or careers URL, and the "row" is a job posting — useful for sourcing candidates, watching a competitor's hiring, or tracking headcount signal across a target list. Teamtailor is the dominant ATS across the Nordics and much of continental Europe, a segment the portfolio's other six ATS actors (Greenhouse, Lever, Ashby, Workday, Workable, SmartRecruiters, Personio) don't cover. ### Why this one - **Direct from Teamtailor's own job feed.** No HTML scraping to break when a careers page gets redesigned — this reads `.teamtailor.com/jobs.json`, the same public JSON Feed (jsonfeed.org spec, with an embedded schema.org `JobPosting` per item) that every Teamtailor board publishes, no login required. - **You pay per company, not per job.** A board with 23 open roles and a board with 2 both cost one `item-lookup` charge. A company with no board, or zero open roles, is a free miss. - **Real filters, not a wall of raw fields.** Title keyword include/exclude, location, remote-only, and posted-after-date all combine, so you can ask for exactly the roles you want. - **A delta mode for watching hiring over time.** Turn on `onlyNewSinceLastRun`, put the actor on a schedule, and every run after the first returns only postings you haven't seen — a quiet week still gets a row, so you can tell "nothing new" from "the run broke." - **Flexible input.** A bare Teamtailor subdomain token or the full careers URL both work — no need to go find the raw subdomain first. ### What you get One row per open job posting by default (toggle "One row per job posting" off in the Input tab to get one row per company instead, with the full job list nested in `jobs`). Every row carries these fields, whether or not you've turned on filters or delta mode — the columns never move: | Field | Type / format | Description | | --- | --- | --- | | `query` | text | The company value you passed in, unchanged. | | `found` | boolean | `true` if the company has a Teamtailor board with at least one open role, `false` otherwise. | | `status` | text | `OK`, `NOT_FOUND` (no board, or no open roles), or `BAD_FORMAT` (input didn't look like a subdomain or URL). | | `boardToken` | text | The Teamtailor subdomain, extracted from whatever you pasted (bare token or careers URL). | | `jobCount` | number | How many roles matched, after your filters (and after delta filtering, if `onlyNewSinceLastRun` is on). | | `totalJobCount` | number | How many roles were on the board before any filtering — lets you see what a filter dropped. | | `newJobs` | number | How many roles are new since your last scheduled run. Empty unless `onlyNewSinceLastRun` is on. | | `firstRun` | boolean | `true` if this was the baseline run for this watchlist. Empty unless `onlyNewSinceLastRun` is on. | | `jobs` | array | The full list of matching jobs, each with the fields below. Present in every row; it's what gets expanded into separate rows in "one row per job" mode. | | `title` | text | Job title. | | `location` | text | City and country as Teamtailor's structured `JobPosting.jobLocation` lists it (e.g. "Munich, DE"); multiple locations join with `; `. | | `remote` | boolean | `true` if the location or title reads as remote (matches "remote", "anywhere", "work from home", "wfh", "distributed" in the location, or the word "remote" in the title). | | `postedAt` | date (ISO) | When Teamtailor published the posting. | | `applyUrl` | link | Direct apply link for the role. | | `scrapedAt` | date (ISO) | When this actor fetched the row. | A company with no Teamtailor board, or with a board but zero open roles, still comes back as one row with `found: false` and a `status`/`message` explaining why — and that row is never charged. ### Price $4 per 1,000 companies, plus a $0.00005 start fee. Misses (`found:false`) are never charged. However many roles a found company has open, it's one charge: a board with 23 postings costs the same as one with 2. Misses (`found: false`) — no board, or a `BAD_FORMAT` input — are never charged, no matter how many companies are in the list. ### How to use 1. **In the Apify Console.** Open the actor page and click **Start** — the `companies` field is already pre-filled with a working example. Results land in the run's dataset as soon as each item is found. 2. **Via the API.** Call it directly with a POST request — no Console needed once you have an API token: ```bash curl "https://api.apify.com/v2/acts/accountable_eel~teamtailor-jobs-lookup/run-sync-get-dataset-items?token=" \ -X POST \ -H "Content-Type: application/json" \ -d '{"companies":["tmgchicago"]}' ``` 3. **On a schedule.** Save this actor as an Apify **Task** with the input you want, then add a **Schedule** (hourly, daily, weekly) so it runs on its own — no server of your own required. Paste one company per line — a bare Teamtailor subdomain like `tmgchicago`, or the full careers URL (`https://tmgchicago.teamtailor.com/jobs` or just `https://tmgchicago.teamtailor.com`). The subdomain is extracted automatically either way, so you don't need to go look up the raw feed URL. To narrow the roles you get back, open the **🎯 Job filters** section of the Input tab. All of these are optional and combine with AND across fields, OR within a field: | Input | What it does | | --- | --- | | `titleKeywords` | Keep only roles whose title contains at least one of these — `["engineer","designer"]`. Case-insensitive, partial words count. | | `excludeTitleKeywords` | Drop roles whose title contains one of these — `["intern","contract"]`. Applied after `titleKeywords`. | | `locations` | Keep only roles whose location contains one of these — `["Berlin","United States"]`. | | `remoteOnly` | Keep only roles that read as remote. | | `postedAfter` | Keep only roles first published on or after this date — `"2026-06-01"`. | Leave every filter empty and you get every open role. `jobCount` (matched) and `totalJobCount` (before filtering) both come back on every row, so a filtered result is never ambiguous — and a company whose roles all get filtered out still returns a `found: true` row with `jobCount: 0`, charged like any other found company, because it answered the question you asked. For a standing watchlist, turn on **`onlyNewSinceLastRun`** in the **🔁 Watch for new jobs** section and put the actor on a schedule. The first run baselines (returns everything matching your filters, `firstRun: true`); every run after that returns only postings it hasn't shown you before, counted in `newJobs`. A quiet run still returns a row per company (`jobCount: 0`, `newJobs: 0`) so you can tell "nothing new" from "the run failed" — and every company checked is still charged once. Two schedules with different filter values keep separate seen-lists automatically. ### Input ```json { "companies": [ "tmgchicago" ] } ``` One company per line — paste the Teamtailor subdomain token or the full careers page URL. Accepted formats: cigames, https://cigames.teamtailor.com/jobs, https://parcellab.teamtailor.com. ### Sample output | query | found | status | boardToken | jobCount | totalJobCount | newJobs | firstRun | jobs | title | location | remote | postedAt | applyUrl | scrapedAt | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | tmgchicago | true | OK | tmgchicago | 23 | 23 | | | \ | CNC Field Service Technician - (Remote Work) | Valparaiso, US | true | 2026-08-20T10:48:48-05:00 | https://tmgchicago.teamtailor.com/jobs/8250011-cnc-field-service-technician-remote-work | 2026-08-31T07:00:53.752Z | In "one row per company" mode (turn off "One row per job posting"), the same run returns a single row per company with the full job list nested under `jobs` and `title`/`location`/`remote`/ `postedAt`/`applyUrl` empty at the parent level. ### Use it from Clay, n8n, Make, or an AI agent This actor runs synchronously over plain HTTP — call it directly from a script, a workflow tool, or an AI agent, no Apify Console needed once you have an API token. ```bash curl "https://api.apify.com/v2/acts/accountable_eel~teamtailor-jobs-lookup/run-sync-get-dataset-items?token=" \ -X POST \ -H "Content-Type: application/json" \ -d '{"companies":["tmgchicago"]}' ``` **n8n.** Add an HTTP Request node: Method `POST`, URL `https://api.apify.com/v2/acts/accountable_eel~teamtailor-jobs-lookup/run-sync-get-dataset-items?token=`, Body Content Type `JSON`, JSON Body `{"companies":["tmgchicago"]}` (swap in an expression from an earlier node for a real value). **Clay.** Add an "HTTP API" column: Method `POST`, URL `https://api.apify.com/v2/acts/accountable_eel~teamtailor-jobs-lookup/run-sync-get-dataset-items?token=`, Body `{"companies":["{{company}}"]}`, mapping the row's company into the `companies` array. **MCP.** In Claude, Cursor, or any MCP client with the Apify MCP server, ask for "Teamtailor Jobs Lookup | Apify" — the agent will find and run this actor. ### Tips - **Combine filters to build a watchlist query, not just a keyword search.** `titleKeywords: ["engineer"]` plus `locations: ["Stockholm"]` gets you Stockholm-based engineering roles only, in one pass, instead of filtering a full dump afterward. - **Put delta mode on a weekly schedule for competitor tracking.** `onlyNewSinceLastRun` plus a fixed company list turns this into a hiring-alert feed. - **Switch to one-row-per-company mode when you just want a headcount number.** Turn off "One row per job posting" and read `jobCount` per company for a fast hiring-momentum signal across a long company list. - **Don't combine delta mode with "Only keep rows containing."** That filter runs on the finished row and can drop the `newJobs: 0` heartbeat row — the one row that tells you the schedule is still alive on a quiet week. ### vs. alternatives | | What it costs | What you get | Trade-off | |---|---|---|---| | **This actor** (`teamtailor-jobs-lookup`) | Charged per company whose board is found, nothing for a company with no Teamtailor board | Every open posting for a company's Teamtailor board — title, location, apply URL — filtered by role keyword, location or posting date, with `onlyNewSinceLastRun` for deltas | Teamtailor only. No dedicated Teamtailor actor previously existed in the Apify Store. | | **Teamtailor's own feed** | Free | The same JSON | It is the same JSON. This handles the subdomain-token guessing, filtering, deltas, retries, and the MIME-type quirk of Teamtailor's feed (`application/feed+json`, which a naive crawler silently drops), and hands you a flat table. | | **Clay** | Credits, on top of a seat | A whole enrichment workspace | If you want one place that does everything and you're not counting rows, that's Clay. This is one column, priced per column, callable *from* Clay via its HTTP step. | ### FAQ **Why does `found` say false, or a row come back empty?** Either the input didn't look like a Teamtailor subdomain or URL (`status: BAD_FORMAT`), the company doesn't have a Teamtailor board, or it currently has zero open roles (`status: NOT_FOUND` either way). Check the `message` column for the specific reason. **Was I charged for that row?** Only if `found` is `true`. A company with no board, or no current openings, is free — check `status` to confirm which case it was. **I got charged for a company that returned `jobCount: 0` — why?** Because its board exists and has open roles — they just didn't match your filters, or weren't new since your last delta run. `totalJobCount` shows how many were actually on the board before filtering. That's a real answer to the question you asked, so it's billed like any other found company. A company with no board at all, or nothing open, comes back `found: false` and is never charged. **How does the delta / "new since last run" state work, and can I reset it?** It lives in a named key-value store, `teamtailor-jobs-lookup-state`, inside your own Apify account — nobody else can see it. Delete that store to reset every watchlist and re-baseline on the next run. Changing your filters also starts a fresh watchlist automatically. **Why is there no `departments` field, and no `updatedAt`?** Teamtailor's job feed doesn't expose a department, category, or employment-type field anywhere — not on the feed item, not inside the embedded `JobPosting` data — and there's no second endpoint to source one from either, unlike some other ATS platforms. Rather than ship a column that would be permanently blank, there isn't one. Likewise, the feed carries exactly one date per posting (`datePosted`, or the feed's own `date_published` when the structured data is missing) — there is no separate last-modified timestamp to report as `updatedAt`, so `postedAt` is the only date field. **Does this actor hit rate limits on large company lists?** It calls Teamtailor's public job feed once per company, with its own timeout and retry handling. The feed is unauthenticated and public — this actor doesn't need proxies to reach it. Very large company lists still take proportionally longer to run, since each company is a separate request. **Is this GDPR-safe to run against companies in the EU?** The data returned is what each company has already published publicly on its own careers page — job titles, locations, apply links. No personal data about applicants or employees is collected. As with any lookup, you're responsible for how you use the output downstream. **Can I run this on a schedule?** Yes — set up an Apify schedule against this actor with your company list as input. Combine it with `onlyNewSinceLastRun` for a hiring-alert feed, or leave it off to get a fresh full dump every run. **Can an AI agent call this directly?** Yes — it's registered with the Apify MCP server. An agent with that MCP connected can find and run "Teamtailor Jobs Lookup" by name and get dataset rows back without you writing any integration code; see [Use it from Clay, n8n, Make, or an AI agent](#use-it-from-clay-n8n-make-or-an-ai-agent). ### Related actors - [Greenhouse Jobs Lookup](https://apify.com/accountable_eel/greenhouse-jobs-lookup) — the same lookup, filters, and delta mode for companies on Greenhouse. - [Lever Jobs Lookup](https://apify.com/accountable_eel/lever-jobs-lookup) — the same lookup, filters, and delta mode for companies on Lever. - [Workable Jobs Lookup](https://apify.com/accountable_eel/workable-jobs-lookup) — the same lookup, filters, and delta mode for companies on Workable. # Actor input Schema ## `companies` (type: `array`): One company per line — paste the Teamtailor subdomain token or the full careers page URL. Accepted formats: cigames, https://cigames.teamtailor.com/jobs, https://parcellab.teamtailor.com. You're only charged for the ones we actually find — a miss costs nothing. ## `testRun` (type: `boolean`): Turn this on to test your input on a small sample before running the full list. Turn it off to process everything. ## `onlyFound` (type: `boolean`): Only keep rows where something was actually found. Misses are always free, whether or not you show them here. ## `includeKeywords` (type: `array`): Optional. Only keep results that mention at least one of these words (e.g. a job title, a city, a product name). Leave empty to keep everything. ## `excludeKeywords` (type: `array`): Optional. Drop any result that mentions one of these words. Leave empty to skip nothing. ## `maxResults` (type: `integer`): Optional. Stop the run once this many results have been found — useful for a quick, cheap sample. Leave blank for no limit. ## `titleKeywords` (type: `array`): Optional. Keep only roles whose title contains at least one of these words — e.g. "engineer", "account executive", "designer". Case doesn't matter, and partial words work ("engineer" matches "Engineering Manager"). Leave empty to keep every role. ## `excludeTitleKeywords` (type: `array`): Optional. Drop any role whose title contains one of these words — e.g. "intern", "senior", "contract". Applied after the include list above, so a role matching both is dropped. ## `locations` (type: `array`): Optional. Keep only roles whose location mentions one of these — e.g. "Berlin", "New York", "United Kingdom". Case doesn't matter and partial matches work. Leave empty to keep every location. ## `remoteOnly` (type: `boolean`): Keep only roles whose location or title says remote (also matches "anywhere", "work from home", "distributed"). Companies label remote work inconsistently, so treat this as a strong filter, not a guarantee. ## `postedAfter` (type: `string`): Optional. A date like 2026-06-01 (or a full timestamp). Keeps only roles Teamtailor published on or after it — useful for "what opened up this month". Leave empty for no date limit. ## `onlyNewSinceLastRun` (type: `boolean`): Turn this on for a scheduled watchlist: the first run returns everything that matches and remembers it, and every run after that returns only postings it hasn't shown you before. A company with nothing new still gets a row (with 0 jobs), so a quiet schedule never looks like a broken one. Changing the filters above starts a fresh watchlist. ## `columns` (type: `array`): Choose which pieces of information to include in each result row. All are included by default. ## `expandRows` (type: `boolean`): When on, each job posting found gets its own row instead of being grouped under its company. You're still only charged once per company, no matter how many rows it produces. ## `maxConcurrency` (type: `integer`): Parallel requests. Keep conservative — this target has no browser fallback, so getting blocked costs more than slow-and-steady. ## `proxyConfiguration` (type: `object`): Apify Proxy config. Residential recommended for anti-bot-sensitive targets. ## Actor input object example ```json { "companies": [ "tmgchicago" ], "testRun": false, "onlyFound": false, "includeKeywords": [], "excludeKeywords": [], "titleKeywords": [], "excludeTitleKeywords": [], "locations": [], "remoteOnly": false, "postedAfter": "", "onlyNewSinceLastRun": false, "columns": [ "boardToken", "jobCount", "totalJobCount", "newJobs", "firstRun", "jobs", "title", "location", "remote", "postedAt", "applyUrl" ], "expandRows": true, "maxConcurrency": 5, "proxyConfiguration": { "useApifyProxy": true } } ``` # Actor output Schema ## `results` (type: `string`): No description # 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 = { "companies": [ "tmgchicago" ], "includeKeywords": [], "excludeKeywords": [], "titleKeywords": [], "excludeTitleKeywords": [], "locations": [] }; // Run the Actor and wait for it to finish const run = await client.actor("accountable_eel/teamtailor-jobs-lookup").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 = { "companies": ["tmgchicago"], "includeKeywords": [], "excludeKeywords": [], "titleKeywords": [], "excludeTitleKeywords": [], "locations": [], } # Run the Actor and wait for it to finish run = client.actor("accountable_eel/teamtailor-jobs-lookup").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 '{ "companies": [ "tmgchicago" ], "includeKeywords": [], "excludeKeywords": [], "titleKeywords": [], "excludeTitleKeywords": [], "locations": [] }' | apify call accountable_eel/teamtailor-jobs-lookup --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com/?tools=fetch-actor-details,accountable_eel/teamtailor-jobs-lookup" } } } ``` 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/NvYjzYlPb1UE0m5WY/builds/oLVP2LBKmUSw5gH52/openapi.json