Recipe: uses the API · Make
Owner names in Make scenarios, with HTTP and a webhook.
One scenario sends each business to LocalContact with Make's HTTP module. A second scenario receives the people who run it when the search finishes.
Updated
Can I use LocalContact with Make?
Short answer
Yes. In Make, a scenario with the HTTP module's Make a request sends each business name and address to the LocalContact API, along with a webhook address. A second scenario starts with Webhooks > Custom webhook and receives the names and job titles when the search finishes. It's a recipe, not a native Make app, and needs the LocalContact Scale plan.
How it works
LocalContact searches run in the background, so the recipe has two scenarios:
- Start: your trigger (a new row, a new CRM record, a form entry), then an HTTP request that sends the business to LocalContact with a
webhook_url. - Receive: a custom webhook that LocalContact posts the people to when the search finishes, then the modules that save them.
You need an API key from the LocalContact Scale plan.
1. Create the scenario that receives results
- Create a scenario and add Webhooks > Custom webhook as the first module.
- Click Add, name the webhook (for example “LocalContact results”) and save.
- Copy the webhook address Make shows. It looks like
https://hook.eu1.make.com/…. - Click Run once, so the webhook waits for its first data.
Keep the address private: anyone who has it can send data to your scenario.
2. Create the scenario that starts searches
- Create a second scenario with your trigger, for example Google Sheets > Watch New Rows.
- Add HTTP > Make a request and fill it in:
- URL:
https://server.localcontact.ai/api/v1/search - Method:
POST - Headers:
Authorization=Bearer <your API key> - Body content type:
application/json - Body input method: a JSON string
- Body content: the JSON below, with your trigger’s values mapped in place of the example values, and the webhook address from step 1
- Parse response: on
- URL:
{
"company": "Bramblewood Bakery",
"address": "12 Oak St, Austin, TX",
"titles": ["Owner", "Founder"],
"webhook_url": "https://hook.eu1.make.com/…"
}
LocalContact answers at once with status 202 and a task id. With Parse response on, you can save the task_id next to the row if you want to match results later.
3. Run one business to set the data structure
With the receiving scenario still waiting from step 1, run the starting scenario once with a real business. When the search finishes, LocalContact posts this to your webhook:
{
"task_id": "9b2f6c1e-…",
"status": "completed",
"company": "Bramblewood Bakery",
"location": "12 Oak St, Austin, TX",
"leads_count": 1,
"leads": [
{
"name": "Maria Lopez",
"title": "Owner",
"company_name": "Bramblewood Bakery",
"company_domain": "bramblewood.example",
"company_type": "Bakery",
"company_address": "Austin, US"
}
],
"completed_at": "2026-11-15T10:02:00+00:00"
}
(Example data: the business and the person are made up.) Make reads the shape of this data from the first run, so you can map leads, name and title in the next modules.
4. Write the people where you need them
- After the webhook, add Flow control > Iterator and choose
leads. Each person becomes one bundle. - Add the module that saves them, for example Google Sheets > Update a Row (find the row by
company) or a CRM’s create-contact module, and mapnameandtitle. - Add a filter before the iterator if you only want runs where
leads_countis more than 0. - Switch both scenarios on.
If something goes wrong
| What you see | What to do |
|---|---|
401 from LocalContact |
Check the header: Bearer, a space, then the key |
403 with a message about the plan |
API access needs an active Scale plan |
402 Insufficient credits |
Buy more credits |
422 with a list of errors |
A field is missing or too long: titles need 1 to 5 entries |
| Nothing reaches the webhook | Check the webhook_url in the body and that the scenario is on |
| A failed search | status is failed and leads is empty |
Make’s help centre lists limits on incoming webhooks, such as how many requests a webhook takes in a short time and the payload size. LocalContact sends one request per finished search. For every API field, see the API docs. Other recipes: Zapier, n8n and Google Sheets.
Questions
Still have questions? Contact us
Is there a LocalContact app in Make?
Not yet. This recipe uses Make's built-in HTTP and Webhooks apps to call the LocalContact API with your own API key.
What does it cost?
1 LocalContact credit per business searched, with every person found included, even when no one is found. Each scenario run also uses Make credits on your Make plan.
Why two scenarios instead of one?
A LocalContact search runs in the background. Rather than making Make wait and ask again, LocalContact posts the results to your webhook when the search finishes, which starts the second scenario straight away.
My webhook stopped working. Why?
Make's help centre says webhooks that aren't connected to any scenario for more than 5 days are turned off. Keep the receiving scenario connected and switched on.
Stop emailing info@. Find who actually decides.
Name and address in. The people who run the business out.