<notify>

<notify> contains one or more built-in or imported custom notification provider tags.

Why use it

Use it to connect durable approval authority or observational lifecycle events to communication channels without placing credentials in message content.

Common use cases

• Deliver approval actions to several destinations.
• Alert operators after a workflow failure.
• Use a project-specific reusable notification transport.

Syntax

<notify>
  <telegram
    chats="123456789"
    bot-token="{{secrets.TELEGRAM_BOT_TOKEN}}"
  />
  <discord
    channels="200000000000000001"
    bot-token="{{secrets.DISCORD_BOT_TOKEN}}"
  />
</notify>

Rules and behavior

• Inside an approval, every delivery has its own single-use capability and all deliveries settle the same approval.
• One successful approval delivery is enough to wait; if every delivery fails, the run fails.
• Inside lifecycle hooks, notifications are informational and failures become lifecycle warnings.
• Lifecycle message templates may use bounded scalar context and lifecycle placeholders, but never secrets.

Related documentation

• Notifications
• Human approval
• Reusable WOML definitions