Send Slack and Discord notifications with Notification triggers

A notification trigger is a moment that sends a message to your team. It might be a new feature request or a failed step in one of your monitored processes. You manage them on the Notification triggers page in the sidebar, and each one can post to the Slack channels and Discord destinations you have connected.

Before you start

Connect at least one destination first. Open Integrations and set up Slack, Discord, or both. If none are connected, the notification dialog tells you "No Slack or Discord destinations yet" and offers an Open integrations button.

You also need permission to manage integrations to change which destinations a trigger uses. Without it, the dialog shows a notice and you cannot save changes.

Product triggers

The Product triggers card lists built-in Releaseo moments. They need no tracking code. Today the list contains:

Feature request created: a new feature request was submitted to your board.
Monitor step failed: a monitored flow step reported a failure. It fires at most once every 15 minutes per step, so you get an alert without the noise.
Monitor run completed: a monitored flow run finished successfully. It fires for every completed run, so it can be noisy for high-traffic flows.

A green chip such as "2 destinations" shows how many destinations already receive that trigger.

Your own triggers

Below the product triggers, the Notification trigger catalog lists triggers you define yourself. These are your own events, sent from your code with releaseo.track(). To create one, select Create trigger. The article "Track custom events" covers payload fields and the Event Profile.

Send a trigger to Slack or Discord

On the Notification triggers page, find the trigger. For a product trigger, select Notifications on its row. For one of your own, open the row's actions menu and choose Notifications. The menu shows a count, for example "Notifications (2)", when destinations are already set.
Under Send to, tick the destinations. Slack channels appear as #channel, with the workspace name beside them. Discord destinations appear in their own group.
Optionally edit the message (see below). The Preview panel on the right updates as you type.
Select Save notifications.

Paused or disconnected destinations cannot be selected. Fix them under Integrations first.

To stop sending a trigger everywhere, select Turn off notifications and confirm.

Customize the message

Title & description: switch Include title and Include description on or off. Type your own text in Title and Description to replace the defaults. Clear the fields to go back to the defaults.
Additional message: add optional details below the title. Type { to insert a field from the event, such as a flow name or error message. The editor supports bold, italic, strikethrough, code, and links.
Clear additional message empties the extra text.
Preview with missing data shows how the message looks when a field has no value.

Copy is saved per trigger and destination. If you pick several destinations that currently have different copy, the dialog warns you, and saving applies what you see to all of them.

Message limits

To protect your channels, the dialog shows a per-minute cap on messages (the default is 6 per minute). Extra activity is rolled up into a summary message instead of flooding the channel.

Manage a trigger

Open the actions menu on a row in the catalog to view its profile, copy its tracking snippet, edit it, set it active or inactive, or archive it. Archived triggers stay visible in history but should no longer be used.

Troubleshooting

The Create trigger button is disabled. You need at least one active option under Static data > Trigger types, and permission to manage events.
I can't choose a destination. It is probably paused or disconnected. Open Integrations and reconnect it.
Nothing arrives in Slack or Discord. Check that the destination is enabled and that the trigger is saved to it. Open the trigger's Notifications dialog and confirm the destination is ticked.