The Workflow Library

Library / Reporting and alerts / reporting-alerts-047

Slack alert: contact reaches a key lifecycle stage milestone (e.g. became Customer)

Reporting and alertsContactMarketing Hub ProfessionalSimple~20 min to buildFull spec

Outcome. The team sees a Slack message the moment a contact reaches a chosen lifecycle stage milestone, most commonly becoming a Customer, so conversion events are visible in real time without opening the CRM.

Workflow map Enrollment, branches and actions at a glance reporting-alerts-047
flowchart TD
    A[Lifecycle stage changes to Customer] --> B{Already alerted?}
    B -->|yes| Z[Exit, no duplicate alert]
    B -->|no| C[Send Slack message to #milestones]
    C --> D[Set lifecycle_milestone_alert_sent = true]
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse it for real-time visibility on a specific, high-signal lifecycle transition, becoming a Customer, becoming an MQL, or another stage the team wants to celebrate or act on immediately.
  • UseUse it to keep non-CRM stakeholders (marketing, leadership, customer success) aware of conversion events without dashboard access.
  • SkipDo not use it for every lifecycle stage change; pick one or two milestones that matter, or the channel turns into noise. Pair with reporting-alerts-020 for the full transition-matrix view instead.
  • SkipDo not treat this as your system of record. It is a notification, not a reporting export.
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.3 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.