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.

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.

Prerequisites

Requirement	Notes
Coresignal API key	Log in to your account to locate your unique API key on the Self-service dashboard
Zapier account	Free tier is sufficient for setup and testing

Available actions

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

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

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.

Action	Filter fields
Find Employee	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
Find Company	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
Find Job	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)

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:

Data	Identifier field
Employee	Employee ID or profile URL/slug
Company	Company ID, profile URL/slug, or website/domain
Job	Job ID

• 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.

1

Get your Coresignal API key

Sign in to the Coresignal dashboard and copy your API key from the home screen.

2

Start building the Zap

1. In Zapier, click Create → Zaps.

   
2. Set the Trigger to HubSpot → New Company.

   
3. Click + Add Action and search for Coresignal.

4. Pick the action event, e.g. Find Company by ID.

3

Connect your Coresignal account

1. Click Sign in / Connect.

2. Paste in the API key from the Step 1 and continue.

   

Zapier will test the key automatically:

Result	What you'll see
Valid key	"Coresignal (Connected)"
Invalid key	"Invalid API key – please check your key at https://dashboard.coresignal.com/home"

4

Configure the lookup

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

   
2. Set Lookup By – Website/Domain.

   
3. Map the company website field from your HubSpot trigger into this field.

   
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)

5

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.

   

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

6

Send the enriched data back to HubSpot

1. Add another action: HubSpot → Update Company.

   
2. Map the Coresignal fields (industry, employee count, technologies, etc.) into the matching HubSpot company properties.

   

7

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.

Resources

Coresignal integrations

Find information about Coresignal integration in Zapier

Quickstart

Getting started with Zapier

API documentation

Coresignal API documentation