Slack
Operators get their arming codes as DMs from the Outis app, and /outis proposes requests for actions other integrations own. The integration provides no actions of its own.
Proposing
Section titled “Proposing”/outis deploy.production repo=acme/api ref=main proposes directly. /outis alone opens a modal listing every action the workspace’s organization holds that an integration can carry out, with the params each one takes. The reply is ephemeral, to the person who ran the command.
A code reaches an operator as a DM, so the account has to be linked first. From the dashboard, an operator presses LINK SLACK on their own row and completes Sign in with Slack. Once a request is decided, the operators who turned their keys get a DM with the outcome.
Workspaces and organizations
Section titled “Workspaces and organizations”Each organization adds the Outis Slack app to its own workspace from the dashboard. A command’s workspace names the organization, and the request belongs to it. A command from a workspace nobody has connected is answered in words and proposes nothing. An organization may connect more than one workspace.
Signatures
Section titled “Signatures”Slack signs every request over the timestamp and the raw body. Both routes check the signature and its freshness, five minutes either way, before reading anything, and the signature itself is the replay key.