Slack app
Signals & Orchestration for Slack
Let a TotalCtrl agent watch the channels you choose, and let your automations post messages, open channels and message people as workflow steps.
Add to SlackYou will be asked to sign in to TotalCtrl first. An integration is installed into a workspace, so we have to know which one.
What it does
Signal Sources — an agent that watches
Point an agent at the channels you care about and it reads what happens
there as signals: a customer complaint in a shared channel, an alert in
an ops channel. It can then act on them through the Agent Inbox.
Orchestration — Slack as a workflow step
Post a message to a channel, create a channel for an incident or a deal,
or send somebody a direct message — as steps in a workflow, alongside
every other app TotalCtrl connects to.
One app, two features
Installing once covers both. You choose which to use inside TotalCtrl;
nothing runs until you configure a signal source or add a Slack step to a
workflow.
Permissions it asks for
| Permission | Why it is needed |
|---|---|
chat:write |
Post the messages your workflows send. |
channels:manage |
The Create Channel workflow step, for a public channel. |
groups:write |
The same step when the channel is private. |
im:write |
Open a direct message for the Send Direct Message step. |
users:read.email |
Find the person to DM from the email address in your workflow. |
users:read |
Slack requires this to be requested alongside the lookup above. Nothing here reads your member directory. |
Three of these exist only for the Send Direct Message step
—
It does message people, and it does not listen. The app's Messages tab is read-only: a DM from a workflow arrives, and there is nobody on this end to reply to. Nothing is subscribed to your messages.
im:write, users:read.email and
users:read, which Slack will not grant the email lookup
without. If you never use that step, none of them are called.
They are declared because Slack refuses a call whose scope was not requested
at install, not because the app reads your directory in the background.
It does message people, and it does not listen. The app's Messages tab is read-only: a DM from a workflow arrives, and there is nobody on this end to reply to. Nothing is subscribed to your messages.
What it can see
Only the channels you point a signal source at, and only while that source
is active. Orchestration reads nothing at all — its Slack steps are writes.
Delivery is per-source: each signal source and each workflow trigger has its
own URL created inside TotalCtrl, so nothing is subscribed workspace-wide.
Removing it
Remove the app from Slack (Settings & administration
→ Manage apps) or disconnect it inside TotalCtrl. Either one stops it
immediately; disconnecting in TotalCtrl also deletes the stored token.
Any workflow with a Slack step will start reporting that step as failed rather
than silently skipping it, so you can see what needs changing.