WorkIndia Jobs Scraper

Extract public WorkIndia job listings by city, category, listing URL, or job detail URL. Get salary, company, locality, category, experience, qualification, posted text, and optional detail-page enrichment in a clean dataset.

What does WorkIndia Jobs Scraper do?

WorkIndia Jobs Scraper turns public pages on workindia.in into structured job-posting data.

Use it to monitor frontline hiring demand across Indian cities, compare local salary ranges, collect public job URLs for recruiting workflows, and track category-level job supply.

The actor is HTTP-first and reads the server-rendered WorkIndia pages that are visible without login.

It does not scrape private candidate data, resumes, hidden phone numbers, or authenticated employer dashboards.

Who is it for?

Recruitment agencies can monitor active blue-collar and frontline job demand by city and role.

Staffing marketplaces can build market intelligence datasets for delivery, telecalling, retail, back-office, driver, and field-sales jobs.

HR analytics teams can compare salaries and hiring volume across localities.

Developers can plug structured WorkIndia job data into lead-routing, alerts, dashboards, or enrichment pipelines.

Researchers can observe public employment trends without manually browsing dozens of city/category pages.

Why use this actor?

• ✅ Extracts public WorkIndia job cards into a typed dataset
• ✅ Supports city slugs and category slugs
• ✅ Accepts direct WorkIndia listing URLs and job detail URLs
• ✅ Optional detail-page enrichment for richer records
• ✅ No browser needed for the default workflow
• ✅ Includes source URL and scrape timestamp for auditability

Typical use cases

• Track delivery hiring in Bengaluru, Mumbai, Delhi, Pune, and Hyderabad
• Compare monthly salary ranges by city and role
• Build a recruiter lead list from public job postings
• Monitor new postings in localities relevant to your business
• Enrich internal labor-market dashboards with WorkIndia supply data
• Create recurring alerts for high-volume categories

Data fields

Field	Description
jobTitle	Public WorkIndia job title
jobUrl	Canonical WorkIndia job detail URL
companyName	Company name when visible
city	City parsed from location or detail data
locality	Locality/neighborhood when visible
location	Full location text from WorkIndia
category	Job category such as Delivery or Telecaller
salary	Public salary range text
minSalary	Numeric minimum salary from detail data when available
maxSalary	Numeric maximum salary from detail data when available
experience	Experience requirement
shiftOrTimings	Job timings from detail pages
qualification	Education/gender requirement text when visible
englishRequirement	English requirement shown by WorkIndia
openings	Openings count from detail route data
postedText	Listing posted text
postedAt	Detail-page created timestamp when available
description	Job description from detail page
jobAddress	Job address from detail page
interviewTimings	Interview timing text
views	Listing badge text when visible
tags	Listing badges such as New or views
sourceUrl	Listing/detail URL that produced the record
scrapedAt	ISO timestamp of extraction

How much does it cost to scrape WorkIndia jobs?

This actor uses pay-per-event pricing.

There is a small start charge for each run and a per-job charge for each dataset item produced.

The default input is intentionally small so you can test cheaply before running broader city/category monitoring.

Current formula-derived BRONZE price is $0.005 per run start plus $0.000029093 per job item, with lower per-item prices on higher Apify tiers.

Input options

Start URLs

Paste one or more WorkIndia listing URLs or job detail URLs.

Examples:

[
  { "url": "https://www.workindia.in/jobs-in-bengaluru/" },
  { "url": "https://www.workindia.in/delivery-jobs-in-mumbai/" }
]

City slugs

Use WorkIndia city slugs such as:

• bengaluru
• mumbai
• delhi
• pune
• hyderabad
• chennai

The actor creates URLs like https://www.workindia.in/jobs-in-bengaluru/.

Category slugs

Use category slugs such as:

• delivery
• telecalling
• accountant
• field-sales
• driver
• back-office
• retail

When combined with city slugs, the actor creates URLs like https://www.workindia.in/delivery-jobs-in-bengaluru/.

Maximum jobs

maxItems is a global cap across all input URLs.

Use a small value for tests and a larger value for production monitoring.

Detail enrichment

Set includeDetails to true when you need description, openings, timings, address, salary bounds, and posted timestamp.

Detail enrichment makes one extra HTTP request per job.

Example input: city monitoring

{
  "citySlugs": ["bengaluru", "mumbai", "delhi"],
  "maxItems": 60,
  "includeDetails": false
}

Example input: category monitoring

{
  "citySlugs": ["bengaluru", "mumbai"],
  "categorySlugs": ["delivery", "telecalling", "driver"],
  "maxItems": 100,
  "includeDetails": true,
  "requestDelayMs": 250
}

Example input: exact URLs

{
  "startUrls": [
    { "url": "https://www.workindia.in/jobs-in-bengaluru/" },
    { "url": "https://www.workindia.in/delivery-jobs-in-bengaluru/" }
  ],
  "maxItems": 40,
  "includeDetails": false
}

Example output

