The Workflow Library

Library / Reporting and alerts / reporting-alerts-019

Slack alert: workflow goal completion milestone reached

Reporting and alertsContactMarketing Hub ProfessionalSimple~20 min to buildFull spec

Outcome. The marketing channel gets a Slack message the moment a contact meets a defined nurture milestone, so goal completions are visible without checking each workflow's goal-performance tab.

Workflow map Enrollment, branches and actions at a glance reporting-alerts-019
flowchart TD
    A[Contact meets milestone criteria] --> B{goal_milestone_alerted = true?}
    B -->|yes| Z[Exit, already alerted]
    B -->|no| C[Send Slack message to #marketing-milestones]
    C --> D[Set goal_milestone_alerted = true]
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse it when a nurture or lead-scoring workflow already has a meaningful goal set (Automation > workflow settings > Goal) and the team wants real-time visibility on who reaches it, not just the aggregate goal-performance percentage.
  • UseUse it for milestones worth celebrating or acting on quickly, such as a demo request or a pricing page visit combined with a score threshold.
  • SkipDo not use it for a milestone that fires constantly, hundreds of contacts a day. A high-frequency goal produces Slack noise. Use a scheduled digest instead, following the reporting-alerts-004 pattern.
  • SkipDo not confuse this with reporting-alerts-047, which covers a specific lifecycle stage change. This fiche covers any custom-defined goal criteria, which may or may not be a lifecycle stage.
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.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 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.