# Whatsapp Indonesia Leads Scrape by Places (`masoncode/waready-id`) Actor

Get WhatsApp-ready local leads from 22 Indonesian cities. Pick a city and place type, then download +62 mobiles and wa.me links from public OpenStreetMap. Export CSV or Excel, schedule runs, or call the API. You only pay for rows you can message. Not a Google Maps scraper.

- **URL**: https://apify.com/masoncode/waready-id.md
- **Developed by:** [Mason Alv](https://apify.com/masoncode) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $6.00 / 1,000 whatsapp-ready leads

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

### What does WaReady ID do?

Get **WhatsApp-ready local leads** from Indonesian cities for outreach, market lists, or research. Pick a **city** and a **place type**, then download businesses you can actually message.

You get:

- A **place name** plus the city and category you asked for
- An Indonesian **mobile** in `+62` format when one is public
- A clickable **`wa.me`** link you can open in WhatsApp

```json
{
    "name": "Warung Sederhana",
    "city": "Jakarta",
    "category": "restaurant",
    "phone_e164": "+6281234567890",
    "wa_me": "https://wa.me/6281234567890",
    "lead_ready": true
}
```

Try the default input (**Jakarta restaurants**) on [Apify](https://console.apify.com/). Then export CSV or Excel, or pull the list from the Apify API.

The data comes from public [OpenStreetMap](https://www.openstreetmap.org/) places via the [Overpass API](https://overpass-api.de/). This is **not** a Google Maps scraper and it never logs into WhatsApp.

### Why use WaReady ID?

Most map dumps give you pins. This Actor gives you **numbers you can open in WhatsApp**.

- **Lead-gen and outreach teams** — build city lists for restaurants, clinics, hotels, salons, and shops, then click `wa.me` into a campaign.
- **Local SEO and listing shops** — collect consistent packs for 22 Indonesian cities, from Jakarta and Surabaya to Semarang, Makassar, and Batam.
- **Researchers and operators** — keep callable places (name, phone, address), not just coordinates.

On Apify you also get **scheduling**, **API access**, **integrations** (Make, n8n, Zapier), run monitoring, and **pay-per-event** billing so you only pay for WhatsApp-ready rows.

### What data can WaReady ID extract?

| Field               | What it means                                                 |
| ------------------- | ------------------------------------------------------------- |
| `name`              | Place name                                                    |
| `city` / `category` | The pack you selected                                         |
| `phone_e164`        | Indonesian **mobile** (`+628…`), or empty if it is a landline |
| `wa_me`             | `https://wa.me/628…` when the number is a mobile              |
| `lead_ready`        | `true` only when both the mobile and the WhatsApp link exist  |
| `address`           | Street address when OpenStreetMap has one                     |
| `lat` / `lon`       | Map coordinates                                               |
| `osm_url`           | Link to the public OpenStreetMap page                         |

Landlines (`021`, `031`, and similar) stay in the file so you can see coverage. They are marked `lead_ready: false` and you are **not** billed for them.

### How to scrape WhatsApp-ready Indonesia leads

1. Open the Actor in [Apify Console](https://console.apify.com/).
2. On the **Input** tab, pick a **city** and **category** (defaults: Jakarta restaurants).
3. Set **Max places** (1–500, default 50) if you want a smaller sample.
4. Click **Start**. When the run finishes, open the **Output** tab.
5. Download **JSON, HTML, CSV, or Excel**, or pull items from the dataset API.

No coding is required for a first run. Developers can start the same Actor from the **API** tab.

### How much will it cost to scrape Indonesian local leads?

You pay **only for WhatsApp-ready rows**. The billed event is **`lead_ready`** — one charge per place that has a `+62` mobile and a `wa.me` link.

Failed runs and landline-only rows are free.

**Example:** if the live price is **$0.006 per ready lead**, then **1,000 WhatsApp-ready leads cost $6**. Check the **Pricing** tab for the exact rate.

A 15–50 place sample is a cheap way to confirm a city before you scale. Runs are HTTP-only (no browser). Memory is capped at 256–1024 MB so compute stays predictable.

### Input

See the **Input** tab for the full form. You only need a city and a category.

| Field      | Options                                                                                                                                                                                                                    |
| ---------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| City       | Jakarta, Surabaya, Bandung, Semarang, Yogyakarta, Surakarta, Malang, Medan, Palembang, Pekanbaru, Padang, Bandar Lampung, Jambi, Makassar, Manado, Denpasar, Mataram, Samarinda, Balikpapan, Banjarmasin, Pontianak, Batam |
| Category   | Restaurant, cafe, hotel, clinic, salon, gym, spa, shop                                                                                                                                                                     |
| Max places | 1–500 (default 50). The list can include landlines; you only pay for ready rows.                                                                                                                                           |

```json
{
    "city": "Jakarta",
    "category": "restaurant",
    "maxItems": 15
}
```

### Output

You can download the dataset in various formats such as **JSON, HTML, CSV, or Excel**.

```json
{
    "name": "Warung Sederhana",
    "city": "Jakarta",
    "category": "restaurant",
    "phone_e164": "+6281234567890",
    "wa_me": "https://wa.me/6281234567890",
    "lead_ready": true,
    "address": "10 Jl. Melawai Jakarta",
    "lat": -6.244,
    "lon": 106.801,
    "osm_url": "https://www.openstreetmap.org/node/42"
}
```

A landline row looks the same except `phone_e164` and `wa_me` are empty and `lead_ready` is `false`.

### Tips and advanced options

- Start with **15–50 places** while you confirm coverage in a city.
- **Shop** is a broad filter and can take longer in Jakarta.
- Indonesian mobiles like `08xx`, `8xx`, `+62 8xx`, and `00 62 8xx` are normalized to `+628…`.
- Set a **max cost per run** in Console if you want a hard spend cap. The Actor stops when that limit is reached.

### MAMS HQ reporting

Each run can push telemetry to [MAMS HQ](https://github.com/dirga89/mams-dashboard) so Finance and Tech rooms stay current. Reporting is implemented in `src/mams.ts` and runs automatically when the env vars below are set. If they are unset, the Actor still works and ingest is skipped.

| Variable | Required | Purpose |
| -------- | -------- | ------- |
| `MAMS_URL` | Yes | HQ base URL (e.g. `https://your-mams.vercel.app`) |
| `MAMS_KEY` | Yes | Ingest key sent as `x-mams-key` header |
| `MAMS_SLUG` | No | Business slug in HQ (default `waready-id`) |
| `MAMS_PUSH_STATUS` | No | Set to `1` to POST lifecycle updates to `/api/ingest/status` |
| `MAMS_STATUS` | No | HQ status when `MAMS_PUSH_STATUS=1` (`building`, `launched`, etc.) |
| `MAMS_PUBLIC_URL` | No | Store or product URL for HQ |
| `MAMS_REPO_URL` | No | Git repo URL for HQ |
| `MAMS_LAUNCH_DATE` | No | `YYYY-MM-DD` launch date for HQ |

**What each run reports**

- **Heartbeat** — start and end of every run (`/api/ingest/heartbeat`)
- **Metrics** — `runs_count`, `items_out`, `leads_ready`, `run_failures`, `error_count`, `compute_cost_usd`, `revenue_usd` with per-run `dims` (`/api/ingest/metrics`)
- **Financials** — daily UTC revenue and compute cost, merged in the Actor KV store (`/api/ingest/financials`)
- **Status** — only when `MAMS_PUSH_STATUS=1` (`/api/ingest/status`)

Copy `.env.example` to `.env` for local `apify run`. On Apify Console, add the same keys under **Settings → Environment variables** (never commit live secrets).

### FAQ, disclaimers, and support

#### Does this scrape WhatsApp or Google Maps?

No. It reads **public OpenStreetMap** place tags. It does not scrape Google Maps and does not log into WhatsApp.

Our Actors do not extract private user data such as email addresses or gender. They only extract what has been shared publicly on OpenStreetMap. Results can still contain personal data (business phones). Personal data is protected by the GDPR in the European Union and by other regulations around the world. Do not scrape personal data unless you have a legitimate reason. If you are unsure, consult your lawyers.

#### Why are some rows not WhatsApp-ready?

OpenStreetMap often stores landlines. Those rows stay in the dataset so you can see coverage, but they are not charged.

#### Can I use this from Make, n8n, or my own API?

Yes. Use the **API** tab, or connect the Actor through Apify integrations. The dataset is the same list you see in Output.

#### Where do I report issues?

Use the Actor **Issues** tab. We aim to reply quickly.

# Actor input Schema

## `city` (type: `string`):

Which Indonesian city to search. Coverage is that city’s area on OpenStreetMap.

## `category` (type: `string`):

Type of place to collect. Shop is a broad filter and can take longer in large cities.

## `maxItems` (type: `integer`):

How many places to return this run (1–500). The list can include landlines. You only pay for WhatsApp-ready rows (Indonesian mobile + wa.me link).

## Actor input object example

```json
{
  "city": "Jakarta",
  "category": "restaurant",
  "maxItems": 15
}
```

# Actor output Schema

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

// Prepare Actor input
const input = {
    "city": "Jakarta",
    "category": "restaurant",
    "maxItems": 15
};

// Run the Actor and wait for it to finish
const run = await client.actor("masoncode/waready-id").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 = {
    "city": "Jakarta",
    "category": "restaurant",
    "maxItems": 15,
}

# Run the Actor and wait for it to finish
run = client.actor("masoncode/waready-id").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 '{
  "city": "Jakarta",
  "category": "restaurant",
  "maxItems": 15
}' |
apify call masoncode/waready-id --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,masoncode/waready-id"
        }
    }
}
```

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/M4OEt4XJIpW6Icub8/builds/VvTmoP9NL10qyQ6AU/openapi.json