> For the complete documentation index, see [llms.txt](https://docs.spike.sh/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.spike.sh/alerts/slack.md).

# Slack

<figure><img src="/files/LV6xomtTZEouKuhXAzlE" alt="Spike app for Slack"><figcaption><p>Spike app for Slack.</p></figcaption></figure>

The Spike app for Slack keeps your team informed and responsive during incidents.

Key features:

* Incident alerts with acknowledge, resolve, and escalate actions
* On-call shift notifications
* Private channel support
* Create incidents directly from Slack
* View current on-call responders

{% tabs %}
{% tab title="Quick links" %}

* [Install Spike app on Slack](https://app.spike.sh/settings/general/alerts)
* [App on Slack marketplace](https://slack.com/apps/AKRF4KSG5-spike)
* [Set incident alerts with escalations](https://app.spike.sh/escalations)
* [Set on-call alerts](https://app.spike.sh/settings/general/alerts)
  {% endtab %}
  {% endtabs %}

## How to set up

Go to **Integrations** and click **Add to Slack**.

{% tabs %}
{% tab title="Setting up incident alerts" %}

<figure><img src="/files/h13Sb89VeeJDwKC6TtR8" alt="Adding Slack to an escalation policy"><figcaption><p>Adding Slack to an escalation policy.</p></figcaption></figure>

Go to **Integrations** and click **Add to Slack**. The Spike app requests some basic permissions.

Add Slack as a step in your [escalation policy](https://app.spike.sh/escalations) to receive incident alerts. You can choose between public or private channels.
{% endtab %}

{% tab title="Setting On-call shift notifications" %}

<figure><img src="/files/2Z7ZqXXjDj5DIX4rstRY" alt="On-call shift notifications on Slack"><figcaption><p>On-call shift notifications on Slack.</p></figcaption></figure>

Go to **Integrations** to select Slack channels to receive on-call shift alerts.
{% endtab %}

{% tab title="Connect for DMs" %}

* Other team members can link their Slack accounts to receive direct messages for important updates.
* Run the `/connect` command to connect.
  {% endtab %}
  {% endtabs %}

Use the `/help` command in Slack for further help. The Spike app cannot read any of your messages.

## Slash commands

<figure><img src="/files/E2ld2EN6SpxYBzUkd9Cf" alt="Slash commands for the Spike app on Slack"><figcaption><p>Slash commands available in the Spike app.</p></figcaption></figure>

1. `/create-incident`: Create a new incident directly from Slack. Anyone in your workspace can use this.
2. `/oncall now` or `/oncall me`: Check who is currently on-call or view your on-call schedule.
3. `/connect`: Connect your Slack account with Spike.
4. `/help`: Display a help message with guidance on using the Spike app.

### Create incidents from Slack

Using `/create-incident` opens a form to create incidents directly from Slack.

{% stepper %}
{% step %}

### Add a title and details

Provide a clear title and relevant details, including JSON data or links if applicable.
{% endstep %}

{% step %}

### Select integration and escalation policy

Choose the integration and escalation policy to route the incident correctly.
{% endstep %}

{% step %}

### Submit

Click to create the incident.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
Anyone in your Slack workspace can create incidents, even if they are not part of your Spike account.
{% endhint %}

## Incident alerts

<figure><img src="/files/rmYHi4ukheztcc7DTTXl" alt="Incident alert on Slack"><figcaption><p>Incident alert on Slack.</p></figcaption></figure>

Spike's incident alerts mention `@here` to notify everyone online in the channel. Each alert includes the title, responders, links, and integration.

### Available actions

* **Acknowledge**
* **Resolve**
* **Escalate**
* **Discuss in a new channel**

### Discuss in a new channel

<figure><img src="/files/XJs5NpUSFUSy5H3guMLZ" alt="Discuss incident in a new Slack channel"><figcaption><p>Discuss an incident in a dedicated Slack channel.</p></figcaption></figure>

Each incident includes the option to discuss in a new channel. When triggered, a dedicated channel is created for the incident. Only the user who initiates the action is added initially. Spike cannot read messages in these channels.

### Auto-updating Slack messages

When an incident is resolved via phone, SMS, email, or the dashboard, the Slack message updates automatically to reflect the resolved status.

<figure><img src="/files/-MXuKb452pRTx5d_QjEf" alt="Slack message showing incident already resolved"><figcaption><p>The Spike app notifies you if the incident was already resolved elsewhere.</p></figcaption></figure>

If you try to resolve an incident on Slack that has already been resolved elsewhere, the app notifies you.

## Private channels

Private channel access can be configured in **Integrations**.

### Adding private channels to escalations

Only users who have connected their Slack account with Spike can view private channels in escalations. They can only see channels where:

1. They are a member.
2. The `@Spike.sh` app has been added.

{% hint style="warning" %}
Add the `@Spike.sh` app to your private channels to continue receiving alerts. This is mandatory for escalations configured before 11th December 2024.
{% endhint %}

### Private channel visibility

Once a private channel is added to an escalation, its name is visible only to users who:

1. Have connected their Slack account with Spike.
2. Are members of the same private channel.

## On-call alerts

<figure><img src="/files/2Z7ZqXXjDj5DIX4rstRY" alt="On-call shift alerts on Slack"><figcaption><p>On-call shift alerts on Slack.</p></figcaption></figure>

Go to **Integrations** to select Slack channels to receive on-call shift alerts. You can enable notifications for both shift start and shift end.

## FAQs

### Can anyone create an incident from Slack? Is there an extra charge?

No. Anyone in your workspace can create an incident and there is no additional cost.

### I can't find a channel in the dropdown. What should I do?

Paste the channel ID from Slack. To find it, open the channel, go to the **About** section, and copy the unique ID.

<figure><img src="/files/BAw8mX0AGg7mTGdiYDeX" alt="Finding a Slack channel ID"><figcaption><p>Find the channel ID in the About section.</p></figcaption></figure>

### Why can't I see a private channel in the escalation dropdown?

You must be a member of the private channel, have connected your Slack account with Spike, and the `@Spike.sh` app must be added to that channel. Run `/connect` on Slack to connect your account.

### How do I add the @Spike.sh app to a private channel?

Type `/invite @Spike.sh` in the channel.

### Can all team members view private channels added to escalations?

No. Only users who are members of the private channel and have connected their Slack account with Spike can see it in escalations.

### Can the same discussion channel be reused for multiple incidents?

No. A new channel is created for each incident to keep discussions separate.

### What happens to a discussion channel after the incident is resolved?

The channel stays in your workspace until manually archived. Archive it after the incident is resolved to keep your workspace tidy.

### Can non-Spike users join a discussion channel?

Yes. Anyone in your workspace can be invited to join, regardless of their Spike account status.

### What happens if I disconnect my Slack account after adding private channels to escalations?

You will no longer see the private channel names in escalations, even if you are still a member of those channels.

### User A and B are in a private channel in the escalation policy, but B can't see the channel name. Why?

User B hasn't connected their Slack account with Spike. They can run `/connect` in Slack or send a direct message to the Spike bot to connect.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.spike.sh/alerts/slack.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.