Clay
Search people and companies in your connected Clay workspace and pull existing Clay tables into Salesfinity. Discovery only — no phones or emails.
What the Clay integration does
Salesfinity's Clay integration runs people and company searches against your own connected Clay workspace and can read tables you have already built in Clay, pulling those rows into a Salesfinity list. It is a discovery integration: it finds and loads records, and it explicitly does not return phone numbers or email addresses through this path. If you have already done the enrichment work inside Clay, the table connector is the fastest way to get that work onto the dialer.
Search your Clay workspace
People search with structured filters — titles, seniorities, locations, and employer
Company search by industry, size, and location
Runs on your team's own Clay API key, so it uses your Clay workspace and your Clay credits
Load an existing Clay table
Pull the rows of a Clay table you have already built and enriched, by table ID
Rows are read page by page and mapped into person records in a Salesfinity list
Uses the same list-loading path as the CRM loaders, so the result behaves like any other Salesfinity contact list
Discovery only — stated plainly
Clay search and table load in Salesfinity return profile records, not contact details
No phone numbers and no email addresses come back through the Clay connector
Contact details are a separate enrichment step in Salesfinity, and that step always requires your explicit approval before credits are spent
Common use cases
Dialing a list you already built in Clay
A growth team spends its time building and enriching tables in Clay, but Clay does not dial. They point Salesfinity at a finished Clay table, the rows load into a Salesfinity contact list, and reps start calling through the parallel dialer. The enrichment work stays where the team already does it.
Running a Clay search without leaving the calling workflow
A rep asks the AI Companion for directors of operations at mid-market logistics companies and names Clay as the provider. The search runs against the team's Clay workspace with structured title, seniority, and location filters, and the results land in a List Builder table next to results from other sources.
Keeping vendor spend in one place
A team that has already standardized on Clay for data does not want a second data contract. Because the Salesfinity connector uses the team's own Clay key, searches draw on the Clay subscription they already pay for rather than adding a separate line item.
How to connect Clay to Salesfinity
In Salesfinity, open Settings → Integrations and find Clay.
Generate an API key in your Clay workspace.
Paste the key into Salesfinity and save it; the key is stored per team.
Use the connection test to confirm the key reaches your Clay workspace.
In the List Builder or the AI Companion, name Clay as the provider for a search, or give a Clay table ID to load an existing table.
Frequently asked questions
Does Salesfinity's Clay integration return phone numbers or email addresses?
No. The Clay connector in Salesfinity is discovery only — it returns profile records with no phone numbers and no email addresses. To get dialable numbers you run Salesfinity's contact enrichment on the list afterwards, which always requires your explicit approval before any credits are spent.
Can I load a Clay table I already built into Salesfinity?
Yes. Salesfinity can read an existing Clay table by its table ID and map the rows into a Salesfinity contact list, which is then dialable in the parallel dialer. This is the most direct path if the enrichment already happened inside Clay.
Whose Clay credits does this use?
Yours. The integration is bring-your-own-key and the key is stored per team, so searches run on your Clay workspace under your own Clay contract.
Does the Clay integration write anything back to Clay?
No. The connector reads from Clay — search results and table rows — and does not write records, call logs, or dispositions back into your Clay workspace.
When would I use Clay instead of Exa or Prospeo?
Use Clay when the data already lives in your Clay workspace, or when your team has standardized on Clay and wants searches to draw on that contract. Use Prospeo when you need enum-exact people filters like seniority and years of experience, and Exa when your criteria are descriptive rather than a fixed filter set.
Need more guidance
on how to integrate ?
Other Integrations
