Email notifications work. But nobody checks email while they're working. Slack is where the alerts actually get seen.
Svortie now supports Slack as a notification channel. Paste a webhook URL, done.
Setup
- Go to Account and find Notification Channels
- Click Add Channel, pick Slack
- Name it (the Slack channel name works:
#eng-alerts) - Paste your Slack incoming webhook URL
- Hit Send Test to verify
The test message shows up in your Slack channel immediately. If it doesn't, the webhook URL is wrong.
Getting a webhook URL
Slack requires creating an "app" for incoming webhooks. Sounds heavy, takes two minutes:
- Go to api.slack.com/apps and create a new app (from scratch)
- Click Incoming Webhooks in the sidebar, toggle it on
- Add New Webhook to Workspace, pick the channel
- Copy the URL
That URL is all Svortie needs. No OAuth flow, no bot permissions, no app review.
What notifications look like
Slack messages use Block Kit formatting. Each notification includes:
- Status with emoji (checkmark for completed, X for failed)
- Run summary or error message (markdown converted to Slack format)
- Direct link to the run detail page
- Artifact count when files were produced
Notifications fire for agents, workflows, and scheduled runs. Same preferences as email: always, on failure, or never.
Picking channels per agent
Once a Slack channel is added on the account page, it shows up everywhere you configure notifications. Open any agent's settings, expand Advanced Settings, and check the channels you want. Same for workflows and schedules.
Mix and match. Send failures to Slack, successes to email. Or both everywhere. Each agent can have different channels selected.
Try it
Head to Account, add a Slack channel, and send a test. Then pick it on your next agent run.