Post by Ori Shimon

Here's how I used Claude Code to merge two HubSpot workflows into one. We had two workflows doing almost the same thing - one for form submissions, one for LinkedIn Lead Gen ads. Both routed leads, sent Slack alerts, assigned contacts to lists. But they did it differently, and every time we launched a new campaign it was the same headache: "Which workflow do I update? Both? Just one? Will they conflict?" I wanted to simplify this. So I pointed Claude Code at our HubSpot instance and asked it to pull both workflows through the API and compare them side by side. Within minutes it mapped out every branch, every condition, every action and generated an interactive visual showing exactly where the two overlapped and where they contradicted each other. Differences were everywhere - test email filtering, task creation for sales requests, wait steps before routing, Slack notification formats. Same goal, different behavior. Well, what can you expect from a human who built them months apart? That's how things break quietly, and with two separate workflows doing similar things you get double the maintenance and double the risk of something slipping through. For the entire research phase I used a dedicated read-only skill I built specifically for this kind of work. It connects to HubSpot through the API but can only read - never write, never update, never delete. Even though the API key has full permissions, the skill enforces read-only at the instruction level. That means I can point it at our entire instance and let it research freely. The safety isn't in my discipline, It's in the design. Once I had the full picture, Claude Code created a consolidation proposal - one unified workflow that handles both sources, eliminates the inconsistencies, and scales to new campaigns without needing a code change for each one. Keep in mind these weren't simple workflows - each had dozens of branches, conditions, and actions. Rebuilding something like that manually from scratch would take hours and almost guarantee mistakes along the way. I asked it to build the new workflow in draft mode so I could go in, review every branch, verify every condition, and turn it on only when I was confident it was right. Read-only for research. Draft mode for building. Human review before anything goes live. If you're running GTM ops with more than a handful of workflows, there's a good chance some of them are quietly contradicting each other. You just can't see it yet. #GTMOps #RevOps #HubSpot #ClaudeCode #AIOperations

Video Content