Recipe: uses the API · Zapier

# Owner names in your Zaps, with two webhooks.

One Zap sends each new business to LocalContact. A second Zap catches the people who run it when the search finishes, and sends them wherever you like.

Updated 15 Nov 2026

[Read the API docs](https://localcontact.ai/docs/api) [Book a demo](https://localcontact.ai/demo)

## Can I use LocalContact with Zapier?

Short answer

Yes, with Webhooks by Zapier. One Zap sends each new business name and address to the LocalContact API with a webhook URL. A second Zap starts with Catch Hook and receives the names and job titles when the search finishes. There's no LocalContact app in Zapier yet, and Webhooks by Zapier needs a paid Zapier plan.

Recipe: uses the API

This is a recipe, not a native app: there is no LocalContact app in Zapier yet. You connect the two yourself with Zapier's own HTTP step and your LocalContact API key, which comes with the Scale plan.

## How it works

LocalContact searches run in the background, so the recipe uses two Zaps:

1. **The starting Zap** fires when a new business appears (a new spreadsheet row, a new CRM company, a form entry). It sends the business name and address to LocalContact, with a `webhook_url`.
2. **The catching Zap** fires when LocalContact posts the results to that URL, and sends the people wherever you need them.

You need a paid Zapier plan for Webhooks by Zapier, and the LocalContact Scale plan for an API key.

## 1. Create the Zap that catches results

1. Create a new Zap. For the trigger, choose **Webhooks by Zapier** and the event **Catch Hook**.
2. Copy the webhook URL Zapier gives you. It looks like `https://hooks.zapier.com/hooks/catch/…`.
3. Leave this Zap open: you’ll test it in step 3.

Keep the URL private. Anyone who has it can send data to your Zap.

## 2. Create the Zap that starts searches

1. Create a second Zap with the trigger you want, for example **Google Sheets: New Spreadsheet Row**.

2. Add the action **Webhooks by Zapier: Custom Request**. Zapier recommends Custom Request for JSON with a list in it, and the job titles are a list.

3. Fill it in:

   - **Method:** `POST`
   - **URL:** `https://server.localcontact.ai/api/v1/search`
   - **Headers:** `Authorization` = `Bearer <your API key>` and `Content-Type` = `application/json`
   - **Data:** the JSON below, with your trigger’s fields in place of the example values, and your catch hook URL

```
{
  "company": "Bramblewood Bakery",
  "address": "12 Oak St, Austin, TX",
  "titles": ["Owner", "Founder"],
  "webhook_url": "https://hooks.zapier.com/hooks/catch/…"
}
```

Zapier sends the Data field exactly as you type it, so check the JSON is valid. If a business name can contain double quotes, clean it in a Formatter step first.

LocalContact answers at once with a task id (`202`):

```
{ "cached": false, "task_id": "9b2f6c1e-…", "message": "Search task initiated successfully" }
```

## 3. Test with one business

Run the starting Zap once with a real business. When the search finishes, LocalContact posts a JSON body like this to your catch hook:

```
{
  "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.) In the catching Zap, click **Test trigger** to load it. If a search fails, `status` is `failed` and `leads` is empty.

## 4. Send the people where you need them

`leads` is a list, so Zapier shows it as line items. Add the actions you need:

- **Update the spreadsheet row:** look up the row by `company` and write the names and titles.
- **Create CRM records:** for example a contact per person with `name` and `title`, linked to the company.
- **Filter:** continue only when `leads_count` is greater than 0.

## If something goes wrong

| What you see                        | What to do                                                         |
| ----------------------------------- | ------------------------------------------------------------------ |
| `401` from LocalContact             | Check the Authorization header: `Bearer` and 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 catching Zap never runs         | Check the webhook URL in the Data field, and that the Zap is on    |

LocalContact retries a webhook a few times if your endpoint answers with a server error. For every field, see the [API docs](https://localcontact.ai/docs/api). Other recipes: [Make](https://localcontact.ai/integrations/make), [n8n](https://localcontact.ai/integrations/n8n) and [Google Sheets](https://localcontact.ai/integrations/google-sheets).

## Sources

- [Zapier: trigger Zaps from webhooks](https://help.zapier.com/hc/en-us/articles/8496288690317-Trigger-Zaps-from-webhooks)
- [Zapier: send webhooks in Zaps](https://help.zapier.com/hc/en-us/articles/8496326446989-Send-webhooks-in-Zaps)
- [Zapier pricing](https://zapier.com/pricing)
- [LocalContact API: start a single search](https://localcontact.ai/docs/api/start-search)

## Questions

Still have questions? [Contact us](https://localcontact.ai/contact)

Is there a LocalContact app in Zapier?

Not yet. This recipe uses Webhooks by Zapier to call the LocalContact API directly, with your own API key.

Which Zapier plan do I need?

Zapier's help centre says Webhooks by Zapier is available on its Professional, Team and Enterprise plans, not on Free. On the LocalContact side, API access comes with the Scale plan.

What does each search cost?

1 LocalContact credit per business, with every person found included, even when no one is found. Each Zap run also counts as Zapier tasks on your Zapier plan.

What if the search finds no one?

The catching Zap still runs: leads_count is 0 and leads is empty. Add a filter step if you only want to continue when someone was found.

## Stop emailing info\@. Find who actually decides.

Name and address in. The people who run the business out.

[Find the owner ](https://localcontact.ai/try)[Book a demo](https://localcontact.ai/demo)

Source: https://localcontact.ai/integrations/zapier · Updated: 2026-11-15
