Field notes
Telegram + GPT bot
Chat bots with AI: coverage is partial, outbound still matters.
What Crash Labs saw
Gate WARN · risk 43/100 · 1 outbound action(s) · coverage 100%.
"Untitled workflow" can launch with caution (WARN): 6 high finding(s), risk 43/100. Start with: Nobody gets alerted when this workflow fails.
Why this breaks in production
high
Nobody gets alerted when this workflow fails
You may think an email or invoice finished when it actually stopped halfway - and no one is paged.
Fix → In n8n Settings, set an Error Workflow (or add an Error Trigger flow) that Slack/emails your team with the failed run link.
high
"Telegram" can fail with no backup path
Customers get silence, duplicate retries, or a half-finished experience with no internal alert.
Fix → Turn on retry for transient SMTP/API errors, and route hard failures to an error branch that alerts someone.
high
Retry survival: 1 side effect(s) still fire on delivery #2
Retry survival: 1 side effect(s) survived run 2.
Fix → Add dedupe keys, idempotency, and rate limiting / a queue before outbound sends and Stripe writes.
high
Simulation failed: Spam burst (10 triggers)
10 trigger fires produced 10 external action(s) (1+1+1+1+1+1+1+1+1+1 per run). 9 still fired after delivery #1. Ledger: 10 near-identical chat messages posted.
Fix → Add dedupe keys, idempotency, and rate limiting / a queue before outbound sends and Stripe writes.
Run this pattern on your workflow
Upload your n8n JSON at Crash Labs. Same gate, blast-radius ledger, and shareable report for clients.