Omniscio

Slack integration (triage Slack from Omniscio)

Omniscio's Slack integration pulls selected channels and DMs into the unified inbox so you can read, triage, and reply to Slack messages without switching apps. It connects to your workspace through Slack's Socket Mode (a WebSocket connection — no public webhook URL needed), so messages arrive in real time.

On this page

What it is

Omniscio's Slack integration pulls selected channels and DMs into the unified inbox so you can read, triage, and reply to Slack messages without switching apps. It connects to your workspace through Slack's Socket Mode (a WebSocket connection — no public webhook URL needed), so messages arrive in real time. Each conversation appears as a row in the Omniscio sidebar/inbox alongside your Gmail, SMS, and Telegram threads, and you reply with the same Quick Responses + AI-suggested reply chips you use everywhere else. Sending goes back through the Slack Web API as your bot user.

Where to find it

Settings → Channels → Slack: press Connect Slack (when its Labs switch is on) or paste the tokens yourself, then pick which channels and DMs to follow in the same panel.

How it behaves

How to use it

Connect Slack (one click, desktop app only). This is the easiest way, and it ships behind its own switch in Settings → Lab (one-click Slack setup, off by default). It stays hidden until Team Chat is unhidden; with the switch off, the Slack settings screen looks the way it always did. The phone and web views do not offer it.

  1. Press Connect Slack. In Settings → Channels → Slack, Step 1 shows a Connect Slack button with a live progress line under it. Omniscio opens its own sign-in window on Slack, already filled in with Omniscio's app settings (all the permissions it needs, the bot, events and Socket Mode).
  2. Sign in and create the app. Sign in to Slack (an email code and a robot check), choose your workspace in the pre-filled Create from a manifest box, then press Next and Create. If Slack lands you somewhere else once you are signed in (its Choose a workspace list, your workspace, or a blank app list), Omniscio takes the window back to the pre-filled box by itself. You copy and paste nothing: Omniscio reads the new app's Client ID and Client Secret from the app's page and makes the app-level connection token (the connections:write one) itself, checking each with Slack.
  3. Press Allow once. One Slack approval screen asks for both the workspace (bot) permissions and your personal permissions, including mpim:read, mpim:history, pins:read and users:read.email, which let the import reach group DMs, pinned messages and the member emails it matches people by. After you press Allow, Omniscio checks the bot token and your personal token with Slack and saves all three, encrypted. The window closes, its sign-in is wiped, and Settings moves on to Step 2, Select channels.

Nothing is saved unless Slack confirmed every value, and a failed attempt leaves an earlier Slack connection exactly as it was. If anything goes wrong, Connect ends cleanly with a plain reason (you cancelled or closed the window, it timed out after 20 minutes, Slack's page changed, you declined the approval screen, your workspace admin must approve app installs, a Slack check failed, or Slack's page could not load) and points you to the manual path. The sign-in window never touches your own browser or its logins, refuses every permission request (so it cannot launch the Slack desktop app), and has its own taskbar button. Connect always saves your personal token. To also switch on Personal Slack Account (sending as yourself), tick Also let it send as me above the Connect button before you press it; the box starts unticked and is locked while Connect runs. Left unticked, Personal Slack Account stays exactly as it was, and you can switch it on later in the same panel.

Disconnect forgets the connection. Once connected, Disconnect (after a confirm) stops monitoring and removes the saved Slack connection from this computer: the app, bot and personal tokens, the workspace name and the channel list. Nothing is left to reconnect, during this run or the next launch, and the panel returns to Connect Slack. It works only on the desktop app, like clearing tokens.

Set it up yourself (always available). In the same Step 1, the Set it up yourself toggle reveals the manual steps. With the Labs switch off, these are the only steps shown.

  1. Create a Slack app. Go to api.slack.com/apps → Create New App → From scratch. Add the OAuth scopes you want the bot to read/write (channels:history, channels:read, chat:write, users:read, plus im:* for DMs), enable Socket Mode, and generate an App-Level Token with connections:write. Connecting your personal account is a second, separate step by hand, and the wizard lists the User Token Scopes it needs, the same ones named in the Connect Slack steps above.
  2. Connect Omniscio. Settings → Channels → Slack → paste the Bot Token (xoxb-…) and the App Token (xapp-…). Toggle slackEnabled on. Omniscio opens the Socket Mode WebSocket and starts receiving message events. If Slack refuses the channel list (for example the bot is missing channels:read or groups:read under Bot Token Scopes), the panel names the missing permissions instead of a generic "Could not load channels".
  3. Connect your personal account (for sending as yourself, and for the Team Chat import). Turn on Personal Slack Account in the same panel, then click Connect Personal Account and paste your app's Client ID and Client Secret (Slack app → Basic Information → App Credentials). Authorize with Slack opens your browser for the Slack approval. This card appears as soon as the toggle is on, with no bot setup required: the import only needs your personal account.

