Job Board Keyword Signal Scanner

Turn public job boards into hiring-signal intelligence. This actor scans Greenhouse, Lever, Ashby, and simple careers pages for the exact keywords that matter to your sales, recruiting, RevOps, investment, or market research workflow.

What does Job Board Keyword Signal Scanner do?

Job Board Keyword Signal Scanner accepts public ATS or careers-page URLs and a list of keywords. It returns matching job posts with company name, ATS source, job title, location, department, posting URL, dates, matched keywords, and a context snippet.

Use it when you want to know which companies are hiring for specific tools, teams, compliance programs, seniority levels, or go-to-market motions.

Who is it for?

• 🧭 B2B sales teams looking for buying triggers such as Salesforce, HubSpot, SOC2, Snowflake, AI, RevOps, or security hiring.
• 🧑‍💼 Recruiters monitoring companies hiring for specific roles or technologies.
• 📈 RevOps teams enriching account lists before routing them to SDRs.
• 💼 Investors and analysts tracking company priorities through hiring language.
• 🧪 Growth teams testing niches before building a larger account-intelligence workflow.

Why use this actor?

Hiring pages are public, current, and rich with intent. A company hiring Salesforce administrators, AI platform engineers, RevOps managers, or security compliance roles is often signaling an active internal project. This actor makes those signals exportable and API-ready.

Supported sources

• Greenhouse public job board API and Greenhouse board URLs.
• Lever public posting API and jobs.lever.co board URLs.
• Ashby posting API URLs.
• Generic careers pages as a lightweight fallback.

Data you can extract

Field	Description
company	Company or job board owner
sourceAts	Greenhouse, Lever, Ashby, or generic
jobTitle	Public job title
location	Location exposed by the ATS
department	Team or department when available
postingUrl	Public URL for the matched job
jobId	ATS job ID when available
firstPublishedAt	First publish timestamp when available
updatedAt	Last update timestamp when available
matchedKeywords	Keywords found in title, metadata, or description
matchCount	Number of matched keywords
snippet	Context around the first match
descriptionText	Optional full text when enabled
sourceUrl	Input URL scanned
scrapedAt	Extraction timestamp

How much does it cost to scan job boards for hiring signals?

This actor uses pay-per-event pricing. There is a small start event for each run and a per-item event for each matched job saved to the dataset. Keep your first run small by using the prefilled example and maxResults around 25.

How to use it

1. Open the actor on Apify.
2. Add one or more public job board URLs.
3. Add keywords such as salesforce, revops, soc2, ai, snowflake, or security.
4. Choose any keyword matching for broad discovery or all for strict matching.
5. Run the actor and export the dataset as JSON, CSV, Excel, or via API.

Input example

{
  "sources": [
    {
      "url": "https://boards-api.greenhouse.io/v1/boards/airbnb/jobs?content=true",
      "companyName": "Airbnb",
      "source": "greenhouse"
    },
    {
      "url": "https://api.ashbyhq.com/posting-api/job-board/ashby?includeCompensation=true",
      "companyName": "Ashby",
      "source": "ashby"
    }
  ],
  "keywords": ["salesforce", "revops", "soc2", "ai"],
  "maxResults": 25,
  "matchMode": "any",
  "includeFullDescription": false
}

Output example

{
  "company": "Airbnb",
  "sourceAts": "greenhouse",
  "jobTitle": "Senior Salesforce Engineer",
  "location": "United States",
  "department": "Business Technology",
  "postingUrl": "https://boards.greenhouse.io/...",
  "jobId": "123456",
  "firstPublishedAt": "2026-06-01T00:00:00Z",
  "updatedAt": "2026-06-18T00:00:00Z",
  "matchedKeywords": ["salesforce"],
  "matchCount": 1,
  "snippet": "...own Salesforce workflows and integrations...",
  "sourceUrl": "https://boards-api.greenhouse.io/v1/boards/airbnb/jobs?content=true",
  "scrapedAt": "2026-06-20T20:00:00.000Z"
}

Keyword tips

• Use product names: Salesforce, HubSpot, Snowflake, Databricks.
• Use departments: RevOps, GTM, Partnerships, Security, Compliance.
• Use initiatives: SOC2, ISO 27001, AI, ML, data platform, cloud migration.
• Use role language: founding AE, solutions architect, customer success, platform engineer.

Match modes

any saves a job when at least one keyword appears. This is best for discovery and broader lead lists.

