Slack Integration

Slack workflows are rolling out for selected beta workspaces. Create the hosted account first, then email us with the workspace and use case if your team needs early access.

Slack support is in limited beta.

What is planned for Slack?

Team workflow fit

Keep incident context where your team already works once your workspace is enabled.

Channel alerts

Route beta alerts to an ops channel for early customer workspaces.

Threaded conversations

Threaded incident discussions are part of the Slack rollout.

Block Kit UI

Interactive controls are limited during beta and will expand over time.

Workspace permissions

Workspace-level access controls are planned for the full Slack release.

Beta access

01

Create an account and request access

Sign up with email, then tell us your Slack workspace and the commands you need first.

02

Enable beta app

We enable selected workspaces as the private beta expands.

03

Connect server

Install the agent and connect the workspace to your mttrly account.

04

Start limited rollout

Use the enabled beta commands and alerts while we expand coverage.

Slash commands

Slack command coverage is limited during private beta; full Block Kit parity is still rolling out.

/start — Connect and initialize the bot
/setup — Add a server
/servers — List connected servers
/setup_deploy — Configure a deploy profile
/healthcheck — Run the overall server health check
/logs — View scoped service logs
/restart — Request a service restart with approval
/containers — List Docker container status
/nginx — Test the nginx configuration
/certs — Check SSL certificate status
/help — Show the available beta command catalog

Best for

→ DevOps teams — incident response in the channel where discussion happens

→ Startups — small team, one Slack, ops included

→ On-call rotations — alerts go to the right channel, right people

→ Remote teams — async server management across timezones