---
lang: en
---

# Deploy

Connect is where a product is linked to Slack, Discord and Linear, and where its escalations are sent by email and to a chat channel. The Overview lists every connection with its state, and the Messenger, help site and AI clients have their own pages.

> Verified against the product on 2026-11-20

## See what is connected

The **Overview** page lists every connection your product has, in three groups: **Answers in**, **Reads from** and **Escalates to**, each row with its state.
Use **Show** to filter the rows to **All**, **Connected** or **Not yet**.
Above the groups, **This week** counts the questions the connections answered and the escalations sent in the last seven days.

Each row opens the page that sets it up. The Messenger and the help site have their own pages, [Messenger](https://cactus.heycactus.ai/w6vu4g-messenger) and [Help site](https://cactus.heycactus.ai/94dn3s-help-site). AI clients are on [AI clients](https://cactus.heycactus.ai/766ch7-ai-clients). GitHub and the flag tools open Settings › Sources, which [Sources](https://cactus.heycactus.ai/ec27z4-sources) tells.

Slack and Discord rows appear only where Slack and Discord are available. Linear appears under **Escalates to** only where Linear is available.
Where Slack isn’t available, the Slack page says **Slack isn’t available yet.**

## Connect Slack

1. In **Connect › Slack**, select **Connect**.
2. Approve the install in Slack. You return to the page, which says what Connect set up.

Connecting Slack sets up **#cactus-escalations** for escalations and **#cactus-releases** for releases, and adds you to both.
In Slack, tag @Cactus in a channel it is in, or send it a direct message, and it answers there.
How the bot answers in Slack is on [Slack and Discord](https://cactus.heycactus.ai/4jkxwd-slack-and-discord).

**Hold to disconnect** removes Slack for your whole team, and every product’s channels go with it.

Under **Releases**, **Stop posting releases** takes the release channel away, and releases are then not posted. There is no separate switch.

## Connect Discord

1. In **Connect › Discord**, select **Connect**.
2. Approve the install in Discord.

Connecting Discord sets up **#cactus-escalations** for escalations.
Cactus uses a channel already named `cactus-escalations` if the server has one, and makes it only if not.
Discord posts no release announcements.
In your server, mention @Cactus and it answers in a thread on your message.

**Disconnect** forgets the server for this product only, and deletes the connection once no other product uses it.

## Connect Linear

1. In **Connect › Linear**, select **Connect**. It returns you to Connect.
2. Someone who is an admin of your Linear workspace has to connect it.

Feature requests and bugs people report are sent to your Linear, as new issues or onto ones you already have.
A workspace with one team has that team picked already. Otherwise the first team is used until you pick one.
To change it, open the **Linear** menu on the row and check a team under **New issues go to**.

**Hold to disconnect** in the same menu stops sending to the workspace. Issues already sent stay linked.
Cactus’s app is removed from the whole Linear workspace only when no product still uses it.

## Where escalations go

**Escalations** lists every place an escalation goes, email first. The mail goes out on every escalation, and a channel is posted to as well.
Every escalation is emailed to your whole team, and the addresses you add get them too.
Added addresses never decide whether an escalation exists.

To add an address, type it in **Escalation address** and select **Add**. To remove one, select it.
Where sending email isn’t available, the Email panel says **Sending email isn’t available yet.**

Once a platform is connected, its channel is chosen under **Where escalations go**. Pick a channel from the list and select **Use this channel**, or select **Create #cactus-escalations**.
To change it, select **Change**.

Once a platform is connected, the page says how a handoff works. Each escalation gets one card, with a thread under it. Only **Reply…** on the card, or asking Cactus to reply, reaches the customer, and Cactus sends it in the Messenger and by email. Everything else your team says in the thread stays private.

## If a connection fails

| What you see | What it means | What to do |
| --- | --- | --- |
| “Couldn’t load this workspace’s Slack channels. Try again in a moment.” | Cactus could not list Slack’s channels. | Try again in a moment. |
| “Couldn’t load this server’s Discord channels. Try again in a moment.” | Cactus could not list the server’s channels. | Try again in a moment. |
| “Slack isn’t connected. Connect it again.” | Slack is no longer connected for your team, so a channel cannot be made or set. | Select **Connect** on **Connect › Slack**. |
| “Discord isn’t connected. Connect it again.” | The Discord server is no longer connected for this product. | Select **Connect** on **Connect › Discord**. |
| “Cactus isn’t allowed to make channels in this server. Pick one instead.” | Discord refused Cactus permission to make #cactus-escalations. | Pick an existing channel under **Where escalations go**. |
| “Slack wouldn’t accept that channel. Pick another one.” or “Discord wouldn’t accept that channel. Pick another one.” | The platform refused the channel you picked. | Pick another channel. |
| “#name was deleted in Slack, or Cactus was removed from it.” | Slack no longer lets Cactus use that channel. | Select **Set up a channel**. |
| “Couldn’t read where escalations go. Try again.” | The escalations page could not read its connections. | Try again. |
| “Linear isn’t available yet.” | Linear is not available. | Nothing on your side. |

If a Discord server already belongs to another Cactus team, it is not moved to your product.
If Linear refuses Cactus’s access, the workspace connection is removed, and you need to connect Linear again.
