- phaseDiagnostics
- engagementProject
The problem this solves
The sync with your finance system stopped a few weeks ago, and nobody noticed. Two systems write to the same field, so the value depends on which one wrote last, and nobody has opened the Make scenario since the person who built it left.
How I work
I document every connection to HubSpot: marketplace apps, Make scenarios and custom scripts. For each one I record the direction, objects and fields, what triggers it and what happens when something goes wrong. I spend the most time on custom scripts, because that’s where error handling is most often missing.
Then I check whether data lands where everyone assumes it does. I look for fields written by two systems, read the error logs and check whether anyone gets an alert when a connection stops. I also look at HubSpot API limits. You get a map of your connections with a rating for each one, and a plan: what to monitor, what to rebuild and what to turn off.
What you get
- An inventory of connections: marketplace apps, Make and custom code
- A map of the fields that flow between systems
- Fields written by more than one system
- A review of error handling and alerts for each connection
- A plan: what to monitor, what to rebuild, what to turn off