all saves a job only when every keyword appears. This is best when you need high-confidence signals such as salesforce plus revops.

Integrations

• Send matched companies to a CRM as account triggers.
• Join output with a domain resolver or LinkedIn company URL actor.
• Enrich matched companies with contact details.
• Send matching job posts to Slack for daily GTM alerts.
• Load the dataset into Clay, Airtable, Google Sheets, or a warehouse.

API usage with Node.js

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('automation-lab/job-board-keyword-signal-scanner').call({
  sources: [{ url: 'https://boards-api.greenhouse.io/v1/boards/airbnb/jobs?content=true', companyName: 'Airbnb' }],
  keywords: ['salesforce', 'revops'],
  maxResults: 25
});
console.log(run.defaultDatasetId);

API usage with Python

from apify_client import ApifyClient
import os

client = ApifyClient(os.environ['APIFY_TOKEN'])
run = client.actor('automation-lab/job-board-keyword-signal-scanner').call(run_input={
    'sources': [{'url': 'https://api.ashbyhq.com/posting-api/job-board/ashby?includeCompensation=true', 'companyName': 'Ashby'}],
    'keywords': ['ai', 'security'],
    'maxResults': 25,
})
print(run['defaultDatasetId'])

API usage with cURL

curl -X POST 'https://api.apify.com/v2/acts/automation-lab~job-board-keyword-signal-scanner/runs?token=YOUR_APIFY_TOKEN' \
  -H 'Content-Type: application/json' \
  -d '{"sources":[{"url":"https://boards-api.greenhouse.io/v1/boards/airbnb/jobs?content=true","companyName":"Airbnb"}],"keywords":["salesforce","revops"],"maxResults":25}'

MCP usage

Use the Apify MCP server with Claude Code or Claude Desktop to run this actor as a tool:

https://mcp.apify.com/?tools=automation-lab/job-board-keyword-signal-scanner

Claude Code setup:

claude mcp add apify-job-board-keyword-signal-scanner \
  https://mcp.apify.com/?tools=automation-lab/job-board-keyword-signal-scanner

Claude Desktop JSON config:

{
  "mcpServers": {
    "apify-job-board-keyword-signal-scanner": {
      "url": "https://mcp.apify.com/?tools=automation-lab/job-board-keyword-signal-scanner"
    }
  }
}

Example prompts:

• "Scan these Greenhouse URLs for Salesforce and RevOps hiring signals."
• "Find companies hiring for SOC2 or security compliance roles."
• "Turn this list of Lever boards into GTM trigger signals."

Best practices

• Start with 5-20 companies and a small keyword list.
• Use companyName when the URL does not reveal the company clearly.
• Keep includeFullDescription off unless you need the text for downstream LLM enrichment.
• Use maxResults to cap exploratory runs.

Troubleshooting

If a source returns no matches, check that the job board is public and that your keywords appear in visible job text. Use broader keywords first, then narrow down.

If a generic careers page gives only one result, that is expected. Generic mode scans a page as a fallback signal source, while Greenhouse, Lever, and Ashby return individual job posts.

Limitations

The actor reads public job-board data only. It does not log into private ATS systems, submit applications, bypass access controls, or scrape candidate data. Some companies customize their careers pages in ways that require a future adapter.

Legality

This actor is designed for public business and hiring information. Always respect applicable laws, platform terms, privacy obligations, and your own compliance rules. Do not use the output for discriminatory employment decisions.

Related scrapers and workflows

• https://apify.com/automation-lab/domain-to-linkedin-url-resolver
• https://apify.com/automation-lab/contact-details-scraper
• https://apify.com/automation-lab/b2b-url-finder

Changelog

• 0.1 — Initial version with Greenhouse, Lever, Ashby, and generic careers-page scanning.

FAQ

Can I scan any company careers page?

Yes, but structured results work best with Greenhouse, Lever, and Ashby. Generic pages are treated as page-level signals.

Does this actor need proxies?

No proxy is required for the default public ATS API workflow.

Can I monitor the same companies every week?

Yes. Create an Apify task with your sources and keywords, then schedule it daily or weekly.

Can I export to CSV?

Yes. Use Apify dataset export to download JSON, CSV, Excel, XML, RSS, or HTML.

Can I include full descriptions?

Yes. Enable includeFullDescription if your workflow needs complete text for LLM processing or deeper enrichment.