Clay is good at finding companies and enriching rows. Aptiro is good at deciding which accounts are ready to buy, scoring them against your ideal customer, writing a brief, and tracking who on your team reached them. Many teams keep Clay for enrichment and add Aptiro as the CRM that acts on the result.
There is no separate Clay connector. You connect Clay the same way you connect any other system that can answer Aptiro during a scan: as a webhook trigger source. Aptiro asks your endpoint about an account it already has; your Clay-backed endpoint looks that company up in a Clay table and returns signal documents. Aptiro then scores, briefs and tracks as usual.
Webhook sources are a Scale-plan feature. An owner or admin with permission to manage signal sources sets them up in Settings > Signals > Sources.
What each tool does
| Clay | Aptiro | |
|---|---|---|
| Find and enrich companies | Yes | Also finds accounts, and scores them against your ICP |
| Hold buying signals you already gathered | In a table or workbook | Attached to the account, graded strong / medium / weak |
| Decide who is ready to buy | You decide in Clay | Fit, readiness and opportunity scores, plus a brief |
| Track outreach and ownership | Outside Clay | Who owns the account, activities, sequences and Today |
Clay does not replace Aptiro's CRM, and Aptiro does not replace Clay's enrichment grid. The webhook is the hand-off from Clay's rows into Aptiro's scan.
What has to be true first
- The company already exists as an account in Aptiro (imported, found, or created by hand). A scan runs on Aptiro accounts; the webhook does not create accounts from Clay rows.
- An admin has added a webhook source in Settings > Signals > Sources,
pointed at an
httpsendpoint your side controls, and accepted the data terms. The signing secret is shown once. - That endpoint can look a company up in Clay (by domain or company name) and return documents in the shape below.
To confirm on your Clay plan: which Clay HTTP API, webhook or agent can host
that endpoint for you. Aptiro only requires a public https URL that answers
the contract in
add a webhook trigger source.
How a scan reaches Clay
On each scan of an account, Aptiro sends a signed POST to your endpoint
with the account's id, name, website and any custom fields you chose to
share. Your endpoint:
- Finds the matching row in the Clay table (usually by domain or company name).
- Builds one document per signal or enrichment you want Aptiro to read.
- Responds
200with adocumentsarray.
Aptiro reads those documents alongside its other sources, extracts buying
signals, scores the account, and updates the brief. Credits for the webhook
source are charged like any other source; a failed call is refunded and the
rest of the scan still runs. Full request and response shapes live with the
code at docs/trigger-sources/WEBHOOKS.md in the product repository.
Copyable response mapped from typical Clay columns
Map Clay columns into each document like this:
| Clay column (typical) | Document field | Notes |
|---|---|---|
| Company / Account name | (used to match the request, not returned) | Match on Aptiro's account.name or account.website |
| Domain / Website | (used to match) | Prefer domain match when both exist |
| Signal / Note / Insight | text and usually title |
text is what the AI reads; keep it factual |
| Source URL / Evidence link | url |
Must be http or https; shown as the evidence link |
| Date / Signal date | publishedDate |
ISO date or datetime; omit if unknown |
Example response your endpoint can return when Aptiro asks about Acme:
{
"documents": [
{
"title": "Series B announced",
"url": "https://news.example.com/acme-series-b",
"publishedDate": "2026-10-12",
"text": "Acme Ltd raised a Series B. Clay row signal: \"Series B announced\" for domain acme.com."
},
{
"title": "Hiring surge in sales",
"url": "https://www.linkedin.com/company/acme/jobs",
"publishedDate": "2026-10-20",
"text": "Clay enrichment notes a jump in open sales roles at Acme over the last 30 days."
}
]
}
Up to 20 documents are read per response. An empty documents array means
nothing new for that account, which is normal. A document that does not fit
the shape is skipped; the rest still count.
What Aptiro does with the result
After the webhook (and any other sources) return:
- Fit and readiness. The account is scored against your ideal customer profile and how ready it looks to buy. See understanding ICP fit and readiness scores.
- The brief. Signals from Clay appear on the account with their evidence link, alongside signals from news and other sources you have switched on.
- Tracking who reached the account. Ownership, activities, sequences and the Today list stay in Aptiro, so the team that acts on a Clay-sourced signal is the same team that owns the CRM record.
Limits worth knowing
- Aptiro calls your endpoint; Clay does not push rows into Aptiro through this path. To bring Clay-found companies in as accounts, import them (for example with import contacts from a CSV once you have people, or create the accounts first) and then scan.
- The endpoint must be public
https. Private addresses are refused. - Signing, timeouts and size limits are the same as any webhook source; see add a webhook trigger source.