Integrations
Richie Reach and Clay
By Sayudh Mukherjee
Richie Reach delivers signal records directly into Clay tables.
Every record that passes the ICP gate and enrichment waterfall arrives in Clay with the full signal metadata attached: engagement type, keyword theme, engagement recency, behavioral intent class, and composite score.
What arrives in Clay
| Field | What it contains |
|---|---|
| person_name | Full name |
| linkedin_url | LinkedIn profile URL |
| title | Job title |
| company_name | Company name |
| company_size_range | Employee count range |
| industry | Industry category |
| location | Country or region |
| signal_type | Comment, reaction, or share |
| signal_theme | The keyword theme that triggered capture |
| signal_recency | Days since engagement |
| engagement_class | evaluating, active_buyer, category_engaged, surface_engagement |
| composite_score | 0.00 to 1.00 |
| Verified email or null if not found | |
| enrichment_source | Which waterfall tier found the email |
How teams use it in Clay
Most teams route from the Richie Reach table into their own Clay waterfall. Common patterns:
- Route by score threshold: HIGH records (0.74 and above) to one sequence, MED records (0.52 to 0.73) to another
- Additional enrichment: Clearbit, Clay's built-in enricher, tech stack lookups
- CRM push to HubSpot or Salesforce with signal fields mapped to custom properties
- Copy generation using the signal_theme and engagement_class fields as inputs
The signal fields give Clay enough context to write personalized openers without a separate enrichment step for intent data.
What we set up
We provision the Clay table, set the webhook endpoint, and confirm field mapping before the first delivery. Ongoing delivery is automated. You access the table as a standard Clay data source.
Talk to the founder
20-minute call to walk through how the Clay table fits your existing workflow.