u/kumarshikhardeep1

I'm curious how people running business-critical Zaps handle monitoring.

Error notifications are one thing, but what about:

• Zap runs but output is wrong
• trigger stops arriving
• API behavior changes
• Zap hasn't run when it normally should

How are you handling these cases?

I'm curious how people running business-critical Zaps handle monitoring.

Error notifications are one thing, but what about:

• Zap runs but output is wrong
• trigger stops arriving
• API behavior changes
• Zap hasn't run when it normally should

How are you handling these cases?

I've been thinking about a problem that becomes painful once you have dozens of production workflows:

How do you know when an automation has silently stopped doing what it should?

Execution errors are relatively easy to detect.

The harder cases are:

• workflow executes successfully but produces bad/empty output
• webhook stops receiving events
• upstream API changes behavior
• workflow hasn't executed for an unusually long time
• downstream system stops receiving expected data

Curious how people running n8n in production handle this today.

Do you rely on n8n's built-in execution/error handling, custom alerting, external monitoring, or something else?