# Use Nodus from Slack

> Connect your Nodus account, read resource status, and receive channel notifications with the ordinary Nodus Slack app.

Source: https://www.nodus-compute.ai/docs/guides/slack-bot/
Build revision: 4c89a51d7dcfd856f1373531796fbb15831d8da3

**Beta:** this feature may change.

The Nodus Slack app works through ordinary `/nodus` commands. It does not require Slackbot AI or a Business+ upgrade. Commands read resource status; they do not start, stop, or delete compute. Notifications are optional and visible to everyone in the channel where an administrator enables them.

## Connect your account

1. A Nodus organization owner or admin opens [Slack setup](https://console.nodus-compute.ai/slack), selects the organization, and clicks **Add Nodus to Slack**. Slack requests `commands` and `chat:write`.
2. In Slack, run `/nodus connect` and open the private link yourself. Do not forward it.
3. Sign in to Nodus, select the matching organization and a project, then choose **Connect read-only access**.
4. Run `/nodus get jobs`. Only you see the reply.

Each person connects their own account. A workspace belongs to one Nodus organization. The connection creates a user-owned API key restricted to the selected project and the supported read scopes, expiring after 90 days. Your current membership, key permissions, expiry, and revocation still apply to every resource read.

## Commands

|Command|Result|
|-|-|
|`/nodus help`|Available commands|
|`/nodus connect`|A private, ten-minute account-linking URL|
|`/nodus get jobs`|Up to 20 Jobs in your linked project|
|`/nodus get workspaces my-workspace`|One Workspace’s status|
|`/nodus get sandboxes`|Sandbox status|
|`/nodus get pools`|Pool status|
|`/nodus get trainingjobs`|TrainingJob status|
|`/nodus get functions`|Function status|
|`/nodus status`|Recent Jobs|
|`/nodus disconnect`|A private page to revoke your connection|

## Channel notifications

A linked Nodus owner or admin can enable notifications for their selected project:

1. Invite **@Nodus** to the intended channel.
2. Run `/nodus notify on` there. This shares supported resource names and status-change reasons with all channel members, including any external members. It does not send job logs, environment variables, or secrets.
3. Run `/nodus notify test`. The private acknowledgment only confirms queuing; a separate message from **Nodus** confirms delivery.
4. Run `/nodus notify off` to stop notifications in that channel.

Delivery retries transient failures and may produce duplicates after an uncertain response. Notifications older than 24 hours are discarded. A deleted subscription, disconnected account, expired/revoked key, or lost admin membership suppresses queued notifications. Reconnecting removes subscriptions attached to the old connection; enable them again explicitly.

## Disconnect or reconnect

Run `/nodus disconnect`, open the private link, and click **Disconnect and revoke key** while signed in as the linked account. You can also revoke its `slack-…` key from **Settings → API keys**. Revocation propagates through the normal API-key cache, within 30 seconds. Disconnect removes the bot’s saved key and subscriptions immediately.

If a key expires or is revoked, run `/nodus connect` again. If a notification test never appears, confirm that Nodus is a member of the channel and the channel is not archived, then reinstall from Nodus Slack setup if its Slack permissions were revoked.