FireHydrant's Slack and Slack Enterprise Grid integration enables you to drive incidents end-to-end without leaving your collaboration tool. This provides convenience and reduces context switching and toil so your responders can focus on the incident.
To connect your Slack workspace:
- Go to FireHydrant's integrations page, search for the Slack tile, and click the plus "+."
- Click "Authorize Application" and follow the on-screen prompts
- Verify that the FireHydrant workspace is selected from the drop-down in the top right corner of the Slack installation page
- Follow the Slack prompts. That's it! Now, you'll be able to run any of Slack's commands.
After you set up the integration, we'll automatically link your Slack account to your FireHydrant account.
If you've already installed the FireHydrant integration into a Slack workspace and would like to move it to enterprise grid, make sure you uninstall the Integration before continuing.
FireHydrant works great with Slack Enterprise Grid; you can connect your FireHydrant organization to multiple Slack workspaces to leverage creating incidents across a broader set of your organization.
If you are a Slack administrator with access to approve Slack apps for the entire organization, this guide is for you!
Follow the on-screen prompts ensuring you select your organization, not an individual workspace from the dropdown in the top right.
This will install FireHydrant as an Org-level integration into the selected Slack organization.
Once FireHydrant has been added to an organization, you must add the integration to the workspaces you'd like to have access to the integration. This enables the members of that workspace to run commands such as
/fh new to declare incidents.
Now for the fun part. When FireHydrant creates channels for incidents, posts into your
#incidents channel, etc., we need to know which Slack workspace we should do that in!
- Visit the integrations page in your FireHydrant account
- Search for the Slack tile and click the pencil icon
- Under workspace, select which workspace we should use
- Click save!
Workspaces may take a few minutes to sync (we've configured it to be about every 5 minutes), so grab a coffee, read Hacker News for a few, and smash refresh on this page.
If you've added FireHydrant to 1 workspace, or 5, or 50, you can now run the same command from any of them and declare a new incident:
And that's it! You're prepared to declare and manage incidents in your Slack Enterprise Grid organization. Now, brush up on our Slack Commands to get the most value from the Slack integration.
For users' activities in Slack to be associated with their accounts in FireHydrant, they will need to be linked. FireHydrant will attempt to auto-link users by matching email addresses between Slack and FireHydrant, and this auto-linking will occur in a couple of different scenarios:
- When a user tries to run any
/fhcommand from Slack.
- When a user joins an incident channel, whether manually or by Runbook step
If auto-linking fails for some reason, users should be able to manually run the
/fh link command. They can confirm whether their Slack accounts are linked to their FireHydrant accounts by checking their user profile settings at Top Left Dropdown > User Profile > [Organization Name]:
FireHydrant's Slack integration allows configuring various parameters to make it more powerful and easier to use.
- Default channel for alerts - FireHydrant posts a notification message whenever an external system posts an alert to FireHydrant via Alert Routing. This default channel will be used to post those notifications*.
- Starred event emojis - When working through incidents, you can "star" or respond to messages from Slack with emojis to mark them as critical items. FireHydrant sets these to
:star:by default, but you can modify this. To learn more, visit Incident Timeline docs.
- Starred confirmation emoji - When you "star" an event using one of the emojis above, the FireHydrant bot responds by also emoji-responding to that message. By default, it is
:fire:but this can also be configured.
- Task emojis - When managing tasks via Slack, you can respond to a Slack message with an emoji to automatically turn it into a Task. By default, the emoji is
- Follow up emojis - Same as with Tasks, you can manage follow-ups from Slack and also similarly create follow-ups with emojis. The default is
When you first install FireHydrant, we will try to find a
#incidentschannel in your workspace, and we will use it if it exists. If it does not exist, we will create it. However, you can change the default channel setting here.
FireHydrant posts all incident updates into the incident Slack channel, from details to tasks and more. This can be a little noisy and overwhelming for some organizations, so you may choose to customize which notifications you want in the Slack channel.
- Navigate to FireHydrant's integrations page and search for the Slack tile. Click the pencil.
- In Slack settings, click the Channel Notification Preferences tab.
- Tweak the notification preferences and settings on this page as desired.
FireHydrant allows custom commands that either return templated responses (helpful in providing quick, on-the-go rules or resources) or make webhook requests (useful for taking actions in external systems).
To learn more, visit the documentation for Command Extensions.
If you have shared workspaces between multiple Slack organizations, you can have Slack Connect users be a part of incident channels. However, there will be limitations because only one organization/FireHydrant account can own incidents and channels (e.g., you can't "share" one incident between multiple orgs).
- FireHydrant will track messages from guest users in shared incident channels. For example, if Org A owns an incident channel and a guest from Org B joins it, that guest user's messages will be tracked in the timeline.
- But FireHydrant cannot automatically invite Slack Connect users to the incident channel. This must be done manually. Users have done this by having the FireHydrant bot Notify Channel into a Shared Slack channel with both workspaces' users so they know there's an incident. Users can then manually join/request to join the incident channel.
- Slack Connect users cannot perform commands on the incident. If Org A owns the incident channel and a guest user joins that channel from Org B, that guest cannot modify the incident, be assigned roles or tasks, etc.
Now that your Slack integration is set up, you can start controlling FireHydrant directly from within Slack. You can also configure Runbooks to notify or create specific Slack channels.
Learn more about using FireHydrant and Slack together in these articles:
Updated about 1 month ago