Recipe: uses the API · Clay
Owner names in Clay, even for rows with no website.
Add LocalContact as an HTTP API column. Send each row's business name and address, get the people who run it back as JSON.
Updated
Can I get owner names in Clay for rows with no website?
Short answer
Yes. Add an HTTP API column that sends each row's business name and address to the LocalContact API, then a second column that reads the results and maps the names and job titles into your table. LocalContact searches for the business itself, so rows with no website or domain work too. It needs the Scale plan.
Use it with Clay, not instead of it
Clay is good at building workflows from many data providers. The rows it struggles with are local businesses with no website and no LinkedIn page, because most people-finding steps start from a domain. LocalContact fills those rows: it starts from the business name and address.
1. Get an API key
API access comes with the Scale plan. In LocalContact, open API and create a key for Clay. Keep it in Clay’s secret fields, never in a shared column.
2. Start the search
Add an HTTP API column with:
- Method:
POST - URL:
https://server.localcontact.ai/api/v1/search - Headers:
Authorization: Bearer <your API key>andContent-Type: application/json - Body: the row’s business name and address, and the job titles you want:
{
"company": "Bramblewood Bakery",
"address": "Austin, TX",
"titles": ["Owner", "Founder"]
}
Insert your table’s name and address columns in place of the example values. The API answers at once with a task id:
{ "cached": false, "task_id": "9b2f6c1e-…", "message": "Search task initiated successfully" }
3. Read the people
Add a second HTTP API column that calls:
- Method:
GET - URL:
https://server.localcontact.ai/api/v1/tasks/{task_id}/results, with the task id from the first column - Headers: the same
Authorizationheader
When the search has finished, it returns the people:
{
"data": [
{
"name": "Maria Lopez",
"title": "Owner",
"company_name": "Bramblewood Bakery",
"company_domain": "bramblewood.example",
"company_type": "Bakery",
"company_address": "Austin, US"
}
],
"meta": { "total": 1, "page": 1, "per_page": 20, "last_page": 1 }
}
(Example data: the business and the person are made up.)
If you call it too early you get a 422 (results not ready): run the column again a little later. For big tables, send a webhook_url in step 2 instead, and LocalContact posts the results to it when each search finishes.
4. Map the fields
Map name and title into new columns, one per person or as a list. company_domain and company_type are useful for checking you got the right business.
Clay or LocalContact on its own?
If you don’t use Clay already, you don’t need it for this: upload a CSV to LocalContact and download the people. If you do, keep Clay for the workflow and use LocalContact for the rows other providers can’t fill. See the API docs for every field, and API and Clay builders for more ways people use it.
Questions
Still have questions? Contact us
Why do rows with no website fail in Clay?
Many people-finding steps start from a company's website or domain, so a row without one has nothing to start from. Clay's own Google Maps guide says rows without a website won't run its website research step. LocalContact starts from the business name and address instead.
Is this an official Clay integration?
No. It uses Clay's HTTP API column, which can call any API. You bring your own LocalContact API key.
What does it cost?
1 LocalContact credit per business searched, with every person found included, plus whatever Clay charges for running its own columns. API access comes with the Scale plan.
What if the results aren't ready yet?
A search runs in the background. If you read the results before it has finished, the API answers 422 (results not ready). Run the second column again a little later, or send a webhook_url so the results are posted to you when they're ready.
Stop emailing info@. Find who actually decides.
Name and address in. The people who run the business out.