hexadatalabs/seccion-amarilla-business-scraper
hexadatalabs--seccion-amarilla-business-scraperDestructive
This tool calls the Actor "hexadatalabs/seccion-amarilla-business-scraper" and retrieves its output results. Actor description: Scrape Sección Amarilla (seccionamarilla.com.mx), Mexico's yellow pages: business name, category, full address, GPS, phone, WhatsApp, website, hours and payment methods. Search by keyword and city or state. Pay per result.
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "hexadatalabs--seccion-amarilla-business-scraper"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| city | No | City or municipality, for example "ciudad de mexico", "guadalajara", "monterrey", "puebla", "cancun". Leave empty to search all of Mexico. Results for a big city include its metro area. Example values: "ciudad de mexico" | |
| state | No | Mexican state, for example "jalisco", "nuevo leon", "estado de mexico". Combine with a city (state + city) or use it alone for a whole state. The site also lists some businesses from other states; strictLocation drops them. | |
| waitSecs | No | Max seconds (0–45, default 30) to cap the wait for the Actor run to reach terminal state. For long-running Actors the response returns at the cap with the current run status; follow `nextStep` to poll via get-actor-run. Set to 0 to fire-and-forget. | |
| startUrls | No | Full Sección Amarilla results URLs to scrape instead of (or in addition to) the queries above, for example https://www.seccionamarilla.com.mx/resultados/dentistas/guadalajara/1 or https://www.seccionamarilla.com.mx/resultados/ferreterias/jalisco/guadalajara/1. A text file with one URL per line is accepted too. Custom URLs are not filtered by city / state. | |
| maxResults | No | Stop after this many businesses in total (across all queries). You are charged per result, so this caps the cost. Example values: 100 | |
| includeEmail | No | Add the contact email published on the listing (business records only). Off by default; enable only if you need it and comply with the applicable data-protection and anti-spam laws. | |
| scrapeDetails | No | Open each business page to get the description, opening hours, payment methods, product/service tags, additional phone lines, branches, the logo/ad image and the official website. One extra request per business. Turn it off for a cheaper, listing-only run (name, category, address, coordinates, phone, WhatsApp, website). Example values: true | |
| searchQueries | No | Business categories or free keywords to search for, one per line, as written on seccionamarilla.com.mx (for example "restaurantes", "ferreterias", "hoteles", "talleres mecanicos"). Each one becomes a separate search. Example values: ["restaurantes"] | |
| maxConcurrency | No | Maximum parallel requests. Keep it low (2–5) to stay polite with the site. Example values: 3 | |
| strictLocation | No | The site pads city and state searches with businesses from other states (about 1 in 4 rows in a Monterrey, Nuevo León hotel test). When enabled, rows whose state is not the requested one (the state given, or the state of the city / metro area) are skipped before they count towards maxResults. Turn it off to keep every row the site returns. Example values: true | |
| onlyWithWebsite | No | Skip listings that do not publish any website (useful for lead generation). | |
| includeIndividuals | No | Some categories (dentists, doctors, lawyers...) contain professionals listed under their own name. By default those records are skipped. When enabled they are kept with publisherType "possible_individual" and WITHOUT phone, WhatsApp or email. Make sure you have a legal basis before enabling this. | |
| proxyConfiguration | No | Proxy to use. Apify proxies are recommended for reliable runs. Example values: {"useApifyProxy":true} |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| tip | No | Advisory guidance RAG Web Browser wrote to its key-value store under the reserved "TIP" key | |
| runId | Yes | Actor run ID | |
| stats | No | Run statistics | |
| status | Yes | Run status: READY | RUNNING | TIMING-OUT | TIMED-OUT | ABORTING | ABORTED | SUCCEEDED | FAILED | |
| actorId | Yes | Stable Apify Actor ID from the run record | |
| summary | Yes | Past-tense summary of the run state | |
| exitCode | No | Actor process exit code; populated for terminal states (especially FAILED) | |
| nextStep | Yes | One primary follow-up action with identifiers interpolated | |
| storages | Yes | Dataset and key-value store metadata, keyed by alias. "default" is always the primary entry. | |
| actorName | No | "username/actor-name" | |
| startedAt | No | ISO timestamp when the run started | |
| finishedAt | No | ISO timestamp when the run finished (terminal states only) | |
| statusMessage | No | Pass-through from Apify run.statusMessage | |
| apifyConsoleUrl | No | Personalized Apify Console link to the run; present only for Console sessions |