Skip to main content
Rubix is the RubixKube agent. In Slack it answers in the thread with what it sees in your environments: open incidents, their root causes, and the fix. It reads first and asks before it changes anything.

​
Install

1

Open the Integrations page

In the RubixKube console, go to Integrations and select Slack, then Connect.
2

Allow Rubix in your workspace

Slack shows what Rubix asks for. A Slack admin may need to approve the install.
3

Invite Rubix where you want it

In each channel where you want to mention it, run /invite @Rubix. Rubix only sees channels it was invited to. Direct messages need no invite.
The agent experience (the Messages tab, sessions and the Stop button) needs a paid Slack plan. Mentions in channels and incident cards work on every Slack plan.

​
Talk to Rubix

​
In a channel

Mention Rubix with a question. It answers in the thread, and the thread is one conversation: later mentions continue it, and Rubix reads what the thread said in between.

​
In the Messages tab

Open Rubix from the apps list and ask there. Suggested prompts sit at the top, Rubix shows a working state with a Stop button while it thinks, and the channel you are looking at is passed along as context, so “what is going on in this channel?” works.

​
Approvals

When Rubix proposes a change (closing an incident, moving a Task, running a command), the thread gets a card with the exact command and three buttons: Approve, Approve for this chat and Deny. Nothing runs until someone approves. The card then shows who decided, and the decision is recorded in your organization’s activity log with that person’s name.

​
Questions

When Rubix needs a choice, the thread gets the options as buttons, with Let Rubix decide as a way out. In a direct message, a plain reply answers; in a channel, mention Rubix with the answer.

​
Incident cards

Paste a RubixKube incident link in Slack and it unfurls as a card with the incident’s status, severity and service, an Ask Rubix button that starts a conversation about it in that thread, and a side pane with the details.

​
In a thread

/rubixkube help, /rubixkube stop and /rubixkube settings work from anywhere.

​
Modes

A new conversation takes your organization’s default mode, set by an admin in the console under Settings: Observe (reads and explains, asks before any change), Assist (asks before each change) or Act (changes without asking, up to the organization’s ceiling). The first reply in a thread says which mode the conversation is in.

​
Permissions and data

Rubix asks only for what it uses: to hear mentions and direct messages, to post and stream replies, to read the thread it was mentioned in at that moment (at most fifteen messages), to show incident cards for RubixKube links, to add a reaction that acknowledges a mention, and to show the name of the person who asked. It does not join channels on its own and does not read channels it was not invited to. Rubix stores no Slack messages. What you say to it, and the thread messages sent along as context, become part of that conversation in RubixKube, kept as long as your organization keeps the conversation. Rubix writes one thing into Slack: a conversation identifier in the metadata of its own replies. No Slack data is used to train models. See the privacy policy. Rubix uses a large language model. Its answers can be wrong: check before you act, and use the Approve step as the check for any change.

​
Troubleshooting

Check that the workspace is connected in the console under Integrations, Slack, and that Rubix was invited to the channel with /invite @Rubix.
An admin connects it in the console under Integrations, Slack.
Say stop in the thread, or press Stop.
Disconnect Slack in the console under Integrations, or remove the app in Slack. Either stops it at once.

PagerDuty

Pair with Slack: chat for day-to-day, PagerDuty for on-call paging.

Microsoft Teams

The same model for Teams-first organisations.