Skip to content
The Workflow Library
Get the full library

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

One of 565 written HubSpot workflow specs, by a collective of independent HubSpot consultants.

Professional

Seat pricing: Professional edition. To build it, a GTM Seat or an Ops Seat (an Ops Seat cannot create marketing emails or sequences). Per-hub plans: Data Hub Professional.

Company4 stepsUpdated for HubSpot seat pricing
OutcomeThe 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 mapreporting-alerts-032
integration_sync_status changes to Failed leads to Send Slack message to #integration-health. Send Slack message to #integration-health leads to Set last_sync_failure_at = now. Set last_sync_failure_at = now leads to Optional: create investigation task. integration_sync_status changes to Failed Send Slack message to #integration-health Set last_sync_failure_at = now Optional: create investigation task
integration_sync_status changes to Failed leads to Send Slack message to #integration-health. Send Slack message to #integration-health leads to Set last_sync_failure_at = now. Set last_sync_failure_at = now leads to Optional: create investigation task. integration_sync_status changes to Failed Send Slack message to #integration-health Set last_sync_failure_at = now Optional: create investigation task

When to use it, when not to

Use it

  • Use 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.
  • Use it to give the admin team a single channel for sync health instead of checking each integration's own settings screen separately.
Read more on when to use itShow less

Skip it

  • Do 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.
  • Do 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.
Read more on when to skip itShow less

The rest of this spec

Prerequisites · 4 items

Every property with its label, internal name, type and options, plus the assets the workflow needs.

Enrollment · 4 parts

The trigger, the criteria as ticked in the UI, the re-enrollment rule and the suppression list.

Steps · 4 numbered actions

Each action in order with its parameters, branches and delays.

Known pitfalls · 5

Traps seen in production, each with what breaks and what to do instead.

Test plan and UAT script · 3 cases, 3 variants

How to prove it works in a test portal, one case per branch, and a sign-off sheet.

Files · PDF, Markdown, JSON, CSV

The properties JSON creates the fields in one call. The workflow JSON documents the build.

Install · 1 click, switched off

The installer creates the properties and the workflow, switched off, then opens a task for what it cannot create. Nothing is deleted, enabled or enrolled.

Unlock all 565 specs, 149 EUR

One-time, excl. VAT. 30-day refund. Installs in 3 portals. Founding price until 30 November.

Read the free Reporting and alerts spec

Not the workflow you needed?

More in Reporting and alerts

50 specs in this section

See all 50 This category, 39 EUR
FreeSlack alert: deal marked Closed Won (revenue milestone notification)Deal4 steps Weekly digest: workflow enrollment and error summary for admins (automation health)Contact1 step Stage-entry timestamp properties for pipeline velocity reportingDeal5 steps Timeline note logging on critical property change (audit visibility)Deal2 steps

Read 12 complete specs before you pay.

One per category, same format as the paid ones. Email only, no card.

We email the link, then a short note when specs change. Nothing else.

149 EUR199

Full library, 565 specs
Get the full library