Slack

Most TeamAPI surfaces wait for someone to look up an answer. In Slack, people ask "does anyone know who owns checkout-api?" in a channel of 200 people.

The integration answers ownership questions in Slack and puts the owner in each channel topic.

1. `/whoowns` in Slack#

The REST API serves a slash-command endpoint at POST /slack/whoowns, backed by the same findServiceOwner lookup the API and the MCP server use.

export SLACK_SIGNING_SECRET=...      # from your Slack app's Basic Information page
teamapi serve-api /path/to/your/org

Point a slash command at https://<your-host>/slack/whoowns, and:

/whoowns checkout-api

  `checkout-api` is owned by *Stream Checkout* (`stream-checkout`).
  _Shopping cart, checkout flow, and order placement_
  Ask in #stream-checkout.

Unknown service names get the list of what is declared, which is usually enough to spot the name someone half-remembered.

The route only exists when SLACK_SIGNING_SECRET is set. It is not registered when the secret is missing, preventing a misconfigured deployment from exposing an unauthenticated endpoint. Requests are checked against Slack's v0:<timestamp>:<body> HMAC in constant time, and anything more than five minutes old is rejected so a captured request cannot be replayed.

2. Channel topics that say who owns the channel#

export SLACK_BOT_TOKEN=xoxb-...
teamapi slack-sync /path/to/your/org            # prints the plan
teamapi slack-sync /path/to/your/org --yes      # applies it

Same plan/apply split as teamapi apply — it writes to a system outside the repo, so it shows you first:

~ #stream-checkout (stream-checkout)
    - (no topic)
    + Stream Checkout — Shopping cart, checkout flow, and order placement · Owns: checkout-api
  #enabling-devex: up to date
  #platform-payments: declared by platform-payments, no such channel in Slack
! #shared-ops is claimed by platform-payments and stream-checkout — left alone
  3 channel(s) no team declares, left alone

1 topic(s) to update.

Requires channels:read and channels:manage (plus the groups: equivalents for private channels).

Limits#

Only topics are changed. The command does not create, invite people to, or archive channels. A spec file should not quietly reorganise a social space with its own history.
Channels nobody declares are left alone, and counted in the output. Not every channel belongs to a team, and treating undeclared as unowned would be wrong.
A channel claimed by two teams gets no topic. Same call as CODEOWNERS, for the same reason: the answer is a decision someone has to make, not a default the tool should pick.
Nothing writes back to teamapi.yml. If Slack is where a channel is really created, add it to the team document in a pull request.

Suggested loop#

Declare each team's channel in channels[] with type: slack.
Run teamapi slack-sync on merge so topics track the spec.
Serve the REST API with SLACK_SIGNING_SECRET set and register the /whoowns command.
When someone asks in a channel anyway, the answer is one slash command away.

Slack

1. /whoowns in Slack#

2. Channel topics that say who owns the channel#

Limits#

Suggested loop#

1. `/whoowns` in Slack#