What output columns are included?

name, address, phone, website, email (empty if not found), rating, place_id, google_maps_url.

How are duplicates handled?

Duplicates are removed by place_id; perform batch enrichment in small chunks (10–50) to avoid timeouts.

What are the key preconditions and costs?

mcporter must be configured with the google-maps server; GOOGLE_MAPS_API_KEY must be available; openpyxl required for XLSX; expect costs from search calls and place details enrichment; report rough run cost and note free-tier caveats.

Google Maps Leadgen

Scanned

@Realowg

npx machina-cli add skill @Realowg/google-maps-leadgen-skill --openclaw

Files (1)

SKILL.md

2.1 KB

Google Maps Lead Generation (MCP)

Use this skill to run repeatable lead-gen batches from Google Maps via MCP.

Preconditions

mcporter configured with server google-maps.
Server key in env (GOOGLE_MAPS_API_KEY) must be server-compatible (no browser referrer restriction).
For XLSX output, openpyxl available in venv.

Fast workflow

Build query set from geography + target verticals.
Run maps_search_places for each query.
Keep only in-target geography, dedupe by place_id.
Enrich each place with maps_place_details.
Export CSV or XLSX.
If user asks for file in Telegram, send with message tool action=send + media path.

Query strategy

Use focused terms instead of broad generic terms.

Good: "odoo partner <city> <country>", "erp integrator <city> <country>", "logistics company <city> <country>"
Avoid huge overlapping lists in one run; do batches.

Required output columns (V2)

name
address
phone
website
email (empty if not discoverable)
rating
place_id
google_maps_url (mobile-safe):
- https://www.google.com/maps/search/?api=1&query=<NAME>&query_place_id=<PLACE_ID>

Cost notes

Search calls are usually main paid SKU driver.
Place details add enrichment cost.
Report rough run cost estimate and mention free-tier caveat.

Reliability guardrails

Batch enrich in small chunks (10–50) to avoid long-running timeouts.
Add retries for transient failures.
Never commit API keys or sensitive exports.

Delivery rules

If user asks for CSV/XLSX file in chat: send via message tool (media path).
If user asks specifically for XLSX formatting/edits, use xlsx workflow standards.
Keep summary concise: count, coverage (with_phone, with_website, with_email), file path/name.

Source

git clone https://clawhub.ai/Realowg/google-maps-leadgen-skillView on GitHub

Overview

Generates B2B leads from Google Maps using a self-hosted MCP server named google-maps and exports results to CSV or XLSX. It supports lead generation by country, city, or industry, with phone/website/email enrichment and deduplicated lists, and can deliver files back in chat (e.g., Telegram).

How This Skill Works

Build a geography + vertical query set, run maps_search_places for each query, keep only targets and dedupe by place_id, enrich with maps_place_details, and export as CSV or XLSX. If delivering in chat, use the message tool with a media path to send the file.

When to Use It

You need B2B leads generated by country, city, or industry using Google Maps data.
You want phone, website, and email enrichment attached to each lead.
You require deduplicated lead lists to avoid repeated contacts.
You plan to export results as CSV or XLSX for downstream workflows.
You want the resulting lead file delivered back in chat (e.g., Telegram).

Quick Start

Step 1: Build a query set from geography (city/country) and target verticals (industry).
Step 2: Run maps_search_places for each query, dedupe by place_id, and enrich with maps_place_details.
Step 3: Export to CSV or XLSX and deliver via chat if needed (use media path for the file).

Best Practices

Use focused query terms like 'erp partner <city> <country>' or 'logistics company <city> <country>'.
Batch queries in small chunks (10–50 items) to avoid timeouts during enrichment.
Deduplicate by place_id to ensure unique leads across batches.
Keep API keys secure (GOOGLE_MAPS_API_KEY) and monitor enrichment costs (place details).
When presenting results, report count and coverage (with_phone, with_website, with_email) and include the file path/name.

Example Use Cases

Identify ERP partners in New York, NY with phone numbers and emails.
Compile logistics companies in Singapore with websites and emails.
Target manufacturers in Berlin with contact details for partnerships.
Gather Odoo partners in Madrid and Barcelona with full contact data.
Aggregate IT services firms in Lagos including phone, website, and email.

Frequently Asked Questions

Add this skill to your agents