Set up failure alerts for workflows

Nicolas Audet
Nicolas Audet
  • Updated

Overview

You can set notifications to receive real-time alerts when a workflow fails. This helps your team respond quickly, without needing to monitor execution logs or wait for users to report issues.

Notifications are fully customizable and can be sent via Slack, Microsoft Teams, or email.

Understanding how it works

  • Triggers automatically when any native workflow fails
  • Captures key details like:
    • Who created the workflow
    • Who created the execution that failed
    • Which nodes failed
    • Error codes and messages
  • Sends a customizable message via Slack, Teams, or email
  • Skips child workflow failures to avoid spam

Only native workflows are supported. This does not apply to Operations.

How to get it added to your organization

This alerting workflow is added manually by gaiia.

  1. Email support@gaiia.com to request the workflow. A member of the gaiia team will add it to your environment.
  2. If you don’t have Builder access, gaiia can help you customize the workflow. 

Customization options

With Builder access, you can customize how notifications are routed based on error type, severity, or affected system.

For example, you could:

  • Send API errors to engineering via Slack
  • Send billing issues to finance by email
  • Notify the workflow creator or executor only

Advanced routing requires Builder access and use of Condition nodes.

Requirements

  • The template must be added manually in your environment by gaiia
  • Microsoft Teams notifications require the native Teams integration to be enabled
  • Slack notifications require a Slack bot to be set up in your environment

The current email node version is added manually. If you’re unsure which one to use, contact support for guidance.

Was this article helpful?

Have more questions? Submit a request