# Job Signal Lead Generator — Indeed & LinkedIn Hiring Data (`avinashchby/job-signal-lead-generator`) Actor

Scrape job postings from Indeed and LinkedIn to identify hiring companies. Extract job titles, company names, locations, salaries, and application URLs. Generate structured hiring-intent signals for sales teams, recruiters, and B2B marketers. Export in JSON, CSV, HubSpot, or Apollo format.

- **URL**: https://apify.com/avinashchby/job-signal-lead-generator.md
- **Developed by:** [Avinash](https://apify.com/avinashchby) (community)
- **Categories:** Lead generation, Marketing
- **Stats:** 1 total users, 0 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $8.00 / 1,000 result processeds

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?

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

## Job Signal Lead Generator — Hiring Company Intelligence

Turn live job postings into B2B sales signals. Search Indeed and LinkedIn for any role, extract hiring companies with job titles, locations, salaries, and application URLs, and export structured hiring-intent data for sales teams, recruiters, and marketers.

### How It Works

The actor queries each selected job board for your title (and optional location), pages through results, and normalizes every posting into a hiring signal: company name, job title, location, salary (when listed), posting date, and direct application URL. LinkedIn is queried through its public guest jobs API, which is fast and reliable. Indeed is fetched as a best-effort HTML source — it frequently rate-limits datacenter IPs, so for heavy Indeed usage attach your own proxy in the input. One blocked source never fails the run: the actor reports per-source status and returns everything it collected.

### Features

- **Multi-board search**: Indeed + LinkedIn in a single run
- **Hiring signals**: Company, title, location, salary, posted date, apply URL
- **Location filter**: City, state, or country targeting
- **Deduplication**: Same posting never returned twice
- **CRM export**: JSON, CSV, HubSpot, and Apollo-friendly output
- **Proxy support**: Apify Proxy included; bring your own for Indeed at scale
- **Never fails on blocks**: Time-budgeted crawl, graceful per-source fallback

### Input Parameters

| Parameter | Type | Default | Description |
|-----------|------|---------|-------------|
| `jobTitle` | string | `software engineer` | Job title to search for (required) |
| `location` | string | — | City, state, or country filter |
| `maxResults` | integer | `50` | Max job signals (1-500) |
| `sources` | array | `["indeed", "linkedin"]` | Job boards to search |
| `outputFormat` | string | `json` | Export format |
| `proxyConfiguration` | object | Apify Proxy | Proxy for reliable access |

### Output Example

```json
{
  "jobTitle": "Senior Software Engineer (Identity Engineering)",
  "company": "Cisco",
  "location": "Austin, TX",
  "salary": "",
  "postedDate": "2026-09-01",
  "jobUrl": "https://www.linkedin.com/jobs/view/senior-software-engineer-identity-e",
  "source": "linkedin",
  "signalType": "hiring",
  "scrapedAt": "2026-09-06T05:01:45.000Z"
}
```

The `OUTPUT` record also includes `source_status` per board (e.g. `{"indeed": "unreachable", "linkedin": "ok (5 total)"}`) so you always know where the data came from.

### Use Cases

- **Sales prospecting**: Target companies that are hiring (growth = budget)
- **Recruiting**: Map competitor hiring velocity by role and location
- **Market research**: Track demand for skills across boards
- **Lead enrichment**: Feed hiring companies into your CRM sequences

# Actor input Schema

## `jobTitle` (type: `string`):

Job title to search for, e.g. 'software engineer', 'sales manager', 'data scientist'

## `location` (type: `string`):

Optional city, state, or country filter

## `maxResults` (type: `integer`):

Maximum number of job signals to return

## `sources` (type: `array`):

Which job boards to search

## `outputFormat` (type: `string`):

Export format

## `proxyConfiguration` (type: `object`):

Select a proxy to avoid blocking. Use Apify Proxy (recommended) or bring your own.

## Actor input object example

```json
{
  "jobTitle": "software engineer",
  "maxResults": 50,
  "sources": [
    "indeed",
    "linkedin"
  ],
  "outputFormat": "json",
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}
```

# Actor output Schema

## `results` (type: `string`):

All scraped and enriched data items.

# 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("avinashchby/job-signal-lead-generator").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("avinashchby/job-signal-lead-generator").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 avinashchby/job-signal-lead-generator --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,avinashchby/job-signal-lead-generator"
        }
    }
}

```

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/PPVJlq7dSzzIo0dcV/builds/MxCdzSTN8GXqvkGgV/openapi.json