Either way, the steps after setup are the same:

  1. Pick which channels show up. In the same settings panel, choose the channels and DMs you want to follow. Only selected conversations sync — the goal is to keep your Omniscio inbox curated, not mirror your entire workspace.
  2. Get an inbox alert for what is meant for you. A new direct message to you, or a channel message that @mentions you, raises one New Slack message from <name> card in the inbox, filed under the Slack hub, with a short preview. That preview, like the one under each conversation in the sidebar, reads as plain text: people are named (@Mitch, never <@U0C9...>), channels read #general, links show their label and & shows as &. A person Omniscio has not seen yet shows as @ plus their Slack id until their name is known. More messages in the same conversation update that one card instead of stacking new ones, and opening the conversation (marking it read) clears it. Ordinary channel chatter that does not mention you only raises the conversation's unread count. Your own messages, sent from Slack on another device, never alert you. The card can be switched off like any other alert type.
  3. Triage the conversation. Open the Slack hub to see the conversation panel — full thread history, thread replies, reactions on hover. Reply inline; sends post back through Slack as the bot (or as you, if a user token is configured).
  4. Pair with automations. Slack messages that arrive over the live connection flow through the same Automation/Auto-replies engine, so you can auto-reply to keywords, forward urgent threads via email, or route specific channels to the daily digest.
  5. Triage from the inbox. New Slack messages appear as inbox rows. Click one to open the conversation panel — full thread history, thread replies, reactions on hover. Reply inline; sends post back through Slack as the bot (or as you, if a user token is configured). A direct message between you and another person can only be reached with your own account, so a reply there goes out as you even when the composer is set to the bot.
  6. Pair with automations. Slack messages flow through the same Automation/Auto-replies engine, so you can auto-reply to keywords, forward urgent threads via email, or route specific channels to the daily digest.

How it works

Slack lives in slack-service.ts — direct fetch calls to https://slack.com/api/* for channel listing, message send, and user resolution, plus a long-running WebSocket connection from apps.connections.open (Slack's Socket Mode endpoint, called with the app-level token) for incoming events. The WebSocket reconnects with exponential backoff + jitter (2s base, 60s cap) and pings every 30s; user lookups are cached for 15 minutes to stay under Slack's rate limits. Response shapes are validated by slack-response-schemas.ts so a malformed Slack reply can't poison the cache. Tokens are encrypted at rest via safeStorage and read through accessors-integrations.ts (getSlackBotToken, getSlackAppToken, getSlackUserToken). The unified-inbox bridge is slack-adapter.ts, which translates Slack-specific shapes into the shared UnifiedConversation / UnifiedMessage types in channel-types.ts. Persistence lives in queries-slack.ts. Every path that stores Slack messages (the live feed, the 5-minute check in slack-catch-up.ts, the hub's sync and a backfill) decides "is this new, and is it for me?" through one rule in slack-arrival.ts, and the history pulls share one saving step in slack-history-store.ts.

Scope and limits

  • Reachable from the localhost CLI — setup is the exception. The control server (127.0.0.1:19519) does reach Slack: GET /slack/status (connection health — connected / disconnected / re-auth-needed), POST /slack/sync (pull the selected channels' history into the local DB), POST /slack/conversations/:channelId/backfill (one conversation's older messages, ?limit= default 50 / max 200), POST /slack/dm (open or create a DM with a workspace member) and DELETE /slack/conversations/:channelId (erase one conversation's stored archive). Sending is POST /slack/send — approval-gated: a 202 means the message is QUEUED for the user to approve in the inbox and transmits only on that approval, the same posture as /sms/send and /telegram/send. Still in-app only: connecting/disconnecting, entering or clearing tokens, and choosing which channels to follow — the classified messaging-client (and feature-scoped-surface, for the import wizard) desktop-only exemptions in the CLI-parity manifest.
  • Reading is two-layered; mark-read is not exposed. Synced Slack messages are searchable via Global Search (Ctrl+K lists Slack alongside every channel), so an agent can find Slack content, and GET /slack/status reports the connection state before an action. Marking a conversation read is the one triage action with no route — the control server exposes no Slack mark-read route, so unread state is cleared in the conversation panel.
  • Each person gets their own Slack app. Connect Slack creates the app in your own workspace, because Slack's Socket Mode allows at most 10 live connections per app, so one shared Omniscio app would fail around the tenth user. Omniscio runs no server for this. If your workspace restricts app installs, an admin has to approve the app before the approval screen can finish; Connect then stops with a plain message and the manual path stays open. The Team Chat Slack import reuses the personal token Connect Slack saved, so right after a successful Connect the import asks for nothing more.
  • The live connection does not carry everything, so Omniscio also checks. Socket Mode delivers nothing while Omniscio is closed, and an app built from Omniscio's settings subscribes to bot events, which do not include a direct message between you and another person. So whenever Slack connects, and every 5 minutes after that, Omniscio reads the newest messages of each conversation you follow and treats anything new from someone else as a fresh arrival. A message can therefore take up to about 5 minutes to raise its card, and one that arrived while Omniscio was closed raises it shortly after Omniscio reopens. The first time a conversation is read, its existing history is saved quietly and raises nothing. A message picked up this way does not run automations; only live deliveries do.
  • Signing out keeps your Slack connection. When you sign out of Omniscio, or your sign-in expires and Omniscio signs you out, your Slack tokens, workspace and chosen channels are set aside for you and Slack stops. Nothing uses them while nobody is signed in. Sign back in as yourself and Slack reconnects on its own, with no setup and no restart. If someone else signs in on that computer, your Slack is removed and they start with none. Switching straight from one Omniscio account to another also removes it.
  • A send while Slack is not connected says so. If Slack has no saved connection, a failed send says Slack isn't connected and offers Open Settings, instead of asking you to try again.
  • A permission Slack refuses is explained, never printed. When Slack declines a read because the connected account was never granted the permission it needs, the surface says so in plain words and points at reconnecting the account in Settings — the provider's error code stays in the app log instead of on screen.

Last verified 2026-10-18