> 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/find-your-clay-records.md).
# Find your Clay records in Kernel
Find Clay-sourced records in Kernel, compare their identifiers and review the available company data.
Use Kernel to find and review the company records associated with your connected Clay workspace.
This guide is for customers who use both **Kernel and Clay**. You need access to your team's Kernel workspace. **Salesforce is not required.** If you have not connected your workspace yet, start with [Use a Kernel key](/integrations/clay/connect-your-kernel-account.md).
## 1. Open your accounts
1. Sign in to the Kernel workspace connected to Clay.
2. Select **Production**.
3. Open [**Accounts**](https://app.kernel.ai/accounts).
Keep one completed **Resolve company entity** result open in Clay, with its KERN ID and source record ID if supplied. You will use it to compare the record across both products.
## 2. Find your Clay records
Use the Clay channel filter where it is available:
1. Open **Filter → Rules → Filter by fields**.
2. Add a rule: **Channel → Equals → Clay**.
3. Select **Apply filters**.
Filter accounts by Channel → Equals → Clay.
Check any other active filters, since they may narrow the results further. The Clay channel mark appears beside **Account ID**.
If **Filter by fields** is not shown, use the name or URL search below and check the account's channel mark. Contact your Kernel team for help with the filtering controls available in your workspace.
## 3. Find a particular company
Use **Search accounts by name or URL**. Start with the company name or website returned by Kernel in Clay.
The resolved name may differ from the name you originally entered. If several companies have similar names, compare their websites and countries, then check the KERN ID.
Use the page controls to browse more results, or change **Rows per page**.
## 4. Match it to the right Clay row
Keep these identifiers separate:
| Identifier | What it identifies | Where to compare it |
| ---------------------------- | ------------------------------------- | ---------------------------------------------------------------------- |
| **Your record ID** | Your original source record | The value supplied to the action in Clay |
| **Account ID / External ID** | The source record stored in Kernel | **Account ID** in the table; **External ID** in the account's Overview |
| **KERN ID** | The company entity resolved by Kernel | The result in Clay and the account in Kernel |
If you supplied **Your record ID** to **Resolve company entity**, compare it with **Account ID / External ID** in Kernel. If you left it empty, Kernel assigns a generated identifier.
Next, compare the **KERN ID** in both products. You can copy it from the account's **Overview** panel.
The Overview shows KERN ID and External ID separately. KERN ID identifies the company; External ID identifies the source record.
Two source records can share a KERN ID when they refer to the same company. A parent and its subsidiary can have different KERN IDs because they are separate entities.
**For future runs:** map a stable source identifier into **Your record ID** and keep it in your Clay table alongside the returned KERN ID.
## 5. Review the account
Click the account row to open its details.
| Tab | What to check |
| ---------------------- | -------------------------------------------------------------------------- |
| **Overview** | KERN ID, External ID, identity confidence and available parent information |
| **Recommended action** | The suggested data action and the reasoning behind it |
| **Change management** | Available CRM changes and their history |
Check that the name, website and country describe the company you intended to process. Keep the company's own KERN ID separate from its parent IDs.
For headcount and revenue, distinguish values for the entity itself from consolidated values that include its subsidiaries. See the [data dictionary](/data/data-dictionary.md) for field definitions.
If a field is empty, check whether the relevant action in Clay completed and returned that field. An unknown value is different from zero or false. Use the result in Clay to check the status of a particular action run.
## If a record is missing
Check these in order:
1. **Workspace:** are you in the Kernel workspace connected to Clay, with Production selected?
2. **Connection:** did the action in Clay use the intended Kernel connection?
3. **Earlier records:** open the Clay connection and check [Import accounts from earlier runs](/integrations/clay/connect-your-kernel-account.md#import-accounts-from-earlier-runs).
4. **Filters:** clear the search and check for other rules that might exclude the record. Search again using the resolved name or website.
5. **Action status:** check the result in Clay. Allow a processing action to finish, or review its error before rerunning it.
If you still need help, contact Kernel with the Clay workspace and table, action name, approximate run time, source record ID and returned KERN ID where available. Keep your API key out of the message.
## Continue your workflow
Continue your enrichment workflow in Clay and use Kernel to review the associated accounts. Check the selected Kernel connection when adding another action or table.
