The Clay integration allows you to send leads from a Clay table directly to SendCopy.
Instead of exporting your Clay table as a CSV and manually uploading it to SendCopy, you can configure a Clay HTTP API action to send each row to a SendCopy lead list.
When a row is successfully sent, SendCopy adds it to the corresponding lead list. This allows you to use your enriched Clay data directly in SendCopy for outreach campaigns.
The integration supports both:
People lists — individual LinkedIn profiles
Company lists — LinkedIn company profiles
Each list type uses its own webhook endpoint.
With the integration, you can:
Send enriched leads from Clay to SendCopy
Create new SendCopy lead lists from Clay
Add new rows to an existing SendCopy list
Import people or company records
Map information such as name, LinkedIn URL, headline, location, and email
Keep your SendCopy lead lists updated as new Clay rows become available
Clay's enrichment data can remain attached to the lead when it is sent to SendCopy, making the imported records more useful for your outreach workflow.
Make sure you have:
An active SendCopy account
Access to SendCopy lead lists
A SendCopy API key
A Clay table containing the leads you want to send
LinkedIn profile or company URLs in your Clay table
Access to Clay's HTTP API action
The integration uses your SendCopy API key to authenticate requests from Clay. Your API key is sent with each request through the X-API-Key header.
First, get your API key from SendCopy.
Open your SendCopy account.
Go to the API Integration section.
Copy your SendCopy API key.
Keep the key secure.
You will add this key to Clay when configuring the HTTP API action.
Clay uses the API key to authenticate each request sent to SendCopy.
Important: Your API key is not your SendCopy password. Do not share it publicly.
Next, generate a Clay webhook endpoint in SendCopy.
Open the Clay integration settings in SendCopy.
Generate a new webhook URL.
Copy the complete URL.
Keep it available for the Clay setup.
The generated URL contains a unique ingestion token that SendCopy uses to identify where the incoming leads should be added.
Generating the webhook URL does not immediately create a lead list.
The list is created when the first valid row is successfully sent through that endpoint.
Open the Clay table containing the leads you want to send to SendCopy.
Your table should contain at least a LinkedIn URL for each record.
For example:
Full Name
LinkedIn URL
Headline
Location
Company
Other enriched information
You can send additional supported fields along with the LinkedIn URL.
In your Clay table:
Click Add column.
Select Add enrichment.
Search for HTTP API.
Select the HTTP API action.
Click Configure.
This action will send each Clay row to SendCopy.
When configuring the HTTP API action:
Click Add account.
Add the following header:
Key: X-API-Key
Paste your SendCopy API key as the value.
Save the configuration.
The API key must be included in the request, so SendCopy can authenticate the incoming data.
In the HTTP API configuration:
Find the Method field.
Select POST.
Paste the webhook URL you generated in SendCopy into the endpoint/URL field.
Your setup should now contain:
Method: POST
URL: Your SendCopy Clay webhook URL
Header: X-API-Key → Your SendCopy API key
The request body tells SendCopy what type of lead you are sending and which data should be added to the lead list.
There are two supported types:
people
company
The type value must be written in lowercase.
For a people list, the minimum request body is:
{
"type": "people",
"listName": "Clay People - Outbound",
"profileUrl": "/LinkedIn URL"
}The required fields are:
type
listName
profileUrl
For a company list, use:
{
"type": "company",
"listName": "Clay Companies - Target accounts",
"profileUrl": "/LinkedIn URL"
}The same three fields are required, but the type must be company.
You can send additional information from your Clay table to SendCopy.
Supported people fields include:
name
profileUrl
publicIdentifier
headline
about
location
emailAddress
phoneNumber
Supported company fields include:
name
profileUrl
publicIdentifier
about
location
emailAddress
phoneNumber
For example, a people request with additional information can look like:
{
"type": "people",
"listName": "Clay People - Outbound",
"name": "/Full Name",
"profileUrl": "/LinkedIn URL",
"publicIdentifier": "/Slug",
"headline": "/Headline",
"about": "/Summary",
"location": "/Location",
"emailAddress": "/Work Email"
}SendCopy currently supports the fields listed above.
When mapping a Clay column into your JSON body:
Enter the SendCopy field name.
Add a colon.
Add quotation marks.
Inside the quotation marks, enter /.
Select the corresponding Clay column.
For example:
"name": "/Full Name"Clay will then use the value from the Full Name column for the name field.
For enriched fields, you may need to select the value from the Enrichment Column section. For example, if you need the LinkedIn slug, select the relevant value from the Enrich Person data.
Tip
If you cannot find a value under the standard columns, check the Enrichment Column section.
The integration guide recommends using enrichment data where available because it can provide more up-to-date and complete information.
After mapping your fields:
Review the JSON body.
Save the HTTP API action.
Choose Save and don't run if you want to review everything first.
Otherwise, run the action on your selected rows.
You can also run the action directly from the Clay table.
Start with a small number of rows so you can verify that the integration is configured correctly before processing the full table.
If you want to create a completely new lead list, generate a new Clay webhook URL in SendCopy.
Each new webhook endpoint can create its own list when the first row succeeds.
For example:
Clay Table A → Webhook A → People List A
Clay Table B → Webhook B → People List B
This makes it easier to keep different prospecting workflows separated.
If you want to continue adding leads to a list that was already created:
Reuse the same webhook URL.
Use the same type as the first successful row.
Run your Clay table.
New rows will be appended to the existing list.
The listName in later requests does not rename the existing list.
The webhook URL determines the list, so changing listName later does not create a renamed list on that endpoint.
Each webhook endpoint becomes associated with the type of the first successful row.
For example, if the first successful request contains:
"type": "people"that endpoint is locked to a people list.
If you later send:
"type": "company"through the same endpoint, SendCopy returns a 409 Conflict because the lead list type does not match the endpoint.
To create a company list, generate a new webhook URL and use:
"type": "company"This keeps people and company leads separated.
After running your Clay table:
Open Lead Lists in SendCopy.
Find the list created by your Clay webhook.
Open the list.
Confirm that the leads were imported correctly.
Check the lead information and mapped fields.
A successful request returns an HTTP 200 response, which Clay can treat as a successful row.
Possible causes:
API key is missing.
API key is incorrect.
API key has expired.
How to fix it:
Check the X-API-Key header in Clay and make sure the correct SendCopy API key is being used.
The type field must be exactly:
peopleor:
companyUse lowercase letters.
For example, People or PEOPLE will fail validation.
Every request needs a valid profileUrl.
If the LinkedIn URL column is empty for a Clay row, that row cannot be imported successfully.
Check your Clay table and make sure the LinkedIn URL is available before running the action.
This happens when you use an existing webhook URL with a different type than the type used by the first successful row.
Fix: Use the same type as the existing list or generate a new webhook URL for the other type.
Check that you are using the complete webhook URL generated by SendCopy.
The endpoint should follow the expected Clay integration URL structure.
Tips
Start with a small number of Clay rows before running the full table.
Always use a valid LinkedIn URL.
Keep
typehardcoded as eitherpeopleorcompany.Use a separate webhook URL for each new list.
Keep people and company lists on separate endpoints.
Use enriched Clay fields when available.
Give different lists clear names so they are easy to identify in SendCopy.
If you use Clay's auto-update functionality, new rows can continue flowing into SendCopy as they become available. The current Clay integration page describes this workflow as keeping the list updated without requiring repeated manual exports or uploads.