When Four Tools Are Supposed to Work Together but Don't
Our customer support process looked fine on paper. We had Zendesk handling tickets, HubSpot managing contact and deal data, Notion storing internal documentation, and Make sitting in the middle as our automation layer. On top of that, we had Excel-based reports that the ops team relied on every week.
The problem was that none of these tools were actually talking to each other. A support ticket would come into Zendesk, but the agent had no visibility into what stage that customer was at in HubSpot. Notion SOPs were being updated manually. Make automations were half-built and breaking intermittently. And the Excel reports? Completely disconnected from any live data.
I decided to take this on myself.
Where the DIY Approach Hit Its Limits
I started by mapping out the data flow I wanted. Zendesk tickets should sync relevant fields to HubSpot contact records. HubSpot deal stage updates should trigger workflow changes in Make. Notion should reflect real-time status updates from both platforms. And the Excel reports should pull structured data without someone copying and pasting it every Friday.
The concept was clear. The execution was not.
Make's scenario logic became deeply nested once I tried to handle conditional paths — what happens if a ticket is marked urgent vs. standard, what happens if a HubSpot contact doesn't exist yet, how to avoid duplicate records. I got parts of it working, but the edge cases kept piling up. The Notion database schema needed to be restructured to accommodate incoming data properly, and the field mapping between Zendesk and HubSpot alone took me two full days and still wasn't reliable.
I was spending time on this that I didn't have, and the integration was becoming more fragile with every patch I added.
Bringing in a Team That Knew the Stack
After a couple of weeks of diminishing returns, I reached out to Helion360. I explained the full picture — the tools involved, the workflow I was trying to build, the parts that were partially working, and the outcomes I needed. They asked the right questions upfront: data volume, ticket priority logic, how HubSpot properties were currently structured, and what the Notion workspace was being used for beyond this integration.
That conversation alone told me they'd done this kind of work before.
They took over from where I had left off. Rather than rebuilding everything from scratch, they audited what I'd already built in Make, identified the logic gaps, and restructured the scenario architecture properly. The Zendesk-to-HubSpot sync was cleaned up with proper field mapping and deduplication logic. The Notion database was redesigned with properties that could receive automated updates cleanly. The Excel reporting piece was handled by connecting Make to a structured data output that could feed a live-updating sheet.
What the Finished Workflow Actually Looked Like
Once the integration was live, the difference was immediate. Support agents could see a customer's HubSpot deal stage directly within the Zendesk ticket view. When a ticket was resolved, Make automatically updated the corresponding HubSpot contact record with a timestamped note. Notion reflected current ticket status for internal teams without anyone manually updating it. The weekly Excel report was no longer a manual exercise — it pulled from a structured data source and formatted itself.
The workflow didn't just connect the tools. It removed the human error that had been built into every step of the process.
What This Project Taught Me About Integration Work
Building multi-platform integrations isn't just about knowing the individual tools. It's about understanding how data flows between them, where transformations need to happen, and how to design for failure states — what the system does when something doesn't go as expected. I knew enough to start the project but not enough to finish it cleanly.
The Zendesk, HubSpot, Make, and Notion stack is genuinely powerful when it's wired correctly. But wiring it correctly takes more than reading documentation.
If you're working on a similar integration and finding that the pieces aren't coming together the way they should, Helion360 is worth a conversation — they took a partially-built, problematic workflow and turned it into something that actually runs.