Notifications

Each project can have any number of notification channels, each posting to a Discord or Slack incoming webhook.

Adding a channel

On a project’s Notifications tab, click Add Channel and fill in:

• Channel Name: a display name.
• Type: Discord or Slack.
• Webhook URL: the incoming webhook URL from Discord or Slack.
• Notify On: which events this channel should fire for: deployment started, succeeded, and/or failed. Success and failure are checked by default; start is not.

Each channel has a Test button that sends a sample message (“This is a test notification from Conveyor.”) so you can confirm the webhook works before relying on it.

What triggers each event

• Deployment started: fires once per deployment, right after it’s created (whether triggered manually, by webhook, or by the API), before any steps run.
• Deployment succeeded: fires when every step completes successfully and (if configured) the health check passes. The message includes the deployment’s duration.
• Deployment failed: fires when a step fails, disk space is critically low, or the health check fails after activation.

Rollbacks send their own start/success/failure notifications through the same channels, using the same event flags.

Webhook URL restrictions

For safety, Conveyor only accepts webhook URLs on the expected host for each channel type, over HTTPS:

• Discord: discord.com, discordapp.com, canary.discord.com, or ptb.discord.com.
• Slack: hooks.slack.com.

A webhook URL pointing anywhere else is rejected when a notification is sent.

Message format

• Discord messages are sent as {"content": "..."}, so Discord’s Markdown (bold, etc.) renders normally.
• Slack messages are sent as {"text": "..."} to a Slack incoming webhook.