> For the complete documentation index, see [llms.txt](https://docs.kernel.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kernel.ai/integrations/clay/connect-your-kernel-account.md).

# Use a Kernel key

Connect your Kernel workspace to Clay, verify the connection and check your first record.

Connect your Kernel workspace to Clay, then use that connection in your Kernel actions. You can review the associated company records in the Kernel app.

## Before you start

You need access to both your team's **Kernel workspace** and **Clay workspace**. A Salesforce connection is not required.

The Clay connection uses the **Production** environment.

If you use Clay without being a Kernel customer, [use a Clay key](/integrations/clay/use-a-clay-key.md) and review the results in Clay.

## 1. Create your key in Kernel

1. Sign in to the [Kernel app](https://app.kernel.ai/) and select the workspace you want to connect.
2. Select **Production**.
3. Open [**Connections → Clay**](https://app.kernel.ai/settings/connection/clay).
4. Under **Connect Clay**, enter a **Key name**. The suggested name is **Default Clay key**.
5. Select **Generate API key** and copy the full key while it is displayed.
6. Keep setup open while you add the key to Clay.

<figure><img src="https://1215786129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvRYB7XIKCnmUi9oCEQGV%2Fuploads%2Fgit-blob-d1ca116be61c65c101b39f29a33493abdd3eed62%2Fapp-clay-connection.png?alt=media" alt="Kernel Clay connection setup with the Key name field and Generate API key button."><figcaption><p>Give the key a name your team will recognize.</p></figcaption></figure>

Store the key in your Clay connection. Treat it as a password and keep it out of table columns, prompts and screenshots.

## 2. Add the key in Clay

1. Open [Clay](https://app.clay.com/) → **Connections → Create**.
2. Choose **Kernel** and add a connection.
3. Give it a name your team will recognize and paste the API key. Open the **Save** menu and select **Test account & save**.
4. Select this saved connection in each Kernel action.

<figure><img src="https://1215786129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvRYB7XIKCnmUi9oCEQGV%2Fuploads%2Fgit-blob-aeb99e5994356cb7250053c215cdb1b63ff2de72%2Fadd-kernel-connection.png?alt=media" alt="Clay&#x27;s Add Kernel API Key form with fields for the connection name and API key, a Set as default switch and the Save menu." width="400"><figcaption><p>Add your Kernel key here, then open Save and choose Test account &#x26; save. The API key field is left empty in this screenshot.</p></figcaption></figure>

Check the connection selected for entity resolution, firmographics and hierarchy separately. See [Clay's Connections guide](https://university.clay.com/docs/connections) for connection-management controls.

## 3. Verify the connection

Return to Kernel. The setup status changes from **Waiting to verify your key…** to **Connection verified** when Kernel confirms the connection.

If it is still waiting, check that you copied the complete key and saved it to the intended Clay connection. You can then run one row through **Resolve company entity** using that connection and check again.

## 4. Check your first record

Run one company through your saved connection, then check that the same record appears in Kernel.

1. In Clay, run **Resolve company entity** for one row using your saved Kernel connection.
2. Wait for the action to finish. Open the completed cell, expand **Data → Record** and note the **Kernel Id** value. This is the returned **KERN ID**.
3. In Kernel, open **Accounts** and search for the company's resolved name or website.
4. Open the account and check that its **KERN ID** matches the result in Clay.

<figure><img src="https://1215786129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvRYB7XIKCnmUi9oCEQGV%2Fuploads%2Fgit-blob-7e2b49097055f544f38c26c50b35e5b223c51b14%2Fresolve-company-result.png?alt=media" alt="A completed Clay result with the Kernel Id field visible under Data and Record." width="380"><figcaption><p>Use the Kernel Id value from your completed Clay result when checking the account in Kernel.</p></figcaption></figure>

See [Find your Clay records in Kernel](/integrations/clay/find-your-clay-records.md) for more help with searching, filtering and matching source record IDs.

**Your record ID** is optional. Mapping a stable source identifier makes reconciliation easier. It identifies your source record; KERN ID identifies the resolved company.

## Import accounts from earlier runs

After you connect, **Import Clay accounts** shows how many earlier Kernel records from your Clay workspace can be brought into your Kernel workspace.

1. Review the count and select **Import accounts**.
2. Follow the progress shown on the connection page.
3. Select **View accounts** when the import finishes.

An account is skipped if your Kernel workspace already has an account with the same external ID. If the import stops before finishing, select **Import accounts** again to bring in the remaining records. Accounts already imported stay in your workspace.

Keep source record IDs and KERN IDs in your Clay table so you can compare the imported records with their original results.

When moving from the Clay-managed Kernel account, select your saved Kernel connection in each action and check one new result before running a larger batch.

## Disconnect or change the connection

Choose **Disconnect** on the Clay connection in Kernel. This revokes the API key associated with that connection. Actions in Clay that use the revoked key will fail until you configure a valid connection.

Contact your Kernel team if you need to change which Kernel workspace is associated with the Clay workspace.

## Next: review your accounts

[Find your Clay records in Kernel](/integrations/clay/find-your-clay-records.md) explains how to search, filter, compare IDs and inspect the available account data.