Abrova
☰ Docs menu · Slack

Slack Integration

Get real-time Abrova Trace error notifications in your Slack workspace via incoming webhooks. Set up the webhook, connect it in Abrova Console, and test it.

Last updated: 27 Oct 2026

Get real-time error notifications in your Slack workspace. Learn how to create a webhook, connect it, and what the notifications look like.

What you'll learn.
  • How to create a Slack incoming webhook
  • Configure Slack notifications in AbrovaTrace
  • What the notifications contain
  • Test your Slack integration
Reaching Slack from Iran.

Slack is a service outside Iran and may be unreachable from some networks in Iran. To set it up and to read the alerts you need a connection that can reach Slack, and deliveries only arrive while hooks.slack.com answers — failed deliveries show in the integration's delivery log. If that is a problem for your team, use the Email or Webhook integration instead, or alongside it.

Which channels your project can use is shown on the Trace → Integrations page in Abrova Console.

Create a Slack Webhook#

  1. Go to api.slack.com/apps
  2. Click "Create New App" → "From scratch"
  3. Name your app "AbrovaTrace" and select your workspace
  4. Navigate to "Incoming Webhooks" in the sidebar
  5. Toggle "Activate Incoming Webhooks" to ON
  6. Click "Add New Webhook to Workspace"
  7. Select the channel where you want notifications
  8. Copy the webhook URL

Your webhook URL will look like: https://hooks.slack.com/services/...

Configure in AbrovaTrace#

  1. In Abrova Console, open Trace → Integrations (integrations belong to the selected project)
  2. Click "Add integration" and choose Slack (or "Connect" on the Slack card)
  3. Enter a Name and paste the webhook URL
  4. Click "Save and send test" to save and verify it (or "Save channel")
OptionTypeRequiredDescription
NamestringYesFriendly name (e.g., #alerts)
Incoming webhook URLstringYesFull Slack webhook URL from step 1. Must be on hooks.slack.com (https://hooks.slack.com/...)

After saving

Managing integrations (add, edit, switch on/off, delete, test) needs the admin or owner role; every role can see them and their delivery log. See Roles & Permissions.

The webhook URL is never shown again once saved: the form shows it as set, with only https://hooks.slack.com/… visible. Leave it as it is to keep the saved URL, or press Replace to paste a new one. Only Slack's own webhook addresses (https://hooks.slack.com/...) are accepted.

Notification Format#

Slack messages from AbrovaTrace include:

  • Header — AbrovaTrace bot username + ⚠️ icon
  • Alert title — New Error: <error message>, linked back to the error
  • Metadata — project, environment, first-seen timestamp, occurrence count

New-error messages are sent the first time an error is seen. Spike detection also posts here, and alert rules and cron monitors post here when you pick this channel for them.

Best Practices#

Create Dedicated Channels

Separate channels for different environments (#prod-errors, #dev-errors)

Reduce Noise with Ignore Rules

Drop known noisy errors so they never notify

Use Thread Replies

Keep error discussions organized in Slack threads

Troubleshooting#

Not receiving notifications?
  • Verify webhook URL is correct — it must start with https://hooks.slack.com/
  • Check the integration is switched on in Trace → Integrations
  • Ensure Slack app is installed in your workspace
  • Try the "Send test" button again
  • Check the delivery log of the integration: a timeout or connection error means Slack could not be reached
Messages going to wrong channel?
  • The webhook URL determines the channel
  • Create a new webhook for the correct channel
  • Edit the integration in Trace → Integrations and press Replace on the webhook URL
Getting rate limited?
  • Slack has rate limits for incoming webhooks
  • Use error grouping to reduce notification frequency
  • Use Ignore Rules to drop noisy errors
Was this page helpful?
Report a problem