Enrichment is only useful if the row becomes a lead. Compare the manual path with Clay connected to SendCopy.
CSV Export: Clay finishes enriching, someone exports the table to CSV.
Manual Upload: The CSV gets uploaded into SendCopy by hand, one list at a time.
Stale List: The list is already stale the moment Clay finds new rows after that.
Idle Pipeline: Most GTM teams stop here. The list sits in Clay until someone remembers to move it.
Auto Post: A row finishes enriching and posts to SendCopy on its own.
Auto Route: It lands in the right list automatically, people or company, no upload step.
Live Sync: The list keeps filling with Clay's auto-update running in the background.
Never Stops: It's a lead in SendCopy before the enrichment column finishes rendering.
A row becomes a lead the second it's sent. Nobody's dragging a CSV into another tab.
Headline, location, company, whatever Clay found stays attached to the lead in SendCopy.
People and companies get their own endpoints, so a target account list never gets diluted by contacts.
Turn on Clay's auto-update and the list keeps filling in the background, no return visit required.
After that, adding leads is just running the Clay table. No return trip to SendCopy required.
Open API Integration in SendCopy and copy your key. Clay sends this on every request, it's how we know the row is yours.
Each endpoint locks to one list and one type, people or company. Keep a separate endpoint for every list you want to build.
Add an HTTP API action in Clay, paste the endpoint, set the method to POST, and point profileUrl and the rest at columns you already have.
Three fields are required no matter what you're sending. Everything past that is optional, and the more of it you map, the more a lead looks like a person instead of a LinkedIn URL.
JSON
{ "type": "people", "listName": "Clay People - Outbound", "name": "/Full Name", "profileUrl": "/LinkedIn URL", "publicIdentifier": "/Slug", "headline": "/Headline", "about": "/Summary", "location": "/Location", "emailAddress": "/Work Email", "phoneNumber": "/phone number"}JSON
{ "type": "company", "listName": "Clay Companies - Target accounts", "name": "/Company Name", "profileUrl": "/LinkedIn URL", "publicIdentifier": "/Slug", "about": "/Description", "location": "/Location", "emailAddress": "/Work Email", "phoneNumber": "/phone number"}Clay endpoint
Locked type
People
The first row that succeeds on an endpoint decides what that list holds. Send the other type to that same endpoint and you'll get a 409, not a mixed list. Generate a second endpoint instead.
Auto-update
ACTIVE142
Leads synced
Latest rows
Turn on Clay's auto-update and every new row that matches your filter gets added the moment it appears. Nobody has to remember to re-run the table or re-export anything.
Separate endpoints
SDR List
People
webhook_sdr_people
Target Accounts
Companies
webhook_target_cos
Point each at its own endpoint and your SDR prospecting list and your target account list never collide, even if they're built from the same source data in Clay.
Connect it to SendCopy and the leads you've enriched start turning into conversations, not another spreadsheet waiting to be uploaded.