Outcome. The operations channel gets a Slack message the moment a connected integration fails to sync a company record, so a broken connection gets noticed the same day instead of at the next data audit.
flowchart TD
A[integration_sync_status changes to Failed] --> B[Send Slack message to #integration-health]
B --> C[Set last_sync_failure_at = now]
C --> D[Optional: create investigation task]

When to use it, when not to
- UseUse it on a portal with a business-critical native integration (ERP, billing, a marketing automation bridge) syncing company data, where a silent failure has real downstream cost.
- UseUse it to give the admin team a single channel for sync health instead of checking each integration's own settings screen separately.
- SkipDo not use it as a substitute for the integration's own error log. This alert tells you THAT a sync failed, not the full technical detail of why.
- SkipDo not build this if the integration in question has no way to write a failure signal into HubSpot. See Known pitfalls before committing to this pattern.
or the reporting and alerts pack, 39 EUR
One-time, excl. VAT. 30-day refund, no questions asked. Founding prices until 31 October, then 199 and 59 EUR. Includes every spec added later, up to the full 500, and the one-click installer on the full library. Building on client portals? The agency licence at 449 EUR covers unlimited client portals.





