PathOctober 2026
Slack alert when a journey fails: proof, screenshot, no noise
An uptime alert says “500”. A Flow alert says “step 3 — Pay button missing” with a screenshot. That is what Slack should get so you can act in five minutes.
Noise kills on-call
Ping filters real network incidents. Flow only alerts when the business journey breaks. Together you avoid a Slack channel flooded with HTTP false positives.
Without that split, the team mutes the channel — and misses the useful alert the day the Shopify funnel actually breaks.
What a good alert contains
- Journey name and failing step.
- Screenshot at the moment of failure.
- Link to the Pathly run to replay.
Example: what lands in Slack
Here is the typical message a team gets when Flow breaks on checkout (fictional names). It is not a bare “HTTP 500”: the step and the proof are inside.
:red_circle: Pathly Flow — Checkout boutique · FAIL Étape 3/5 — Cliquer « Payer » · sélecteur introuvable Région OK · Panier OK · Payer ✕ Région eu-west · durée 18,4 s Capture : checkout-payer-missing.png Run : https://app.pathlyhq.com/runs/ex-7f3a Ping HTTP de la même URL : encore vert (200)
With that, on-call opens the run, sees the screenshot, fixes the selector or theme — without digging through CloudWatch. HTTP uptime stays green: only the business journey broke.
How to set it up
Record the critical journey, connect Slack or Teams by plan, keep email as backup. Test by deliberately breaking a selector in staging before prod.
Pathly sends email alerts from Solo; Slack / Teams by plan. The goal is not more messages — it is the right message with proof.