Skip to content
The SpawnExplore tools
Research workflow

Bring account facts into Clay

Use a saved company CSV as a manual Clay import, map the columns, and verify the resulting row before enriching more data.

Saved tool output

Three companies, actual records

Try tool
stripe.com / vercel.com / linear.app3 records
Download JSON
Three captured company lookups
CompanyWhat they doTeam estimateFounded
Stripestripe.comStripe is a financial services platform that enables businesses to accept payments and manage money movement with flexible billing solutions.Team estimate10K-50KFounded2010
Vercelvercel.comVercel is a technology company that provides a platform for frontend developers to build, preview, and ship websites and applications efficiently.Team estimate1K-5KFounded2015
Linearlinear.appLinear is a project management tool that streamlines issues, projects, and roadmaps for modern product development teams.Team estimate251-1KFounded2019

Three separate lookups. Employee ranges are estimates; absent fields remain null.

Download CSV

Map columns

Check row

Manual CSV handoff. No native Clay connector, automatic sync or tested batch enrichment.

01

Start with the saved example

The Stripe example is a dated company snapshot. Download its CSV and open it before importing. It demonstrates the handoff format, not current company verification. Check the domain, column names and employee estimate so you know which values will enter your table.

02

Choose your Clay destination

Clay documents CSV imports into a new or existing table. Select the CSV source, upload the file and choose the destination. Existing-table imports require column mapping. Interface labels can change; the linked Clay documentation is the current reference.

03

Map identity first

Map domain to the company website field and name to the company-name field. Preserve founding year and employee range in separate columns. Keep the estimated range as text; converting it to a single number would introduce a value the source never supplied.

04

Review before enrichment

Check the imported row against the original CSV. A successful import proves that data arrived, not that the data is correct. If Clay offers automatic enrichment for new rows, review that choice and its costs before enabling it.

05

Plan repeated imports

Keep a stable domain identifier and a source date in your own workflow. Decide how to handle duplicates before importing another file. This example does not configure an update key, recurring job or two-way synchronization for you.

06

Measure a useful outcome

Use the imported facts to reduce repeated manual entry or prepare an account question. Record corrections and missing values. Clay credits and The Spawn executions belong to separate cost records; this manual example does not establish a total automated cost per enriched row.

Keep these fields

domain
Stable company identity for mapping
name
Company name from the saved record
founded
Founding year as returned
employees
Estimated range, retained as text
Stripe

Try a saved company row

Captured 14 September 2026. Team size is estimated.

Download CSV

Sources and next steps

Reviewed 2026-09-14