> For the complete documentation index, see [llms.txt](https://docs.coresignal.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coresignal.com/integrations/zapier.md).

# Zapier

## Overview

Zapier allows to connect Coresignal's employee, company, and job data to over **9,000 Zapier apps** – no code required. You can use it two ways:

* **Enrich** records you already have (a contact, a company domain, a job ID)
* **Discover** new records that match a set of filters

Once Coresignal fetches the data, you can route it anywhere in your Zapier workflow, like a CRM, a spreadsheet, Slack, a database, or any other connected app.

{% hint style="warning" %}

#### Only action steps available

Coresignal does not provide a trigger in Zapier, thus it cannot initiate a Zap. Every Zap using Coresignal must begin with a trigger from another app (schedule, new CRM record, new spreadsheet row, webhook, etc.), with Coresignal invoked as an action step.
{% endhint %}

## Prerequisites

<table><thead><tr><th width="200.4453125">Requirement</th><th>Notes</th></tr></thead><tbody><tr><td>Coresignal API key</td><td>Log in to your account to locate your unique API key on the Self-service <a href="https://dashboard.coresignal.com/home">dashboard</a></td></tr><tr><td>Zapier account</td><td>Free tier is sufficient for setup and testing</td></tr></tbody></table>

## Available actions

The integration exposes 7 actions, grouped into three patterns: Find (search), Find by ID (enrich), and AI Prompt search.

<table data-search="false"><thead><tr><th>Action</th><th>Data</th><th>Description</th></tr></thead><tbody><tr><td>Find Employee</td><td>Employee</td><td>Finds employees matching your filters or an Elasticsearch query. Returns a preview of profiles</td></tr><tr><td>Find Employee by ID</td><td>Employee</td><td>Retrieves one full employee profile by Coresignal ID or profile URL/slug</td></tr><tr><td>Find Company</td><td>Company</td><td>Finds companies matching your filters or an Elasticsearch query. Returns a preview of profiles</td></tr><tr><td>Find Company by ID</td><td>Company</td><td>Retrieves one full company profile by Coresignal ID, profile URL/slug, or website/domain</td></tr><tr><td>Find Job</td><td>Jobs</td><td>Finds job postings matching your filters or an Elasticsearch query. Returns a preview of postings</td></tr><tr><td>Find Job by ID</td><td>Jobs</td><td>Retrieves one full job posting by Coresignal job ID</td></tr><tr><td>Find Employee by AI prompt</td><td>Employee</td><td>Turns a plain-English prompt into a query; either returns the generated query or runs it and returns matching employees</td></tr></tbody></table>

### How the "Find" actions work

"Find Employee", "Find Company", and "Find Job" actions share the same set of controls.

**Search input mode**

* **Filters** (default) – fill in guided fields. Best for most users.
* **Elasticsearch DSL Query** – paste an Elasticsearch DSL JSON object for full control. Each data type has a "build & test your query" playground link available inline.

**Output mode**

* **Preview** (default) – returns up to 20 records with fields, ready to map into your next step or loop over. It includes a **Page** selector, which pages through 20 results at a time (Results 1–20, 21–40, … 81–100). Pair this with Looping by Zapier to walk through multiple pages of results.
* **IDs only** – returns up to 1,000 matching IDs with no field data. This is meant to feed a follow-up "Find … by ID" step for full enrichment, or to loop over at scale.

#### Filter fields per action

Find listed filter fields available for each action.

<table><thead><tr><th width="200.3828125">Action</th><th>Filter fields</th></tr></thead><tbody><tr><td>Find Employee</td><td>Full name · Current job title · Company name · Company website · Country · City · Department · Decision makers only (toggle) · Currently employed only (toggle) · Changed job after (date) · Exclude headline keywords</td></tr><tr><td>Find Company</td><td>Company name · Website domain · Industry · HQ Country · HQ City · Last funding round type · Technologies used · Founded year (min/max) · Employee count (min/max) · Active job postings</td></tr><tr><td>Find Job</td><td>Job title keywords · Company name · Company domain · Country · City · Description keywords · Seniority · Employment type · Remote accepted (toggle) · Easy apply only (toggle) · Date posted after (date) · First seen after (date)</td></tr></tbody></table>

### How the "Find by ID" actions work

"Find Employee by ID", "Find Company by ID", and "Find Job by ID" actions also share the same controls:

* **Identifier field** – what you use depends on the data type:

<table><thead><tr><th width="199.9296875">Data</th><th>Identifier field</th></tr></thead><tbody><tr><td>Employee</td><td>Employee ID or profile URL/slug</td></tr><tr><td>Company</td><td>Company ID, profile URL/slug, or website/domain</td></tr><tr><td>Job</td><td>Job ID</td></tr></tbody></table>

* **Output format**
  * **Mapped fields** (default) – the full profile flattened into individual fields you can map one by one into downstream steps.
  * **JSON** – the complete API response as a single JSON string, useful for developers or for storing the whole record.
* **Hide Empty Fields** (toggle) – when on, strips out null/empty fields so the output stays clean.

### How the "Find Employee by AI prompt" work

Instead of filling in filter fields, you describe who you're looking for in plain English, and Coresignal converts that into a structured query.

* **Prompt** – your plain-English description
* **Return Data** (toggle)
  * Off – returns only the generated query (useful if you want to inspect or reuse it)
  * On – runs the query and returns matching employee records. A **Limit** appears only when **Return Data** is on and sets how many records to return (1–100)

## Setup guide

This guide shows how to set up a Zap that runs automatically: **whenever a new company is created in HubSpot, Coresignal enriches it with B2B data**.

{% stepper %}
{% step %}

### Get your Coresignal API key

Sign in to the [Coresignal dashboard](https://dashboard.coresignal.com/home) and copy your API key from the home screen.
{% endstep %}

{% step %}

### Start building the Zap

1. In Zapier, click **Create → Zaps**.<br>

   <figure><img src="/files/P7TWoPGjA7ChHsMNeru6" alt=""><figcaption></figcaption></figure>
2. Set the **Trigger** to **HubSpot → New Company**.

   <figure><img src="/files/fjjGV278dH2RqL7jejeu" alt="" width="563"><figcaption></figcaption></figure>
3. Click **+ Add Action** and search for **Coresignal**.
4. Pick the action event, e.g. Find Company by ID.
   {% endstep %}

{% step %}

### Connect your Coresignal account

1. Click **Sign in / Connect**.
2. Paste in the API key from the **Step 1** and continue.<br>

   <figure><img src="/files/FsqutOcdJRCFNizIyJrS" alt="" width="494"><figcaption></figcaption></figure>

Zapier will test the key automatically:

<table><thead><tr><th width="200.0390625">Result</th><th>What you'll see</th></tr></thead><tbody><tr><td>Valid key</td><td>"Coresignal (Connected)"</td></tr><tr><td>Invalid key</td><td>"Invalid API key – please check your key at <a href="https://dashboard.coresignal.com/home">https://dashboard.coresignal.com/home</a>"</td></tr></tbody></table>
{% endstep %}

{% step %}

### Configure the lookup

1. Select the action event. Example for Find Company by ID.<br>

   <figure><img src="/files/m4m0v6WoXgVvk2gowYRp" alt="" width="563"><figcaption></figcaption></figure>
2. Set **Lookup By** – `Website/Domain`.<br>

   <figure><img src="/files/lduQu9dH6OckIvvaSS6K" alt="" width="563"><figcaption></figcaption></figure>
3. Map the **company website** field from your HubSpot trigger into this field.<br>

   <figure><img src="/files/rnG6Q1Ep0p04VIXoghG4" alt="" width="488"><figcaption></figcaption></figure>
4. Configure selected action.\
   For Find actions choose:

   * **Search Input** – Filters or Elasticsearch DSL
   * **Output Mode** – Preview or IDs only

   For Find by ID actions choose:

   * **Output Format** – `Mapped Fields` (easier to map into other apps) or `Raw JSON` (full response, for developers)
   * **Hide Empty Fields** – turn on to skip blank fields in the result (optional)
     {% endstep %}

{% step %}

### Test it

1. Click **Test step**. Zapier calls Coresignal and shows you a real enriched record.
2. Check that the fields you actually need (industry, size, funding, etc.) came back.<br>

   <figure><img src="/files/XGyynBLCRHM25yMXZCVj" alt="" width="494"><figcaption></figcaption></figure>

If nothing comes back, double-check the domain being passed in – a missing or malformed website field is the most common cause.
{% endstep %}

{% step %}

### Send the enriched data back to HubSpot

1. Add another action: **HubSpot → Update Company**.<br>

   <figure><img src="/files/nQUJjBhBBmmlXNmUOUcx" alt="" width="563"><figcaption></figcaption></figure>
2. Map the Coresignal fields (industry, employee count, technologies, etc.) into the matching HubSpot company properties.<br>

   <figure><img src="/files/EDJHD0k8v2trhxe7xYOJ" alt="" width="563"><figcaption></figcaption></figure>

{% endstep %}

{% step %}

### Turn it on

1. Name the Zap (e.g. "HubSpot Company Enrichment").
2. Toggle it **On**.
3. Check **Zap History** after a day or two to confirm new companies are being enriched correctly.
   {% endstep %}
   {% endstepper %}

## Resources

<table data-view="cards"><thead><tr><th></th><th></th></tr></thead><tbody><tr><td><a href="https://zapier.com/apps/coresignal/integrations"><strong>Coresignal integrations</strong></a></td><td>Find information about Coresignal integration in Zapier</td></tr><tr><td><a href="https://zapier.com/blog/get-started-with-zapier/"><strong>Quickstart</strong></a></td><td>Getting started with Zapier</td></tr><tr><td><a href="/spaces/cyJAXlZjTKSLvAQjb9rM/pages/owCN1BxUUgsInkeOZj4P"><strong>API documentation</strong></a></td><td>Coresignal API documentation</td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.coresignal.com/integrations/zapier.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.