Signals in.
Clay tables full.
Send any selection of accounts or people from Hunch straight into a Clay table - one JSON row per record through Clay's webhook source. No CSV exports, no size limits, no copy-paste.
How it works
Rows appear in Clay as they arrive.
Clay tables can ingest data from a webhook source - a unique URL that turns every incoming POST into a table row. Hunch sends exactly that: flat JSON where every key maps to a Clay column, one POST per record.
Add your Clay webhook URL once as a named destination, then send from the Accounts or People tables: the current selection, or everything matching a filter. Signal-qualified companies land in Clay with their why-now brief attached, ready for your enrichment and scoring columns to take over.
Create a Clay webhook table
In Clay: new table → import data → Monitor Webhook. Clay gives you a unique URL.
Add it as a destination in Hunch
Settings → Webhook destinations → paste the Clay URL and name it after the table.
Send, and watch rows land
Select accounts or people → Send → your Clay destination. Rows stream into the table as they deliver.
Built for volume
Ten rows or ten thousand.
Small selections deliver instantly. Large ones run as a background push that checkpoints its progress and keeps going until every row has landed - you can close the tab.
Send all matching
Push an entire filtered view - every account in a segment, every person with a verified email - in one action.
Rate-limit aware
If Clay throttles, Hunch paces itself down and retries with backoff. Every row gets delivered, none get dropped.
Signed rows
Every POST carries an HMAC-SHA256 signature, so you can verify rows came from Hunch if you route them beyond Clay.
Row shape
Flat JSON. Every key becomes a column.
No nested objects to unpack: each record arrives as a single flat JSON object, which Clay maps 1:1 onto table columns. Accounts carry the full firmographic picture plus the signal context; people rows add title, seniority, verified email, and LinkedIn URL.
The why_now field is the same AI-written brief your reps see in Hunch - which means your Clay table starts with the reason to reach out already written, not just a company name to enrich.
From there it's standard Clay: waterfall enrichments, scoring columns, AI prompts against the brief, and a push to wherever your sequences live.
{
"record_type": "account",
"name": "Talkdesk, Inc.",
"domain": "talkdesk.com",
"industry": "Software Development",
"employees": 1800,
"location": "San Francisco, CA",
"score": 91,
"is_hot": true,
"tags": "Enterprise",
"linkedin_url": "https://linkedin.com/company/talkdesk",
"short_description": "AI-powered contact center platform.",
"why_now": "VP of Sales promoted to CRO. 14 AE roles opened in 3 weeks...",
"latest_signal": "Sales Hiring Surge",
"latest_signal_at": "2026-07-07T09:01:43.217Z",
"pushed_at": "2026-07-07T09:14:02.005Z"
}Setup
Connected in two minutes.
If you can copy a URL, you can wire Hunch to Clay. The full walkthrough lives in the webhook docs.
01
Get the Clay URL
In Clay, create a table with a Monitor Webhook source and copy the unique URL it generates.
02
Add the destination
In Hunch: Settings → Webhook destinations → paste the URL and give it the table's name.
03
Send from anywhere
Accounts table, People table, the API, or MCP - pick records and choose your Clay destination from the Send menu.
Feed Clay with signals.
Start your Clay tables from companies that are actually in market, with the why-now already written.
See your signals