Outcome. The team lead sees one place every morning listing every ticket approaching an SLA breach, instead of finding out ticket by ticket after each one has already missed its target.
Workflow map
Enrollment, branches and actions at a glance
tickets-sla-026
flowchart TD
A[SLA status becomes Due soon] --> B[Set sla_risk_flag = true]
B --> C[Create immediate follow-up task for owner]
C --> D{Status later reverts to normal?}
D -->|yes| E[Set sla_risk_flag = false, drops off list]
D -->|no, breaches or closes| F[Ticket leaves the active list via the Closed filter, or tickets-sla-003 takes over on actual breach]
When to use it, when not to
- UseUse it once SLA targets are configured on the pipeline and the "due soon" status is populated, and the team lead wants a single daily view rather than reacting to tickets-sla-003's per-ticket breach alerts after the fact.
- UseUse it as the "before it breaches" companion to tickets-sla-003's "after it breaches" alert; the two serve different moments and are worth having together.
- SkipDo not use it expecting a single native workflow action to compose one email listing many tickets; HubSpot's workflow engine runs its actions per enrolled record, it does not natively aggregate several records into one message, see Known pitfalls for how this fiche actually delivers a true digest.
- SkipDo not use it if SLA "due soon" status is not available on your tier; without it, this workflow has nothing reliable to flag on.
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.5 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 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.
