Leadmaps for Make — no-code lead pipelines
Make’s HTTP module is all you need: authenticate with your Bearer key, call /v1/places with your filters, then iterate the data array into any of Make’s 1,500+ apps. Counting via /v1/places/count is free — use it to guard your scenarios.
Setup
- Create your API key at app.leadmaps.io/keys.
- Add an HTTP “Make a request” module: GET https://api.leadmaps.io/v1/places?category=plumber&city=Nantes.
- Header: Authorization: Bearer lm_live_xxx; parse the JSON response.
- Map data[] to Google Sheets, HubSpot or your outreach tool.
GET https://api.leadmaps.io/v1/places?category=plumber&city=Nantes&min_rating=4.5
Authorization: Bearer lm_live_xxx
-> { "data": [...], "pagination": { "next_cursor": "...", "has_more": true },
"meta": { "credits_charged": 20, "credits_free_dedup": 0 } }3 copy-paste prompts
Count plumbers rated ≥ 4.5 in Nantes, then deliver the top 20 with phone and website.Find 150 real-estate agencies in Lille rated ≥ 4.4 with a website, export to CSV.List categories around “food”, then count pizzerias without a website in the Rhône department.
MCP tools
| Tool | Cost |
|---|---|
count_places | Free — always call first |
search_places | 1 credit per place returned (30-day dedup free) |
get_place | 1 credit (dedup) |
list_categories | Free |
create_export | 1 credit per delivered row |
get_export_status | Free |
FAQ
Is there a native Leadmaps app for Make?
Not yet: the HTTP “Make a request” module is all you need (Bearer header + JSON response) and it is the documented path. A native app is under consideration based on demand.
How do I handle pagination in a Make scenario?
Loop on pagination.next_cursor until has_more=false (iterating HTTP module), or use create_export for large volumes: you get a single download URL.
How do I track credit consumption from Make?
Every response exposes meta.credits_charged (and the X-Credits-Charged header). Counting via /v1/places/count is free — use it as a guard before any paid call.