Connect Slack

Guidely posts to Slack in two ways, and you can use both:

  • The Guidely Slack app (recommended): add it once for your workspace, then pick its channels anywhere Guidely posts. Error alerts get buttons to resolve, ignore and assign the issue from Slack, members can get their own notifications as direct messages, Guidely links pasted in Slack get previews, and /guidely looks up an issue.
  • Incoming webhooks: one per channel, pasted from Slack. They post the same messages, without the buttons, DMs, previews or /guidely. Existing webhook channels keep working; nothing changes when you add the app.

1. Add Guidely to Slack

A Guidely workspace admin opens Integrations → Slack in any project and clicks Add to Slack, then approves the app in Slack (adding an app may need a Slack admin's approval, depending on your Slack workspace's settings). Slack sends you back to Guidely, which shows the connected Slack workspace.

  • One Guidely workspace connects to one Slack workspace. Add to Slack again replaces the connection (to use another Slack workspace, or to grant permissions a newer version of the app asks for).
  • The app can post to public channels straight away. For a private channel, invite it first: type /invite @Guidely in that channel.
  • Don't see Add to Slack? Only workspace admins have it; ask one to add the app. If nobody in the workspace sees it, the Slack app isn't set up on this Guidely deployment yet: use incoming webhooks meanwhile.

2. Pick channels

Each project chooses its own channels. Under Integrations → Slack, pick a channel and connect it (↻ refreshes the list after you create or invite the app to a channel). Connecting channels needs the Developer settings permission.

Then choose the channel where you set up what posts:

WhatWhere you pick the channel
Error alerts (issue and metric alerts)Errors → Alerts → a rule's actions (alerts.md)
Cron and uptime monitor incidentsMonitor → Crons / Uptime → a monitor's notifications (monitors.md)
Deploys and new releasesMonitor → Releases → Deploy notifications (releases.md)
Replay alertsReplays → Alerts (product-analytics.md)
Scout conversation requestsScout settings (scout.md)
Complaints and feature requestsTheir webhook and Slack settings (complaints.md, feedback.md)

Every channel picker lists the app's channels and your webhook channels together. It also offers the app's channels that aren't connected to the project yet: picking one connects it.

3. Act on alerts from Slack

Error alerts posted through the app have buttons next to View issue and Watch replay:

ButtonDoes
ResolveResolves the issue. Resolve in the next release is in the ⋯ menu.
Ignore…Forever, for 1 hour, for 24 hours, or until 100 more events
Assign to me / Assign to…Assigns the issue to you, or to the teammate you pick in Slack
ReopenShown after a resolve or ignore
Mute monitorOn cron and uptime incidents

After a click, the message updates in place with what happened, who did it and when.

Who can click. Guidely matches the person in Slack to a member of your Guidely workspace by the confirmed email address of their Slack account, and acts as that member: with their permissions (triage needs Manage insights & alerts, which viewers don't have), in the audit log and the issue's activity under their name. Anyone else (a Slack user whose email isn't a member's, someone from another company in a shared Slack Connect channel, a bot) gets a private note explaining why, and nothing changes.

4. Get your own alerts as DMs

Each person chooses in Settings → Notifications → Slack DM: a switch per kind (issue and metric alerts, issue workflow such as assignments and comments, deploys and releases, the weekly report), for every project or one at a time. Every kind is off until you turn it on. The page shows which Slack account your email matched; if it says none, use the same email in Slack and in Guidely. Alert DMs have the same buttons as channel alerts.

  • Link previews: paste a link to a Guidely issue, recording, trace or release in Slack and the app adds a short preview (for an issue: its short id, title, status, events and when it was last seen). Previews only appear for projects of the Guidely workspace that added the app, and never show your end users' details.
  • /guidely issue NORTHWIND-42 answers privately with the issue, its numbers and the same buttons. /guidely help lists the commands.

Why are the buttons missing?

  • Your workspace requires two-step verification or single sign-on. Slack can't prove someone signed in to Guidely that way, so in workspaces that require two-step verification (Settings → Sign-in; on by default for new workspaces) or enforce SSO (Settings → SSO & SCIM, or SAML as the only sign-in method), Slack actions are off. Alerts and DMs still post, without buttons, and a button on an older message (or /guidely issue) explains why. To triage from Slack, a workspace admin turns that requirement off; otherwise open the issue in Guidely from View issue.
  • The channel is an incoming webhook, not a channel of the app. Webhook messages only have links. Connect the channel through the app and pick it in the rule instead.
  • It isn't an issue alert or a monitor incident. Metric alerts, deploy notifications, replay alerts and Scout requests post with links only.

HIPAA workspaces

Slack is your own vendor, so check your agreement with Slack before sending it health information. Messages to the channels you pick are the same as in other workspaces. What Guidely sends on its own is limited: link previews are off, DMs only say what kind of thing happened, with a link into Guidely, and /guidely issue answers without the error text. See HIPAA mode.

Disconnecting

A workspace admin clicks Disconnect under Integrations → Slack, which revokes the app's access, or removes the app in Slack. Either way the app's channels stop posting in every project of the workspace until Guidely is added again. Incoming webhooks keep working.

Incoming webhooks

To post to a channel without the app: in Slack, create an Incoming Webhook for the channel (Apps → Incoming Webhooks), copy its https://hooks.slack.com/services/… URL, and paste it under Integrations → Slack. Connect one webhook per channel. Webhook URLs are secrets: Guidely only shows them masked.