Reading view

Our customer had ~1,000 manually-managed HubSpot lists and no way to track what changed, so we built a Terraform provider

We build HubSpot tools for a living, so when a customer mentioned this recently, it stuck with us more than it maybe should have. They manage HubSpot config constantly (properties, pipelines, list logic) essentially every other day. Nearly 1,000 lists, built up over time, entirely by hand. We asked the obvious question: if something changes and breaks a report, how do you find out what happened? Answer: mostly, they don't. There's no real history below Enterprise tier, and even with it, only a 30-day window.

That's the moment it clicked that CRM config has basically the same failure mode infrastructure had over a decade ago (manual, undocumented, drifting silently), and the fix (declare desired state as code, diff against reality, review before applying) is the exact same fix that worked for infrastructure.

So we built terraform-provider-hubspot: open source, manages the config plane (properties, pipelines, schemas, lists), not actual records. Works with Terraform and OpenTofu.

Genuinely curious: if you manage CRM at scale (HubSpot or otherwise), does this "no real audit trail, drift you only catch by accident" thing sound familiar? What do you currently do about it, if anything?

submitted by /u/Relentlessish
[link] [comments]
  •  
❌