Integrations
Richie Reach and HubSpot
By Sayudh Mukherjee
Every record delivered by Richie Reach can sync to HubSpot with the full signal metadata attached as contact properties.
This means you can trace a closed deal back to the public engagement signal that triggered it: the keyword theme, the engagement class, the composite score at the time of capture.
Signal fields as HubSpot contact properties
| Property | What it maps to |
|---|---|
| signal_theme | The keyword theme that triggered capture |
| engagement_type | Comment, reaction, or share |
| engagement_class | Intent class assigned by AI classification |
| composite_score | Score at time of delivery (0.00 to 1.00) |
| icp_fit_score | ICP gate score at time of filtering |
| enrichment_source | Which waterfall tier found the email |
| signal_capture_date | Timestamp of original engagement capture |
| delivery_date | Timestamp of record delivery to HubSpot |
The attribution loop
When a deal closes, HubSpot can show which signal theme produced the contact, which engagement class it carried, and what the score was. Over time, this lets you adjust which themes to monitor and which score thresholds to prioritize, based on what actually converts in your specific market.
This is the feedback loop that makes the signal feed better over time, not just a reporting layer.
How sync works
We push to HubSpot via Clay webhook or direct API. On the first delivery, we confirm field mapping and custom property setup. Subsequent deliveries are automated.
Existing HubSpot contacts are deduplicated by email to avoid creating duplicate records.
Talk to the founder
20-minute call to walk through the HubSpot sync configuration.