Use Slack Commands
Manage incidents directly from your Slack workspace with slash commands
Harness AI SRE provides a set of Slack slash commands that enable you to manage incidents directly from your workspace.
These commands work within incident channels and provide quick access to common incident management actions.
Prerequisites
Before using Slack commands, ensure your organization has completed the Slack integration setup.
Available commands
Incident management
/harness new
Create a new incident
/harness edit
Edit the incident associated with the current channel
/harness close
Close the incident associated with the current channel
/harness reopen
Reopen a closed incident associated with the current channel
Incident information
/harness summarize
Display the current incident summary (visible only to you)
/harness key-events
Edit key events for the incident associated with the current channel
Collaboration
/harness attach-meeting
Link a video conference to this incident and automatically transcribe and detect key events from the discussion
/harness runbook
View runbook steps and run scripts for the incident associated with the current channel
Runbook execution
/harness run <slug>
Execute a runbook by its slug (requires Slack authentication)
/harness run
List all available runbook slugs for the current project
Page responders
/harness page
Page a user, user group, or service
/harness page-status
View page status for the incident associated with the current channel
Usage examples
Create a new incident
Enter /harness new in any Slack channel to open the incident creation dialog. Fill in the incident details and submit to create a new incident with an associated Slack channel.
Run runbooks with slugs
Runbook slugs enable you to execute automated response procedures directly from Slack without navigating the Harness UI. This feature is designed for on-call responders who need to trigger runbooks instantly during high-pressure incidents.
Prerequisites
Slack authentication: You must authenticate Slack with Harness AI SRE. The first time you use a slug command, you will be prompted to authenticate.
Runbook configuration: Runbooks must have slugs configured by your administrator. Go to Create Runbooks to learn how administrators assign slugs.
Execute a runbook by slug
From an incident Slack channel, enter:
Replace <slug> with the runbook's short identifier (for example, /harness run restart-pods).
What happens:
Slack validates your authentication.
Harness looks up the runbook associated with the slug for the current project and incident.
The runbook executes, and you receive confirmation in Slack.
Execution progress appears in the incident timeline.
List available slugs
If you do not know which slugs are available, enter:
Output:
If slugs are configured, you will see a list formatted as:
If no slugs are configured, you will see:
The list shows all slugs available for the current project and incident context.
Best practices
Follow these practices to run runbook slugs reliably during an incident:
Memorize common slugs: Frequently used runbooks (for example,
restart-pods,rollback) build muscle memory and reduce MTTR.Use descriptive slug names: Short but meaningful slugs make it easier to remember which runbook does what.
Authenticate early: Complete Slack authentication during onboarding, not during an active incident.
Verify before execution: Use
/harness run(no argument) to confirm the slug name before executing.
Page on-call responders
From an incident channel, use /harness page to page a user, user group, or service. When paging a service, notifications are sent through all configured contact methods (email, SMS, phone, mobile app) based on the service's escalation policy.
To use paging commands, ensure your team has configured on-call schedules and escalation policies.
View incident summary
Use /harness summarize in an incident channel to get a quick overview of the current incident status, including severity, impacted services, and timeline of key events. The summary is displayed as a Slack ephemeral message visible only to you.
Next steps
Go to Slack Integration for Runbooks to set up the Slack integration.
Go to On-Call Management to configure on-call schedules and escalation policies.
Go to AI Scribe Agent to see how incident activity is captured automatically.
Last updated
Was this helpful?