Skip to content
threada Docs

Slack setup and support

Threada for Slack lets a configured Slack channel create governed Threada WorkItems with the /threada slash command. The first public Slack app is intentionally narrow: it receives slash-command payloads, routes them to a mapped Threada pack, and links back to the created WorkItem. It does not read Slack channel history, files, private channels, direct messages, or workspace exports.

Requirements

Before installing the Slack app, make sure you have:

  • An active Threada tenant.
  • Studio access with permission to configure the target pack.
  • Permission to install apps in the Slack workspace, or an available Slack admin approval path.
  • The Slack channel ID for each channel that should be allowed to create Threada WorkItems.

Install Slack

Marketplace reviewers and tenant admins should start from the public setup path, then sign in to Studio to complete the tenant-scoped OAuth install.

Add to Slack

  1. Follow the Add to Slack link and sign in to Studio if prompted.
  2. Select the pack that should receive Slack-created WorkItems.
  3. Open the pack’s integrations area and choose Slack if Studio has not already opened the Slack install flow.
  4. Review the requested Slack scope. The v1 app uses the commands scope so users can run /threada; it does not need message-history scopes.
  5. Approve the Slack OAuth prompt.
  6. After Slack redirects back to Studio, confirm that the workspace install is shown and bound to the selected pack.

If Slack says the app requires admin approval, complete the workspace approval flow in Slack, then return to Studio and retry the install.

Map a Slack channel

The slash command only creates WorkItems from channels that are explicitly mapped in Studio.

  1. In Studio, open the same pack’s runtime channel settings.
  2. Add a Slack channel mapping.
  3. Paste the Slack channel ID, for example C0123456789.
  4. Select the Slack workspace installation that is bound to the pack.
  5. Enable intake for the channel.
  6. Confirm the pack and queue or routing policy that should receive new WorkItems.

Repeat these steps for every Slack channel that should be allowed to create WorkItems. Unmapped channels receive a setup-required response and do not create WorkItems.

Optional governed Slack posting

Tenant admins can enable governed chat.postMessage actions for private or reviewer-safe workspaces by installing a Slack bot token through the shared directory credential route:

POST /api/v1/integrations/slack/directory-install

The authenticated request must include:

  • resource_key: the Slack workspace team ID, for example T0123456789.
  • endpoint_url: optional; if supplied, it must be https://slack.com/api.
  • credential.bot_token: the raw Slack bot token, stored in Secret Manager.
  • credential.app_id: the Slack app ID, stored as slack_api_app_id.
  • credential.granted_scopes: the granted bot scopes; must include chat:write.

Optional metadata fields include credential.team_name, credential.enterprise_id, credential.enterprise_name, credential.bot_user_id, and credential.authed_user_id.

This route upserts a runtime-bound Slack integration with the slack_post_message action allowlist. It is separate from the public v1 Slack OAuth install, which intentionally requests only commands and does not persist raw OAuth tokens.

Use the slash command

In a mapped Slack channel, run:

/threada Need vendor security review for ExampleCo before Friday

Threada responds in Slack with an acknowledgement and a link to the created WorkItem in the Work shell. Open that link to review the request, evidence, drafts, approvals, and audit timeline in Threada.

Troubleshooting

If /threada does not create a WorkItem, use the response text to identify the setup step that needs attention:

  • Slack is not connected to Threada for this workspace. Install Slack from Studio for the tenant and pack you are using.
  • Slack is connected to Threada but disabled for this workspace. Reconnect the Slack workspace in Studio or ask a tenant admin to re-enable the installation.
  • This Slack channel is not connected to Threada yet. Add a channel mapping in Studio for the Slack channel ID.
  • This Slack channel is connected but not mapped to a Threada pack yet. Bind the Slack channel to the intended pack in Studio.
  • This Slack channel is not enabled for Threada intake. Enable intake on the Slack channel mapping.
  • Threada could not create a WorkItem because this Slack installation is not authorized. Ask a Threada admin to reconnect Slack in Studio, then try again.
  • Threada could not create a WorkItem right now. Retry after a minute. If the problem continues, contact support with the workspace, channel ID, command time, and the text of the response.

If Slack shows a generic command failure or no response, retry after a minute. If the problem continues, contact support with the Slack workspace, channel ID, command time, and the text of the response. Do not send Slack signing secrets, OAuth client secrets, or private credentials to support.

Disconnect a channel

To stop a single Slack channel from creating WorkItems:

  1. Open Studio and select the mapped pack.
  2. Open the pack’s runtime channel settings.
  3. Disable or remove the Slack channel mapping.
  4. Run /threada test in the Slack channel and confirm Slack returns a setup-required response instead of creating a WorkItem.

Disconnecting a channel stops future intake from that channel. Existing WorkItems, evidence, approvals, and audit events remain available in Threada for recordkeeping.

Uninstall the Slack app

To remove the app from the Slack workspace, uninstall Threada from Slack’s app management settings. Slack sends Threada an uninstall event, and Threada disables the stored installation metadata for that workspace.

After uninstall, /threada should return a setup-required or disabled response and no new WorkItem should be created. If commands still create WorkItems after uninstall, contact support immediately with the workspace and channel ID.

Data handling

For command-only v1, Threada receives the data Slack sends with the slash command, including workspace ID, channel ID, user ID, command name, command text, and request metadata needed to verify and route the request.

Threada uses this data to create and audit a WorkItem in the configured tenant. Threada does not use Slack data to train large language models. Threada does not read Slack channel history, files, private channels, direct messages, or workspace exports for this integration.

The command-only OAuth flow does not persist raw Slack OAuth tokens. If a tenant admin uses the optional directory credential route for governed Slack posting, the bot token is stored in Secret Manager and only the generated secret_ref is stored in runtime integration metadata. Non-secret installation metadata, channel mappings, WorkItems, evidence, approvals, and audit history are retained according to your tenant’s retention and deletion settings. Uninstalling the Slack app disables future intake but does not delete already-created WorkItems or their audit history.

For privacy or deletion requests, contact privacy@threada.ai. For support requests, contact support@threada.ai. To report a security issue, contact security@threada.ai.

Support requests for the Slack app receive a response within 2 business days.