Back to Help Center

Notification Settings

Notification Settings is where you set the default destinations for trigger results (success or failure). Three similarly-named surfaces sit side by side in Zemu — Notification Settings, the Notification Center, and Inbound Channels — and confusing them is the most common cause of "my notifications aren't working."

Overview

How Notification Settings, the Notification Center, and Inbound Channels are different surfaces; how timing dominates destination toggles; per-trigger overrides; and the profile-reset gotcha.

Basics

Three different surfaces with similar names

These all live in different places and do unrelated jobs.

  • Notification Center (/notifications) — the inbox where you read notifications addressed to you. Has All / Unread filters (shown above)
  • Notification Settings (/settings/notifications) — where you decide where trigger results are sent (next sections)
  • Inbound Channels (/channels) — the entry point for launching AI workers from Slack, etc. Unrelated to outbound notifications

"I'm not getting Slack notifications" and "I can't launch a worker from Slack" are different problems on different pages — figure out which one before changing settings.

Three timings × four destinations

/settings/notifications is split into two blocks.

When to notify (radio, three options):

  • Every run — notify on success and failure
  • Failures only — notify only when a run fails
  • Never — do not send notifications

Destinations (four toggles):

  • Email — sent to your registered email
  • Slack — needs a Slack profile created under Inbound Channels
  • Discord — needs a Discord profile under Inbound Channels
  • LINE WORKS — needs a LINE WORKS profile under Inbound Channels

A common pattern: "Every run" for scheduled reports you want to see succeed, "Failures only" for monitoring-style automation to keep noise low.

"Never" overrides destination toggles (timing wins)

Gotcha: timing dominates the destination toggles.

  • Setting timing to "Never" stops email even with the email toggle on.
  • To silence external chat but keep email, leave timing on "Every run" or "Failures only" and turn off only the Slack / Discord / LINE WORKS toggles.

Resolution order overall:

  1. Timing (every run / failures only / never) is the gate
  2. Destination toggles apply within whatever timing allows
  3. Per-trigger overrides can deviate from the account default for a specific trigger

Combining account defaults with per-trigger overrides lets you say "failures-only Slack for everything, but every run via email for the monthly report."

External chat needs a profile first; profile change resets the channel

To enable Slack / Discord / LINE WORKS destinations, you need a connection profile created on the Inbound Channels page first. Without one, flipping the toggle does nothing — the destination card has no profile to point at.

UI behaviors worth knowing:

  • Changing the profile resets the channel selection (so channels from one workspace don't bleed into another)
  • Slack and Discord pull channel lists from the API; you do not type channel IDs
  • LINE WORKS sometimes can't list channels; in that case it falls back to manual channel-name entry

Verification: after saving, run a representative trigger manually once and confirm the message lands in the configured profile × channel.

Checklist

  1. Can you explain the difference between Notification Settings, the Notification Center, and Inbound Channels to a new team member?

  2. Are you treating timing (every run / failures only / never) as the gate that overrides destination toggles?

  3. Have you set up the underlying Inbound Channels profile for each external chat destination, and accounted for the channel-reset behavior on profile change?