{
  "jobTitle": "Delivery Executive / Rider",
  "jobUrl": "https://www.workindia.in/jobs/delivery_executive__rider-kogilu-bengaluru-10508257/",
  "companyName": "MANNEKERG SOLUTIONS PRIVATE LIMITED",
  "city": "Bengaluru",
  "locality": "Kogilu",
  "location": "Kogilu, Bengaluru",
  "category": "Delivery",
  "salary": "Rs. 35000 - Rs. 59000",
  "experience": "Fresher",
  "qualification": "< 10th Pass / Male Only",
  "postedText": "Posted on: 7/8/2026",
  "sourceUrl": "https://www.workindia.in/jobs-in-bengaluru/",
  "scrapedAt": "2026-07-08T00:00:00.000Z"
}

How to run

1. Open the actor on Apify.
2. Add WorkIndia URLs or city/category slugs.
3. Choose maxItems.
4. Enable detail enrichment only if you need richer fields.
5. Start the run.
6. Download results as JSON, CSV, Excel, or via API.

Tips for better results

• Use WorkIndia slugs exactly as they appear in URLs.
• Combine multiple city/category pages for larger datasets.
• Keep detail enrichment off for fast salary/category monitoring.
• Turn detail enrichment on for lead qualification or analytics.
• Use scheduled Apify tasks for recurring market monitoring.

Limitations

WorkIndia listing pages usually expose a limited number of visible jobs per page.

For larger runs, provide multiple city or category pages.

The actor only returns information that WorkIndia exposes publicly in HTML or route data.

It does not bypass application forms, login walls, or candidate privacy controls.

Integrations

Connect results to Google Sheets for recruiter review.

Send dataset items to Airtable for lead qualification.

Use webhooks to notify Slack when a scheduled run finishes.

Load CSV exports into BI tools for salary and category dashboards.

Use the Apify API to feed WorkIndia jobs into enrichment pipelines.

API usage: Node.js

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('automation-lab/workindia-jobs-scraper').call({
  citySlugs: ['bengaluru'],
  categorySlugs: ['delivery'],
  maxItems: 20,
});

const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

API usage: Python

from apify_client import ApifyClient
import os

client = ApifyClient(os.environ['APIFY_TOKEN'])
run = client.actor('automation-lab/workindia-jobs-scraper').call(run_input={
    'citySlugs': ['mumbai'],
    'categorySlugs': ['telecalling'],
    'maxItems': 20,
})
items = client.dataset(run['defaultDatasetId']).list_items().items
print(items)

API usage: cURL

curl -X POST 'https://api.apify.com/v2/acts/automation-lab~workindia-jobs-scraper/runs?token=<APIFY_TOKEN>' \
  -H 'Content-Type: application/json' \
  -d '{"citySlugs":["bengaluru"],"categorySlugs":["delivery"],"maxItems":20}'

MCP for Claude and AI agents

Use Apify MCP to call the actor directly from Claude Desktop, Claude Code, or another MCP-compatible tool.

MCP endpoint:

https://mcp.apify.com/?tools=automation-lab/workindia-jobs-scraper

Claude Code setup:

$claude mcp add apify-workindia-jobs "https://mcp.apify.com/?tools=automation-lab/workindia-jobs-scraper"

Claude Desktop JSON config:

{
  "mcpServers": {
    "apify-workindia-jobs": {
      "url": "https://mcp.apify.com/?tools=automation-lab/workindia-jobs-scraper"
    }
  }
}

Example prompts:

• "Run WorkIndia Jobs Scraper for delivery jobs in Bengaluru and summarize salary ranges."
• "Scrape telecalling jobs in Mumbai and return companies with public postings."
• "Compare WorkIndia delivery postings across Bengaluru, Mumbai, and Delhi."

Related scrapers

Other automation-lab actors can complement WorkIndia Jobs Scraper when building labor-market or lead datasets:

• https://apify.com/automation-lab/google-maps-lead-finder
• https://apify.com/automation-lab/linkedin-jobs-scraper if available in your account
• https://apify.com/automation-lab/website-contact-finder

Use WorkIndia Jobs Scraper when the target source is public WorkIndia job postings.

Legality and ethical use

This actor extracts public job-posting information.

Use the data responsibly and follow applicable laws, platform terms, privacy rules, and fair-use principles.

Do not use it to collect private candidate data or circumvent access controls.

Troubleshooting

Why did I get fewer jobs than maxItems?

A single WorkIndia listing page may expose only a limited number of jobs. Add more city/category URLs or slugs to collect more records.

Why are description and openings missing?

Enable includeDetails. Listing pages are faster but contain fewer fields than detail pages.

Why did a category URL return no jobs?

Check the category slug against WorkIndia's URL format. Some categories or city/category combinations may not exist.

FAQ

Can I scrape multiple cities at once?

Yes. Add multiple citySlugs or multiple startUrls.

Can I scrape a single job page?

Yes. Put the job detail URL in startUrls.

Does the actor use a browser?

No. The default implementation uses HTTP and Cheerio because WorkIndia returns useful server-rendered HTML.

Does it return phone numbers?

No. The actor is scoped to public job-posting metadata and avoids private application/contact gates.

Can I schedule it?

Yes. Create an Apify task with your preferred input and schedule it daily, weekly, or hourly.

Changelog

0.1

Initial WorkIndia job-listing extraction with city/category URL generation, listing fields, and optional detail enrichment.