integrations

Connect Slack with a customer-provided app

Connect Slack using a customer-created app's bot or user token.

A personal connect creates an installation every time, as the OAuth connect does; a bot connect refreshes the workspace's bot installation when the organization has one. To replace an existing installation's tokens, use POST /v1/integrations/slack/installations/{installation_id}/reconnect instead.

post/v1/integrations/slack/connect

Request body

access_mode'bot' | 'user'

Use a personal user installation (default). bot installs a workspace bot and is only available from the dashboard; requests authenticated with an API key must use user.

bot_tokenstring required

Slack bot user OAuth token (xoxb-…)

user_tokenstring nullable

Slack user OAuth token (xoxp-…)

signing_secretstring required

Slack app signing secret

store_namestring nullable

Ingestion store name. A store that already exists is shared: every data source connected to it ingests into it, except another installation of the same account, which would ingest every item again. Without it, the account's default store, numbered past a store another installation of the account feeds. Rejected with 422 when the connect refreshes an existing installation and names a store other than its own.

new_storeboolean

Ingest into a store created for this connection: the connect fails with 409 when store_name names a store that already exists, and without store_name the default name is numbered past existing stores. Rejected with 422 when the connect refreshes an existing installation, which keeps its store.

Response

The connected Slack installation

Changes

Changed in 6 of the 30 revisions of this API.58

Sep 26, 20269c6c72afde2d1See the full diff
- ○
  added the new optional request property
  new-optional-request-property
Sep 21, 2026b12f43c90ba32See the full diff
- ●
  added the new bucket_unavailable_error enum value to the / response property for the response status
  response-property-enum-value-added
- ●
  added the new bucket_unavailable_error enum value to the / response property for the response status
  response-property-enum-value-added
Sep 15, 2026957bf8ec8df82See the full diff
- ●
  added the new store_frozen_error enum value to the / response property for the response status
  response-property-enum-value-added
- ●
  added the new store_frozen_error enum value to the / response property for the response status
  response-property-enum-value-added
Sep 10, 2026adde8ecfa74f14See the full diff
- ●
  removed the optional property from the response with the status
  response-optional-property-removed
- ○
  added the non-success response with the status
  response-non-success-status-added
- ○
  added the required property to the response with the status
  response-required-property-added
- ○
  added the required property to the response with the status
  response-required-property-added
- ○
  added the required property to the response with the status
  response-required-property-added
This revision also has 3 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
Sep 7, 20261a6549d3e64d1See the full diff
- ○
  the request property default value changed from bot to user
  request-property-default-value-changed
Sep 5, 2026ea8d85b8caca2See the full diff
- ○
  added the new optional request property
  new-optional-request-property
- ○
  added the new optional request property
  new-optional-request-property
This revision also has 31 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog

Full history