Clay logo, go to homepage

Search Marketplace

Browse all Skills
Build listsSkill

Tam Audience Loader

Loads a spreadsheet of companies and contacts into Clay Audiences, linking every contact to its company and turning your columns into real, filterable fields.

Shy Rahnama
Shy Rahnama

Scale-Up Growth Operator at Redline Growth

About this Skill

When to use it

Use this Skill when you need to load a spreadsheet of companies and contacts, a TAM list, or a CRM export into Clay Audiences with contacts properly linked to their companies. It turns raw rows into real, filterable fields and leaves you with a loader you can rerun next quarter. Avoid using it for sourcing new companies or people, enriching or deduping existing records, building segments over already-loaded data, or pushing records into a CRM, sequencer, or out of Clay.

What it delivers

You get company and contact records loaded into Clay Audiences, plus a coverage report and a field-by-field check comparing what Clay stored against your file. The report lists every unloaded row by reason, so you know exactly what to fix before you run it again.

SKILL.md preview

Sign in to install and view the complete SKILL.md

Illustrative preview. Sign in for the actual file.

How someone would prompt this

load a list of companies and a list of people into Clay

Inputs & outputs

What someone provides before the Skill runs, and the reviewable artifacts it returns.

Inputs

  • 01Source files
    • Provide companies and/or people as CSVs, Excel tabs, or a Google Sheet export
    • one table alone is fine.
  • 02Company-contact linking
    • Confirm which column names a company and which contacts column matches it
    • when missing, the Skill derives a key from the headers or the work email domain.
  • 03Field mapping choices
    • Approve which columns to load and the Clay type for each
    • confirm whether a column reuses an existing field or creates a new one.
  • 04Unmatched records handling
    • Choose whether unlinked contacts load anyway or get held back
    • decide whether to create bare company records for companies found only through contacts.
  • 05Run settings
    • Set the order Clay tries match keys, such as domain, LinkedIn, email, or phone
    • set shard count and pace for the load.

Outputs

  • 01Pre-load coverage reportShows counts of rows that can and cannot load, before the Skill writes anything, so you can fix issues first.
  • 02Unmatched company resolutionLists contacts whose company wasn't in your companies file and shows whether it matched an existing company, got created, or stayed unlinked.
  • 03Post-load verificationCompares what Clay stored for each field against what your file carried, and flags values that saved successfully but that no filter can match.
  • 04Refused records, by reasonLists every row that didn't load, grouped by the specific reason, so you know exactly what to fix.
  • 05Load ledgerRecords, row by row, what the Skill wrote and the Clay record id it received, so you can resume a load that stopped partway.

Representative output

Pre-load coverage report

CompaniesContacts
Rows in file4,18026,402
Loadable4,06124,918
No Clay match key1191,484
Duplicate row key012
Sharing a match key with another row46 rows -> 21 records8 rows -> 4 records
Values Clay will not accept as that keylinkedin_url 7email 31
Company link—ok — 24,306 of 24,918 resolve via company_id
Company reference not in the companies file—612, of which 588 carry a domain to go on
Values their field's type will not parseemployee_count 338 of 4,180 (1,001-5,000, ~250)tenure_years 0

The company-link row is the one to read twice. NOT CONFIGURED, COLUMN NOT IN FILE or NOTHING RESOLVES there means every contact would load with no company attached while every row reported success, and the load refuses to start.

How the Skill runs

Follow the steps in order. Each row includes the full instruction.

01
Explain the plan and get files

Explains in plain language what will happen, asks for the companies and/or people files, and does not gate on this step.

Step
02
Read files and show column mapping

Reads every column, infers its type, shows sample values, and asks for one confirmation covering which columns to load, the row key, and the company link column.

Step
03
State the keys being used

Reports which columns serve as the company key and the contact-to-company reference, and says plainly if the Skill had to create a key.

Step
04
Count what will fail to load

Checks every row against Clay's rules before writing anything, reporting rows with no match key, duplicate keys, unmatched company references, and values a field type would reject.

Step
05
Get approval before writing

Stops and waits for one approval covering the exact counts to load, the new fields to create, and whether to create bare company records for companies found only through contacts.

Step
06
Build the fields and workflows

Creates the confirmed fields and builds two Clay workflows, one for companies and one for contacts, that act as the reusable loader.

Step
07
Resolve contacts' missing companies

For contacts whose company isn't in the companies file, matches them to an existing company, creates one if approved, or reports them as unlinked.

Step
08
Resolve contacts' missing companies

For contacts whose company isn't in the companies file, matches them to an existing company, creates one if approved, or reports them as unlinked.

Step
09
Load contacts and link them

Loads each contact using the company's Clay record id so it is genuinely linked, rather than just sharing a similar value like a domain.

Step
10
Verify against Clay's live data

Asks Clay what each field actually holds for this load's own records and reports any field where the stored count differs from what was sent.

Step
11
Deliver results and workflow choice

Hands over the coverage report, verification table, and ledger files, then lets you choose to keep, publish, or delete the two workflows built for this load.

Step

Connections required

CSV or Google SheetsRequired connection

Install Clay and run it

Sign in once, install the Skill, then run the prompt.

  1. 1Install ClayUse the connector or official plugin in your coding-agent environment.
  2. 2Sign up or log inAuthorize Clay access and return when the connection is ready.
  3. 3Install the SkillRun the one-line install command from the Add this Skill card.
  4. 4Run the SkillPaste the example prompt and review the result.

Version history

Version 2From submitted SKILL.mdCurrent

Related Skills

Icp Outbound CampaignTurns your ideal customer profile into a verified lead list saved in Clay Audiences and a drafted outbound email sequence, without sending or launching anything.View Skill →Clean Company Names For CopyCleans raw company-name strings into short, natural versions for outreach copy, running a free normalizer first and escalating to AI only when a 20-row review shows the normalizer falls short.View Skill →Clean First Names For GreetingsCleans the raw first_name_raw field into a proper greeting name in a new first_name_clean column, withholding rows that fail six guard checks instead of guessing.View Skill →

Related searches

Build lists skillsCSV or Google Sheets skills