Operio Doc
Integrations

Slack

Send test failure notifications to a Slack channel

Connect Slack to your team, choose a default channel per project, and Operio posts a message whenever a test case fails during a run.

What the Slack integration does

When a test case fails, Operio sends a message to the project's configured Slack channel with:

  • Project name
  • Test case name
  • Environment name
  • A failure summary, when available
  • A link to the test case result in Operio

Everything is automatic after setup; there's nothing to trigger manually.

Note: Notifications fire per failed test case, not per completed test run. A run with three failures produces three messages.

Connect Slack to your team

  1. Open Settings → Integrations in the project sidebar.
  2. Find Slack and click Connect.
  3. Complete the OAuth flow in Slack and authorize Operio.
  4. You're redirected back to Operio, and the card shows Connected with your Slack workspace name.

The connection is shared across all projects in the team, and disconnecting removes it for every project at once.

OAuth scopes

Operio requests these Slack scopes:

  • chat:write and chat:write.public to post messages to channels
  • channels:read and groups:read to list channels during configuration
  • team:read to identify the connected workspace
  • im:write, requested for future use; Operio doesn't currently send direct messages

Configure a default channel

After connecting at the team level, each project needs a default channel:

  1. On the Slack integration card, click Configure.
  2. Select a channel from the list.
  3. Click Save.

If Slack is connected but no channel is selected, the card shows Action required and notifications are skipped until you pick one.

When notifications are sent

Operio sends a Slack message when all of these are true:

  • A test case result finishes with a failed status
  • The project has a default Slack channel configured
  • The team's Slack integration is connected

Passed and skipped test cases don't produce notifications. Monitor-triggered runs and manual runs behave the same: a failure in either kind sends a message.

Message format

Here's what a notification looks like:

❌ Test case failed

Project: My App
Test case: Login with valid credentials
Environment: Staging
Summary: Expected redirect to dashboard

View test run: https://...

Disconnect Slack

  1. Open Settings → Integrations.
  2. On the Slack card, click Disconnect.

This removes the team-level connection. Per-project channel settings stay stored, but notifications stop until Slack is reconnected.

Troubleshooting

SymptomLikely cause
No messages after a failureDefault channel not configured, or Slack not connected
Channel not in the listThe bot may lack access. Invite the Operio app to private channels
"Action required" badgeConnect Slack, then configure a default channel

If the OAuth flow fails or gets canceled partway through, nothing is stored; just click Connect again. If a connection that used to work stops sending messages, disconnect and reconnect to refresh the authorization.

On this page