Recipe: uses the API · n8n
Owner names in n8n, in one workflow.
An HTTP Request node starts the search, a Wait node pauses until LocalContact posts the results back, and the next node saves the people who run the business.
Updated
How do I enrich leads with business owner names in n8n?
Short answer
Use an HTTP Request node to send each business name and address to the LocalContact API, with the Wait node's resume URL as the webhook_url. The Wait node pauses that run until LocalContact posts the results, then the next nodes split out the people and write their names and job titles to your sheet or CRM. It needs the LocalContact Scale plan.
How it works
n8n’s Wait node can pause a run until a URL is called. Its docs say the resume URL, $execution.resumeUrl, “is unique to each execution”. So the recipe passes that URL to LocalContact as the webhook_url. When the search finishes, LocalContact posts the people to it, and the same run carries on with the results. No second workflow, no polling.
You need an API key from the LocalContact Scale plan.
1. Add your trigger and the rows
Start with whatever brings in new businesses: a Schedule Trigger plus a Google Sheets read of rows without an owner, a CRM trigger, or a Webhook from your own form. Each item needs a business name and an address.
2. Start the search
Add an HTTP Request node:
- Method:
POST - URL:
https://server.localcontact.ai/api/v1/search - Authentication: Generic credential type, Header Auth, with the name
Authorizationand the valueBearer <your API key>. Storing the key as a credential keeps it out of the workflow itself. - Send Body: on, Body Content Type JSON, Specify Body using JSON:
{
"company": "{{ $json.Company }}",
"address": "{{ $json.Address }}",
"titles": ["Owner", "Founder"],
"webhook_url": "{{ $execution.resumeUrl }}"
}
Change Company and Address to your own column names. You can also paste the cURL example from the API docs into the node’s import option and edit it.
LocalContact answers at once with status 202 and a task id.
3. Wait for the results
Add a Wait node right after it:
- Resume: On Webhook Call
- HTTP Method:
POST - Limit Wait Time: on, for example 30 minutes, so a run never waits for ever
When the search finishes, LocalContact posts this body to the resume URL, and the Wait node passes it on:
{
"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.) Depending on your n8n version, the body may arrive under body. Check the Wait node’s output once and map from there.
4. Split out the people and save them
- Add an IF node: continue when
statusiscompletedandleads_countis more than 0. - Add a Split Out node on
leads, so each person becomes one item. - Add Google Sheets: Update Row (match on the company) or your CRM node, and map
nameandtitle.
Running it on a big list
Each search is one HTTP request and one paused run. For a few hundred rows, add a Loop Over Items node with a small batch size before the HTTP Request node. LocalContact allows 1,500 API requests per key per hour. For thousands of rows, a CSV upload in LocalContact is simpler.
If something goes wrong
| What you see | What to do |
|---|---|
401 from LocalContact |
Check the Header Auth value: 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 |
| The Wait node never resumes | LocalContact can’t reach your n8n: check it’s public over HTTPS |
Other recipes: Make, Zapier, Google Sheets and Clay.
Questions
Still have questions? Contact us
Is there a LocalContact node for n8n?
Not yet. This recipe uses n8n's built-in HTTP Request and Wait nodes with your own LocalContact API key.
Does it work on self-hosted n8n?
Yes, as long as LocalContact can reach your n8n instance's resume URL from the internet. If your n8n is only reachable inside your network, poll instead: wait a few minutes, then call GET /api/v1/tasks/{id}/results.
What does it cost?
1 LocalContact credit per business searched, with every person found included, even when no one is found. n8n's own pricing applies to your n8n plan or server.
What happens if a search fails?
LocalContact still posts to the resume URL, with status failed and an empty leads list. Add an IF node after the Wait node to handle it.
Stop emailing info@. Find who actually decides.
Name and address in. The people who run the business out.