Alert Before Users Notice: Detect Rising API Latency Early
Catch performance regressions early — monitor your API's response times and alert the on-call engineer when latency creeps above healthy levels.
- 1
Probe the Endpoint
Add a
Schedule Triggerevery minute and anHTTP Requestnode measuring the response time of a key endpoint. - 2
Track a Rolling Average
Add a
Codenode maintaining a rolling latency baseline in static data. - 3
Detect Degradation
Add an
IFnode continuing when recent latency exceeds the baseline by a set factor for several consecutive checks. - 4
Page On-Call
Add a
PagerDutynode creating an incident with the current and baseline latency. - 5
Activate and Tune
Activate the workflow and adjust thresholds so transient blips don't page needlessly.
Frequently asked questions
Why require consecutive breaches?
Requiring a sustained rise avoids paging for a single slow request or momentary spike.
Can I monitor multiple endpoints?
Yes — loop over a list of endpoints, each with its own baseline, in the same workflow.
Verify Every Shoot's Footage Is Backed Up Before You Leave Set
A videographer's nightmare is discovering a corrupt card after the client's one-time event. Log each card's offload and verify redundant backups before leaving set.
n8nTelegramGoogle SheetsReplay Failed Webhooks From a Dead Letter Queue Automatically
Failed inbound webhooks silently drop events that never get processed. Capture failures into a dead letter queue and replay them automatically once the issue clears.
n8nSlackBlock Disposable Email Signups From Poisoning Your Trial Metrics
Disposable-email trial signups inflate your funnel and abuse free tiers. Detect throwaway domains at signup and route them for verification before they count as trials.
n8nSlack
Keep every recipe free
FlowRecipesHub is free and always will be. If a workflow saved you time, chip in what you like — it helps us keep the lights on and build the next batch of automations for everyone.
Secure checkout via Paddle · one-time, no account needed