> 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/clay.md).

# Clay

## Overview

Clay is a platform for data enrichment and go-to-market automation: it enables teams to ingest data from over 200 providers into a spreadsheet-like table, enrich rows with this data, and then push the results to CRMs, sequencers, or ad platforms. Since Coresignal is one of the data providers, you can use the integration to access our fresh public company, employee, and job data.

Clay exposes Coresignal in two ways:

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th></tr></thead><tbody><tr><td><strong>Native actions</strong></td><td>Pre-built cards for Multi-Source Company Enrichment and Multi-Source Employee Enrichment.</td></tr><tr><td><strong>HTTP API</strong></td><td>A general-purpose Clay action that calls any REST endpoint. It gives you full control over the endpoint, the returned fields, and the headers sent.</td></tr></tbody></table>

This guide explains how to use the HTTP API to enrich a table of company domains with Coresignal's Multi-Source Company data. The same process applies to employee enrichment – use the employee endpoint instead.

## Prerequisites

<table><thead><tr><th width="200.09375">Requirement</th><th>Notes</th></tr></thead><tbody><tr><td>Clay account</td><td>Any plan that supports HTTP API enrichment or Growth plan and above to use native actions</td></tr><tr><td>Coresignal API key</td><td>Get your API key on the Self-service <a href="https://dashboard.coresignal.com/home">dashboard</a></td></tr></tbody></table>

## How to use

{% stepper %}
{% step %}

### Create a table

From the Clay home screen, open **Create** and choose **Blank table**, or **Import from CSV / CRM** if your domains already exist elsewhere. Your workbooks are available at **Home** **→ All Files**.

<img src="/files/GUSTgJIpVBXDpQCRa7Sl" alt="" width="563">

Add a column of company domains – one company per row, e.g. `tesla.com`, `google.com`, `openai.com`.
{% endstep %}

{% step %}

### Add the HTTP API enrichment

1. Click **+ Add column → Add enrichment**.
2. In the tools panel, search for **HTTP API**.

{% hint style="info" %}
Searching "Coresignal" in the tools panel also surfaces the native *Multi-Source Company Enrichment* and *Multi-Source Employee Enrichment* actions. This guide uses HTTP API instead, for full control over the endpoint, response fields, and headers.
{% endhint %}
{% endstep %}

{% step %}

### Configure the request

Open the **Configure** tab and set up the call to Coresignal's company enrichment endpoint.

{% code title="Endpoint" overflow="wrap" %}

```
https://api.coresignal.com/cdapi/v2/company_multi_source/enrich?website={{Domains}}
```

{% endcode %}

Insert the domain column by typing `/` in the field and selecting **Domains**.

**Headers**

| Key      | Value                   |
| -------- | ----------------------- |
| `apikey` | Your Coresignal API key |

Leave **Method** as `GET` (the default for this endpoint).

<img src="/files/yPx5oZoUC2JHiM07WAut" alt="" width="382">
{% endstep %}

{% step %}

### Choose which fields to return

Under **Response values to return**, select the fields to write back as columns.

**Returned by default:** `id`, `source_id`, `company_name`, `created_at`, and the firmographic fields shown later in the cell details.

**Excluded by default:** To keep cells within Clay's size limits, the following heavier fields are omitted from the default response. They are listed below in groups. You can add any of these fields to the response if needed.

{% hint style="warning" %}

#### **Cell size limit: 200 KB**

If a returned cell exceeds this limit, the enrichment will not run for that row. The `*_by_month` time-series fields are the most likely to push a cell over the limit – especially combined with compensation, executive, or job posting fields. Add only what you need, and test on a few rows first.
{% endhint %}

<table><thead><tr><th width="199.91796875">Group</th><th>Fields</th></tr></thead><tbody><tr><td>Compensation</td><td><code>base_salary</code>, <code>additional_pay</code>, <code>total_salary</code></td></tr><tr><td>Executives &#x26; updates</td><td><code>key_executives</code>, <code>company_updates</code></td></tr><tr><td>Job postings</td><td><code>active_job_postings</code></td></tr><tr><td>Monthly time-series</td><td><code>active_job_postings_count_by_month</code>, <code>employees_count_by_month</code>, <code>employees_count_by_country_by_month</code>, <code>employees_count_breakdown_by_seniority_by_month</code>, <code>employees_count_breakdown_by_department_by_month</code>, <code>employees_count_breakdown_by_region_by_month</code>, <code>product_reviews_score_by_month</code>, <code>total_website_visits_by_month</code>, <code>employee_reviews_score_aggregated_by_month</code>, <code>employee_reviews_score_business_outlook_by_month</code>, <code>employee_reviews_score_career_opportunities_by_month</code>, <code>employee_reviews_score_ceo_approval_by_month</code>, <code>employee_reviews_score_compensation_benefits_by_month</code>, <code>employee_reviews_score_culture_values_by_month</code>, <code>employee_reviews_score_diversity_inclusion_by_month</code>, <code>employee_reviews_score_recommend_by_month</code>, <code>employee_reviews_score_senior_management_by_month</code>, <code>employee_reviews_score_work_life_balance_by_month</code></td></tr></tbody></table>
{% endstep %}

{% step %}

### Test, then run

1. Click **Try on 5 rows** to validate the call before running the full table.
2. Once the preview looks right, click **Save**, and choose:
   * **Save and run a batch**
   * Run everything in the current view
   * **Save and don't run** (to run manually later)

![](/files/eISNrKBvt43s4VjpwDB6)

While it runs, Clay shows progress in the column header.

| Status code   | Description                          |
| ------------- | ------------------------------------ |
| `200`         | The row enriched successfully        |
| `400`         | Bad request                          |
| `404`         | No matching company for that domain) |
| {% endstep %} |                                      |

{% step %}

### Review the enriched data

Click any enriched cell to open **Cell details** and inspect the full profile. Any of the fields can be mapped into downstream columns, exports, or your CRM.
{% endstep %}
{% endstepper %}

## Resources

<table data-view="cards"><thead><tr><th></th><th></th></tr></thead><tbody><tr><td><a href="https://www.clay.com/integrations/data-provider/coresignal"><strong>Coresignal integrations</strong></a></td><td>Find information about Coresignal integration in Clay</td></tr><tr><td><a href="https://university.clay.com/"><strong>Clay knowledge base</strong></a></td><td>Clay's documentation, courses and more</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/clay.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.