Outcome. An SLA breach on a live ticket reaches whoever is on call through the paging tool the team already trusts for incidents, instead of depending on someone actually reading an internal HubSpot email notification in time.
Workflow map
Enrollment, branches and actions at a glance
tickets-sla-045
flowchart TD
A[sla_breach_flag becomes true, priority Urgent] --> B{paging_webhook_sent already true?}
B -->|yes| C[No action, already paged]
B -->|no| D[Webhook POST to paging tool]
D --> E[Set paging_webhook_sent = true]
When to use it, when not to
- UseUse it when the team already runs an on-call rotation in a dedicated paging tool (for example a system that pages by phone, SMS, or a mobile push, not just email) and wants SLA breaches on customer tickets to page the same way a server alert would.
- UseUse it once tickets-sla-003 or tickets-sla-005 is already live and reliably firing on breach; this fiche adds an external paging channel on top of that internal alerting, it does not replace the underlying breach detection.
- SkipDo not use it for every ticket breach indiscriminately; paging tools are built for urgent, wake-someone-up situations, reserve this for Urgent-priority breaches or a defined subset, or the team starts ignoring pages the way they might ignore a noisy inbox.
- SkipDo not use it without confirming the native Webhook workflow action is actually available on your tier; sending an outbound webhook from a workflow is an Data Hub Professional capability, not included in Service Hub Professional alone. The send a webhook action requires Data Hub Professional or Enterprise (https://knowledge.hubspot.com/workflows/choose-your-workflow-actions).
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.2 numbered actions
Known pitfallsTraps seen in production, each with what breaks and what to do instead.4 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 tickets and sla 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.
