Google Maps Postcode Filter — ZIP & Postal Territories

Filter Google Maps leads by ZIP code or postcode prefix

Keep only the businesses in your postal territory. Select an existing Apify dataset, enter codes such as T6R*, SW1A* or 02108, and download the matching leads plus an audit of every rejected row. Existing Google Maps scraper output works with the default postalCode field.

Run the included synthetic example first: it keeps one row, rejects one excluded postcode, rejects one outside the territory and identifies one missing postcode. Replace the example with your own completed dataset to process real leads. This Actor processes data already collected; it does not scrape Google Maps or pay another Actor to collect it.

Why use it?

Prepare territory-specific CRM imports without spreadsheet formulas, repeated filtering or another scraping run. Combine multiple postcode prefixes, subtract exact postcodes or smaller prefixes, and see why each record passed or failed. An optional country filter prevents identical postal codes in different countries from being mixed.

Use the Actor through the Apify API, scheduled tasks or integrations after your scraper finishes. All processing stays in your Apify run. No external enrichment service, LLM, geocoder or API key is required.

How to use it

1. Select a completed source dataset in Dataset to filter. This overrides the example rows.
2. Replace Include postcodes with your exact codes or prefixes ending in *.
3. Optionally add exclusions and two-letter country codes.
4. Run and open Kept leads — CSV or Kept leads — JSON in the output.
5. Check the summary and audit before importing into your CRM.

Input

{
  "includePostcodes": ["T6R*"],
  "excludePostcodes": ["T6R 0A1"],
  "countryCodes": ["CA"],
  "data": [
    {"title":"Synthetic Example","postalCode":"t6r 2v4","countryCode":"CA"}
  ]
}

For real data, set datasetId instead of data. Change postcodeField or countryField for other scraper schemas; dotted paths such as address.postcode are supported. The default fields are postalCode and countryCode.

Spaces, hyphens and letter case are normalized. T6R* means any normalized code starting with T6R. T6R 2V4 is an exact match. Wildcards anywhere except the end are rejected. Exclusions always win. ZIP+4 requires an explicit prefix if the extension should match, for example 02108*.

Output

KEPT.json contains matching records. Each has sourceRow, status, title, placeId, postalCode, normalizedPostcode, countryCode, matchedPatterns, excludedPatterns, website, phone, and the complete original record.

AUDIT.json contains every input row with its decision. CSV versions of both files are provided; potentially active spreadsheet cells are escaped. SUMMARY and the default dataset contain row counts and rejection totals. An empty result is valid and still produces a completed report and CSV headers.

Status	Meaning
kept	Included and not excluded
excluded_postcode	Matched an exclusion
outside_postcode_selection	No inclusion matched
country_not_allowed	Country did not match the requested countries
missing_or_invalid_postcode	No usable text postcode; numeric codes are not guessed

Pricing

$0.05 per completed filtering report, including up to 10,000 input rows and all four exports. A report with zero matching leads is also a completed report. Invalid input does not trigger the custom event. Check the Pricing tab for the active rate and any platform charges. Running your own Actor for development is not evidence of a customer sale.

Limits and support

Use completed datasets containing at most 10,000 rows and 10 MiB. Every page is read; oversize or changing sources fail instead of silently returning a partial report. The Actor reads only the selected dataset and its own run storage. Inline data are supported for API and one-off use.

Postcode matching uses the supplied data. It does not verify postal validity, street addresses, service areas or geographic boundaries, and does not deduplicate businesses. Preserve leading zeros by storing postcodes as text. Missing country values are rejected when country filtering is enabled. A selected dataset takes precedence over the sample rows, but never changes your filter settings.

Report reproducible problems through the Issues tab with a small synthetic example. Do not include API keys or private lead data in public issues.