Back to Help Center

Notification Settings

Notification settings manage the default notification rule for trigger run results. Choose whether to notify on all runs, failures only, or never, then configure email, Slack, Discord, and LINE WORKS destinations. To send to Slack, Discord, or LINE WORKS, create a routing connection profile first and select the destination channel.

Overview

Set the default destinations for trigger run results across email, Slack, Discord, and LINE WORKS.

Basics

Notification condition

Trigger notification condition chooses all runs, failures only, or none. Selecting none disables the email and external chat destination switches. Use all runs for scheduled reports where success should be visible, and failures only for monitoring-style automation to reduce noise.

Email notifications

The Email notifications switch controls whether trigger results are also sent by email. It is useful as a baseline destination even before external chat is connected. If the condition is none, email is not sent.

Slack / Discord / LINE WORKS

Enable each destination card, then choose a profile and channel. Changing the profile resets the selected channel. Slack and Discord use fetched channel lists, while LINE WORKS can allow manual channel entry when no channels are returned. If no profiles appear, create the connection from Inbound Channels or native integrations first.

Per-trigger overrides

This screen controls account defaults. Use a trigger's notification override when one trigger needs a different condition or destination. Inbound channel route settings control how Slack or other chat tools start workers, which is separate from trigger result notifications.

Checklist

  1. Confirm whether the condition is all runs, failures only, or none.
  2. For Slack, Discord, and LINE WORKS, confirm both profile and channel are selected.
  3. After saving, run a representative trigger and confirm the default or override destination receives the result.