GitHub
Merge a pull request, approve a colleague’s, or answer a deployment protection rule when the keys turn. Requests come from the App’s webhooks or from a workflow over HTTP. Read more
Integrations
An integration plugs into Outis at one or more of four seams: it can provide actions and propose requests for them, carry arming codes to operators, act on a decision, and prove who an operator is. Outis ships three, and the contract for writing your own is public.
Slack
Arming codes arrive as DMs, and a slash command proposes requests for actions other integrations own. Read more
HCP Terraform
A run task holds the apply until the keys turn, with the plan’s destroy count on the panel. Read more
Build your own
Implement the SDK’s contract in Go and run the conformance suite. Read more
The four seams
Section titled “The four seams”| Seam | What it means |
|---|---|
| Actions | The integration declares action ids and the default policy each one seeds into a new organization. An admin owns every field after that. |
| Proposes | It creates requests from a webhook, a chat command, or an HTTP route behind an API key. |
| Notifies | It carries arming codes and outcomes to operators over a channel they’ve linked. |
| Responds | Once a request is decided, it makes one idempotent call to the system that asked: merge at the sha the panel showed, submit the review, answer the rule. |
Outis holds no credential for anything downstream. An integration that responds uses the other system’s own token.