The Problem
A 120-person B2B SaaS company relied on a sprawling Zapier mesh of 47 zaps to move data between HubSpot, Clearbit, Google Sheets, and their internal BI tooling. Zap failures were silent — deals would fall out of pipeline stages with no audit trail. The RevOps team spent 15 hours per week manually reconciling CRM records against spreadsheet exports.
Architecture Decision
Make.com was chosen as the primary orchestration layer for its visual scenario builder, deterministic error routing, and native HubSpot module. Power Automate was introduced for Microsoft-ecosystem integrations (SharePoint contract repositories, Teams alerts). A unified error handler routes failures into a Slack channel with the exact scenario ID, module position, and raw input payload for one-click replay.
Pipeline Design
The core pipeline ingests a HubSpot deal-stage webhook, enriches the associated contact and company records via Clearbit's streaming API, merges the normalized payload into a denormalized BigQuery events table, and fans a filtered subset into Looker Studio for the C-suite dashboard. Every scenario runs under a Make.com operations team with error-handling routes, retryable bundles, and an execution cap to prevent runaway API billing.
Outcome
Zero silent data loss in the 90 days post-migration. RevOps manual reconciliation dropped from 15 hours to 45 minutes per week. The C-suite dashboard now refreshes on a 5-minute cadence instead of a daily CSV upload. The Make.com scenario library is documented in a Notion runbook with replay instructions for every failure mode.