# Restaurant Lead Finder (`george.the.developer/restaurant-lead-finder`) Actor

Find restaurants in any city with verified contacts, validated emails, and lead scores. Built for restaurant tech, delivery platforms, and POS companies.

- **URL**: https://apify.com/george.the.developer/restaurant-lead-finder.md
- **Developed by:** [George Kioko](https://apify.com/george.the.developer) (community)
- **Categories:** Lead generation
- **Features:** Limited permissions
- **Stats:** 33 total users, 0 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $400.00 / 1,000 restaurant search completeds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Restaurant Lead Finder - Food & Beverage Marketing Leads

Find, enrich, and score restaurant leads from Google Maps. Built for restaurant tech companies, delivery platforms, and POS companies who need verified contact data and qualified lead lists.

### What it does

1. **Scrapes Google Maps** for restaurants matching your search query
2. **Enriches each restaurant** with website data, emails, and social profiles
3. **Validates emails** to ensure deliverability
4. **Scores and ranks leads** using a restaurant-tuned scoring algorithm where reviews and social presence matter most

### Why this exists

Restaurants live and die by reviews and social media. Generic lead scrapers weight phone and email equally, but in F\&B, a restaurant with 500 reviews and active Instagram is a far better lead than one with just an email. This tool scores restaurants the way the industry actually works.

### Input examples

```json
{
    "searchQuery": "restaurants in Austin TX",
    "maxResults": 50,
    "enrichWebsites": true,
    "validateEmails": true,
    "minRating": 3.5
}
```

More search queries that work well:

- `"Italian restaurants San Francisco"`
- `"coffee shops Portland OR"`
- `"sushi restaurants New York"`
- `"Mexican restaurants Los Angeles"`
- `"pizza places Chicago"`
- `"fine dining restaurants Miami"`

### Output fields

| Field | Description |
|-------|-------------|
| `rank` | Position in scored results (1 = best lead) |
| `leadScore` | 0-100 quality score tuned for restaurant vertical |
| `restaurantName` | Restaurant name |
| `vertical` | Always `"restaurant"` |
| `category` | Google Maps category (cuisine type) |
| `address` | Full street address |
| `phone` | Phone number |
| `website` | Restaurant website URL |
| `rating` | Google Maps rating |
| `reviewCount` | Number of Google reviews (heavily weighted) |
| `emails` | Array of found emails with validation status |
| `socialProfiles` | Instagram, Facebook, TikTok, etc. |
| `enrichment` | Raw website enrichment data |
| `aiAnalysis` | AI-powered sales intelligence (optional) |

### Scoring algorithm (restaurant-tuned)

| Signal | Points | Why |
|--------|--------|-----|
| Has phone | +15 | Reservations and orders |
| Has website | +15 | Online presence baseline |
| Has email | +15 | Outreach channel |
| Email validated | +10 | Deliverable = actionable |
| Rating >= 4.0 | +20 | Rating is everything in F\&B |
| Rating >= 4.5 | +5 bonus | Top-tier restaurant |
| Reviews > 50 | +15 | Reviews are KING for restaurants |
| Reviews > 200 | +10 bonus | High-volume established venue |
| Social profiles | +10 | Social is critical for F\&B marketing |

### Pricing

**$0.50 per search**, charged once as the search-completed event after the run finishes. Each search scrapes, enriches, validates, and scores up to your `maxResults` limit. There is no start fee, and a run that fails before finishing is not charged.

### Who this is for

- Restaurant marketing agencies
- POS system sales teams (Toast, Square, Clover)
- Delivery platform partnerships (DoorDash, UberEats, Grubhub)
- Restaurant tech companies (reservation systems, loyalty apps)
- Food photography and branding agencies
- Restaurant supply companies

### Architecture

```mermaid
graph TD
    A[Search Query] --> B[Google Maps Scraper]
    B --> C[Website Enricher]
    C --> D[Email Validator]
    D --> E[Restaurant Lead Scorer]
    E --> F[Ranked Lead List]
    F --> G[Optional: AI Analysis]
```

***

### More lead-gen tools by this developer

- **[LinkedIn Company Employees Scraper](https://apify.com/george.the.developer/linkedin-company-employees-scraper)** — verified current employees + emails for any company, no login
- **[Google Maps Lead Scraper + Website Audit](https://apify.com/george.the.developer/google-maps-leads-website-audit)** — local business leads with contacts and an A-F website audit score
- **[Shopify DTC Brand Discovery](https://apify.com/george.the.developer/shopify-dtc-brand-discovery)** — find Shopify stores by niche with tech stack, contacts, and pitch angles
- **[Company Enrichment API](https://apify.com/george.the.developer/company-enrichment-api)** — turn any domain into a company profile: tech stack, socials, emails, DNS
- **[Email Validator API](https://apify.com/george.the.developer/email-validator-api)** — verify scraped emails before outreach (MX, disposable, syntax)

# Actor input Schema

## `searchQuery` (type: `string`):

What to search on Google Maps. Include location for best results.

## `maxResults` (type: `integer`):

Maximum number of businesses to scrape from Google Maps.

## `enrichWebsites` (type: `boolean`):

Enrich each business with website contact data, social profiles, and technologies.

## `validateEmails` (type: `boolean`):

Validate all discovered email addresses for deliverability.

## `minRating` (type: `number`):

Only include businesses with this rating or higher. Set to 0 to include all.

## Actor input object example

```json
{
  "searchQuery": "restaurants in Austin TX",
  "maxResults": 20,
  "enrichWebsites": true,
  "validateEmails": true,
  "minRating": 0
}
```

# Actor output Schema

## `results` (type: `string`):

Rows of this run's dataset in the Overview table view, with rank, lead score, restaurant name, vertical, category, address, phone and website.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "searchQuery": "restaurants in Austin TX"
};

// Run the Actor and wait for it to finish
const run = await client.actor("george.the.developer/restaurant-lead-finder").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "searchQuery": "restaurants in Austin TX" }

# Run the Actor and wait for it to finish
run = client.actor("george.the.developer/restaurant-lead-finder").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "searchQuery": "restaurants in Austin TX"
}' |
apify call george.the.developer/restaurant-lead-finder --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,george.the.developer/restaurant-lead-finder"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/1dXgeEiI8EAzmQMYW/builds/wn6HTDdbvPtguH6IW/openapi.json