# japan-restaurant-inbound-lead-finder (`aerodynamic_dockyard/japan-restaurant-inbound-lead-finder`) Actor

Find Japanese restaurants showing inbound demand and identify high-value multilingual website, booking, and conversion sales opportunities.

- **URL**: https://apify.com/aerodynamic\_dockyard/japan-restaurant-inbound-lead-finder.md
- **Developed by:** [Senoo Kazuyuki](https://apify.com/aerodynamic_dockyard) (community)
- **Categories:** Lead generation, Travel
- **Stats:** 1 total users, 0 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $50.00 / 1,000 results

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.

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

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Japan Restaurant Inbound Lead Finder

Find Japanese restaurants showing signs of inbound demand — and identify what multilingual website, booking, or conversion service may be worth offering them.

Built for agencies, freelancers, consultants, and sales teams targeting restaurants in Japan.

### What this Actor does

Japan Restaurant Inbound Lead Finder discovers restaurants and analyzes:

- Foreign-language review activity
- English, Chinese, and Korean website support
- Owned website availability
- Online reservation capability
- International booking providers
- Contact and inquiry paths
- Restaurant popularity and review volume
- Localization gaps
- Sales readiness

It turns those signals into a prioritized restaurant lead list with a recommended service for each prospect.

### Who is this for?

This Actor is useful for:

- Translation and localization agencies
- Web design agencies
- Inbound marketing agencies
- Restaurant marketing consultants
- Booking and reservation solution providers
- Freelancers selling multilingual services
- B2B sales teams targeting restaurants in Japan

### Example use cases

Find restaurants in Kyoto receiving foreign-language reviews but lacking English website support.

Find restaurants in Osaka with inbound demand but weak online reservation flows.

Find restaurants in Shibuya relying on Instagram, Tabelog, or other platforms instead of an owned website.

Build prospect lists for English, Chinese, or Korean localization services.

### Input

#### Location

Enter a Japanese city, ward, or neighborhood.

Examples:

- Kyoto, Japan
- Namba, Osaka, Japan
- Shibuya, Tokyo, Japan
- Asakusa, Tokyo, Japan

For large metropolitan areas, using a ward or neighborhood usually produces more focused results.

#### Restaurant type or name

Enter a restaurant type, cuisine, or specific restaurant name.

Examples:

- restaurant
- sushi restaurant
- ramen
- izakaya
- vegan restaurant
- halal restaurant

#### Number of leads

Choose how many restaurants you want returned after discovery and ranking.

#### Reviews analyzed per restaurant

Controls how many recent reviews are sampled for language-demand analysis.

20 is recommended for normal lead generation.

### Output

Each result can include:

- Restaurant name
- Sales Priority
- Sales Priority Score
- Recommended Service
- Recommendation Reasons
- Inbound Opportunity Score
- Inbound Demand Proxy Score
- Foreign-language review ratio
- Foreign review languages
- Rating
- Review count
- Restaurant category
- Address
- Phone number
- Website
- Google Maps URL
- Website type
- English support
- Chinese support
- Korean support
- Online reservation availability
- International booking provider detection

### Recommended services

Depending on the evidence found, the Actor may recommend opportunities such as:

- English website localization
- Chinese website localization
- Korean website localization
- Multilingual website development
- Online reservation flow
- Contact / inquiry conversion flow
- Multilingual conversion audit

Recommendations are only generated when enough supporting evidence is available.

If review-language data is too weak, the result may be marked as `NEEDS_REVIEW` instead of forcing a recommendation.

### How lead prioritization works

The Actor combines multiple signals rather than relying on a single metric.

It considers:

1. Restaurant popularity and review volume
2. Foreign-language review activity
3. Website ownership
4. Existing multilingual support
5. Reservation infrastructure
6. Contactability
7. Localization gaps
8. Overall sales fit

This helps distinguish restaurants with a meaningful sales opportunity from restaurants that simply have a weak website.

### Website recovery

Google Maps sometimes lists only Instagram, Tabelog, Facebook, or another platform even when a restaurant has an official website.

Japan Restaurant Inbound Lead Finder attempts to recover the official website and analyzes it when confidence is high enough.

Potential matches that cannot be verified confidently are not automatically promoted as the restaurant's official website.

### Inbound Demand Proxy

Foreign-language reviews are used as an **Inbound Demand Proxy**.

They provide evidence that a restaurant is receiving engagement from non-Japanese-language customers, but they do not prove that every reviewer is an international tourist.

This Actor is designed for lead discovery and prioritization, not as an official tourism statistics source.

### Recommended workflow

1. Search a specific Japanese location and restaurant type.
2. Sort or filter results by Sales Priority.
3. Review the recommended service and supporting evidence.
4. Open the restaurant website and Google Maps listing for final verification.
5. Use the qualified leads in your sales or outreach workflow.

### Example

A restaurant may have:

- Strong foreign-language review activity
- An owned Japanese-only website
- No English support
- No clear online reservation flow
- A phone number and contact path

The Actor may identify that restaurant as a strong sales prospect and recommend:

**English website localization + online reservation flow**

Instead of simply returning raw restaurant data, the goal is to answer:

**Who should I contact, why are they a prospect, and what service should I offer?**

### Notes

Results depend on publicly available restaurant, website, and review information.

Website structures and third-party listings can change over time, so final human verification is recommended before contacting a restaurant.

# Actor input Schema

## `city` (type: `string`):

Enter a city, ward, or neighborhood in Japan. For large cities, a specific area such as Shibuya, Tokyo, Japan is recommended.

## `category` (type: `string`):

Enter a restaurant type, cuisine, or specific restaurant name, such as restaurant, sushi restaurant, ramen, izakaya, or vegan restaurant.

## `maxPlaces` (type: `integer`):

Maximum number of restaurants to return after discovery and ranking.

## `reviewSampleSize` (type: `integer`):

Number of recent reviews sampled to estimate foreign-language demand. 20 is recommended.

## `reviewCandidateLimit` (type: `integer`):

Internal limit for restaurants analyzed for review-language demand.

## Actor input object example

```json
{
  "city": "Shibuya, Tokyo, Japan",
  "category": "sushi restaurant",
  "maxPlaces": 3,
  "reviewSampleSize": 20,
  "reviewCandidateLimit": 20
}
```

# Actor output Schema

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

Prioritized Japanese restaurant leads and their recommended inbound sales opportunities.

# 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 = {
    "city": "Kyoto, Japan",
    "category": "restaurant"
};

// Run the Actor and wait for it to finish
const run = await client.actor("aerodynamic_dockyard/japan-restaurant-inbound-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 = {
    "city": "Kyoto, Japan",
    "category": "restaurant",
}

# Run the Actor and wait for it to finish
run = client.actor("aerodynamic_dockyard/japan-restaurant-inbound-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 '{
  "city": "Kyoto, Japan",
  "category": "restaurant"
}' |
apify call aerodynamic_dockyard/japan-restaurant-inbound-lead-finder --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,aerodynamic_dockyard/japan-restaurant-inbound-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/MDVcWhPu4lHZxeMEY/builds/znzeBixQOCZM8Qp1B/openapi.json