Notifications

Turbine can send human-readable notifications to services like Slack, Discord, Telegram, and email when workflows complete. Powered by Shoutrrr, configured via the pt_alert_channels collection — manageable from the dashboard under Settings > Notifications.

For programmatic integrations with structured JSON payloads, see Webhooks.

Creating a Channel

Create a record in pt_alert_channels with:

Field	Type	Description
name	string	Friendly label, e.g. "Slack #alerts" (required)
url	string	Shoutrrr URL (required)
events	json	Array of event names to subscribe to (required)
enabled	bool	Whether the channel is active

Supported Services

Service	URL Format
Slack	slack://xoxb:token@channel
Discord	discord://token@webhookid
Telegram	telegram://token@telegram?chats=@channel
Email (SMTP)	smtp://user:pass@host:port/?to=recipient
Teams	teams://token
Gotify	gotify://host/token
Ntfy	ntfy://topic
Pushover	pushover://token:apitoken@user
Matrix	matrix://user:pass@host
Generic webhook	generic+https://example.com/endpoint

See the Shoutrrr docs for the full list of 21 supported services and their URL formats.

Events

Same events as Webhooks:

Event	Fires when
workflow.SUCCESS	Workflow completed successfully
workflow.ERROR	Workflow failed with an error
workflow.CANCELLED	Workflow was cancelled
workflow.WAITING_FOR_APPROVAL	Workflow is paused at an approval gate
workflow.MAX_RECOVERY_ATTEMPTS_EXCEEDED	Workflow exceeded max recovery attempts (dead letter)
workflow.*	Any of the above events

Message Format

Notifications are plain-text messages:

[Turbine] Workflow "orderProcessing" (abc123) completed successfully
[Turbine] Workflow "orderProcessing" (abc123) failed: connection refused
[Turbine] Workflow "orderProcessing" (abc123) cancelled
[Turbine] Workflow "orderProcessing" (abc123) is waiting for approval
[Turbine] Workflow "orderProcessing" (abc123) exceeded max recovery attempts

Testing

Each channel has a Test button in the dashboard that sends a test notification to verify the URL is configured correctly.

Delivery

WARNING

Notifications are fire-and-forget. Failed deliveries are logged but not retried. For critical alerting, consider using a service with built-in retry like a webhook endpoint.

Notifications are dispatched asynchronously and don't block workflow completion.

Security

Notification URLs contain embedded credentials (tokens, passwords). URLs are masked when read through the API — only the service scheme is visible (e.g. slack://***). The full URL is stored in the database and used only for dispatch.