Connection options
- Native auto-sync (Growth plan and up): keeps selected CRM objects and Clay tables in sync, enrich in Clay, results flow back automatically.
- Targeted writes: Clay tables write back to HubSpot through HubSpot integration steps — better when only specific workflows should touch the CRM.
Before the first write
- Create a dedicated integration user or private app token with least-privilege scopes.
- Agree the field map: which HubSpot properties Clay may write, which are read-only, which are rep-owned.
- Define the dedupe key (usually website domain for companies, email for contacts) and use upsert semantics.
- Add provenance fields ("enriched-by", "enriched-at") so CRM data lineage is visible.
Operational safeguards
Pilot on a sandbox or a single pipeline segment. Monitor sync failures (Clay run log + HubSpot integration health). Set expectations: enrichment data ages — schedule refresh passes rather than assuming one-time writes stay current.
Need help applying this?
Describe your project and the ClayForEnterprises team will review it — the resources stay free either way.