A lead-generation agent that starts from a real place search

Start with the Google Maps lead recipe for a spreadsheet or HubSpot handoff, then use the Google Maps MCP setup when the agent should call the Actor directly. Add the lead-list skill when the agent needs a repeatable category-and-place workflow.

A lead agent needs three things: a bounded search, a clean output contract and a destination. The Google Maps recipes already validate the Actor input against its published schema and keep the destination credential outside the file.

Method

  1. Pick the category and place. Start with one city and one category, then check the output fields.

  2. Choose the destination. Use Google Sheets for a reviewable first pass, HubSpot for a CRM import or Slack for a team alert.

  3. Import the recipe or connect the MCP source. Replace the Apify token placeholder and the destination credential.

  4. Run a small batch, inspect the website and phone fields, then scale the search into smaller areas.

Recipes for this job

  • Google Maps leads to Google Sheets

    Pull local business leads from Google Maps into a Google Sheet on a schedule, with phone, website, rating…

    Google MapsGoogle Sheets

  • Google Maps leads to HubSpot

    Send a Google Maps business search into HubSpot as contacts, one contact per place with its name, phone…

    Google MapsHubSpot

  • Eventbrite events to Google Sheets

    List upcoming Eventbrite events for a city or category in a Google Sheet with date, venue, coordinates and…

    EventbriteGoogle Sheets

MCP servers for this job

Skills for this job

Guardrails

  • A Maps list has a result ceiling; split the area and deduplicate by place ID.
  • A missing website tag is a research signal, not a qualified sales fact.
  • Business contact data still carries outreach and privacy rules. Check the destination market before sending.

Questions

Can the agent run a Google Maps search by itself?

The MCP setup lets a compatible client call the selected Actor with an input. The recipe path is better when you want a fixed schedule and a known destination. Both still require your own Apify token and a valid input.

Does the recipe verify emails or phone numbers?

No. It moves the fields the Actor returns. Email enrichment is a separate step and a separate source. Validate any contact field before outreach.

Why use a skill instead of only a recipe?

A recipe is a fixed automation. A skill gives the agent a repeatable instruction set and a script for a task such as a category-and-place lead list. Use the one that matches how the agent is invoked.