Python · Systems audit
HubSpot Runway Auditor
A Python tool that analyzes HubSpot workflows, dependencies, and ownership without changing the CRM.
- Role
- Developer & Systems Analyst
- Organization
- Internal systems work
- Timeline
- Internal audit tooling
- Status
- Completed
Problem
As HubSpot grows, it becomes harder to track overlapping workflows, unclear ownership, and changes that could affect other parts of the system.
Context
- The audit needed to explain configuration to both technical administrators and operational leaders.
- The tool was intentionally read-only so analysis could not alter production configuration.
Requirements
- No write access to HubSpot assets.
- Make the analysis readable without inspecting raw API responses.
- Surface cross-asset dependencies and overlap, not just a flat inventory.
My role
- Build the Python 3.12 exporter and analysis pipeline.
- Organize HubSpot settings into a clear analysis.
- Analyze routing, automation, ownership, lifecycle movement, reporting, and system dependencies.
- Summarize findings for leadership and document assets, dependencies, and overlapping automation.
Process
- 01
Extract
Read configuration and metadata through approved read-only access.
- 02
Normalize
Put different HubSpot settings into a consistent format.
- 03
Trace
Mapped workflows, actions, forms, properties, and dependencies.
- 04
Explain
Packaged findings for both executive review and technical follow-up.
Tools
Challenges
- 01
Showing how nested workflows connect without losing important details.
- 02
Separating genuine overlap from intentional multi-step process design.
- 03
Making risk signals useful without exposing operational details.
Outcome
The analysis brings workflows, forms, fields, and dependencies together so teams can review overlaps and plan changes.