# Austin Tech Jobs Monitor — Greenhouse, Lever & Ashby (`recordstack/austin-tech-jobs-monitor`) Actor

Open jobs at Austin tech employers, pulled live from the public Greenhouse, Lever and Ashby board APIs, matched to Austin offices, deduped, with an only-new monitor mode for scheduled runs.

- **URL**: https://apify.com/recordstack/austin-tech-jobs-monitor.md
- **Developed by:** [Alex Meacham](https://apify.com/recordstack) (community)
- **Categories:** Lead generation, Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$5.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

## Austin Tech Jobs Monitor

Open jobs at Austin tech employers, pulled live from the employers' own
public job-board APIs — Greenhouse, Lever and Ashby — matched to Austin,
deduped, and delivered as one clean table.

### Why this exists

Each board API is free to call, but every employer uses a different
platform with a different schema, and some boards (Cloudflare is the
classic case) publish only a workplace label like "Hybrid" in the list
view — the actual office city is buried in each job's detail record.
This actor handles all of that: it checks the location field AND the
Greenhouse office list (via detail lookups), normalizes the three
platforms into one schema, dedupes, and can run as an **only-new
monitor**: schedule it daily and each run returns only jobs you have
not already seen.

### Default employers (verified live, October 2026)

Greenhouse: Cloudflare, DISCO, AlertMedia, Samsara, Elastic, Airtable.
Ashby: Vanta. Lever: supported — add any jobs.lever.co slug.
Swap in your own list of board tokens at any time.

### Inputs

- `cityKeyword` — default `Austin`; matched against location and offices
- `greenhouseBoards` / `ashbyBoards` / `leverBoards` — board tokens
- `includeRemote` — also match jobs labelled Remote (default off)
- `onlyNewSinceLastRun` — monitor mode (state kept between runs)
- `maxJobs` — per-run cap (you are only charged for jobs delivered)
- `maxDetailFetchesPerBoard` — cap on Greenhouse detail lookups

### Output fields

company, platform, jobId, dedupeId, title, department, locationText,
cityMatched, workplaceType, employmentType, postedAt, updatedAt,
jobUrl, applyUrl, scrapedAt.

### Price

$0.005 per Austin-matched job delivered — under half the ~$0.012/row
charged by the established career-site jobs tool on the same feeds.

### Limits

Coverage is only as good as each employer's board: companies that move
ATS platforms or stop listing Austin offices simply return fewer rows.
Austin matching is keyword-based on the employer's own location/office
text.

# Actor input Schema

## `cityKeyword` (type: `string`):

Matched against each job's location and (on Greenhouse) its office list.

## `greenhouseBoards` (type: `array`):

Company tokens from boards.greenhouse.io/<token>. Defaults are verified Austin employers.

## `ashbyBoards` (type: `array`):

Company slugs from jobs.ashbyhq.com/<slug>.

## `leverBoards` (type: `array`):

Company slugs from jobs.lever.co/<slug>. Empty by default; add any Lever employer.

## `includeRemote` (type: `boolean`):

Also match jobs whose location says Remote (they are not Austin-office roles).

## `onlyNewSinceLastRun` (type: `boolean`):

Monitor mode: return only jobs this actor has not delivered in earlier runs (state kept in the actor's key-value store).

## `maxJobs` (type: `integer`):

Cap on jobs delivered (and charged) per run.

## `maxDetailFetchesPerBoard` (type: `integer`):

Some boards (e.g. Cloudflare) publish only a workplace label in the list view; the real office city is in each job's detail record. This caps the detail lookups per board.

## Actor input object example

```json
{
  "cityKeyword": "Austin",
  "greenhouseBoards": [
    "cloudflare",
    "disco",
    "alertmedia",
    "samsara",
    "elastic",
    "airtable"
  ],
  "ashbyBoards": [
    "vanta"
  ],
  "leverBoards": [],
  "includeRemote": false,
  "onlyNewSinceLastRun": false,
  "maxJobs": 500,
  "maxDetailFetchesPerBoard": 500
}
```

# Actor output Schema

## `datasetUrl` (type: `string`):

Open the dataset with the jobs found in this run.

# 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 '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {};

// Run the Actor and wait for it to finish
const run = await client.actor("recordstack/austin-tech-jobs-monitor").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 '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {}

# Run the Actor and wait for it to finish
run = client.actor("recordstack/austin-tech-jobs-monitor").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 '{}' |
apify call recordstack/austin-tech-jobs-monitor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,recordstack/austin-tech-jobs-monitor"
        }
    }
}
```

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 <APIFY_API_TOKEN>` 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/eIDbbC5JnkcrqTlvU/builds/KkboEfJaLTZvtXEXk/openapi.json