The Workflow Library

Library / Reporting and alerts / reporting-alerts-032

Slack alert: integration sync failure notification (native app connection health)

Reporting and alertsCompanyData Hub ProfessionalIntermediate~25 min to buildFull spec

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.

Workflow map Enrollment, branches and actions at a glance reporting-alerts-032
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]
action or delay branch public on every spec, paid or not

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.
The preview ends here. Six sections are in the library. counted, not blurred
PrerequisitesEvery property with its label, internal name, type and options, plus the assets the workflow needs before you start.4 items
EnrollmentThe trigger, the criteria exactly as they are ticked in the UI, the re-enrollment rule and the suppression list.4 parts
StepsEach action in order with its parameters, its branches and its delays, written as you tick them.4 numbered actions
Known pitfallsTraps seen in production, each with what breaks and what to do instead.5 pitfalls
Test plan, variants and build specHow to prove it works in a test portal, where to look when it does not, the variants for other objects or tiers, and the YAML build spec.3 variants, 3 sections
FilesThe properties JSON creates the fields in one API call, the workflow JSON documents the build.PDF, Markdown, JSON
Install1 click. The installer creates the properties this spec declares and the workflow itself, switched off, then opens a task for the prerequisites that are assets rather than properties, such as a team, a static list or a marketing email. What it created is listed on the install page.1 click, switched off
Unlock the full library, 149 EUR

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.