Skip to content

Bot for Slack

Updated View as Markdown

Read channel context and post a reviewed plain-text handoff with your existing Slack bot. Select the posting command and grant chat:write explicitly.

Example workflows

Copy a prompt into your connected AI client after connecting this integration. Choose resources you can access and review the supported command before running it.

Post a reviewed handoff

Prepare a short customer-renewal handoff for the Slack channel ID I provide. Include the account, owner, next step and source link that I supply. Show the exact plain text and destination for approval before posting once. Use an existing thread timestamp only if I provide it. Do not impersonate anyone, expand links, mention broad groups or retry an uncertain post.

Explore this command: slack-bot.messages.post

What you can do (4)

What you can do

Available commands: 4 (3 read, 1 write). Enable only the commands your application needs.

Command Effect
Verify this bot’s workspace identity — slack-bot.auth.test Read
List one page of bot-visible conversations — slack-bot.channels.list Read
Read one page of a channel’s messages — slack-bot.messages.list Read
Post a handoff to a selected Slack channel — slack-bot.messages.post Write

Connect and use

Connect and use

This connection uses your provider account.

Connect this integration, enter your provider credentials, choose commands and save. Complete provider authorization if prompted.

Get your provider credentials

Follow these steps for Bot for Slack, then enter the issued values in the connection form below.

  1. Create or reuse a Slack app, assign only the bot scopes needed (channels:read, groups:read and relevant history scopes), and install/reinstall it in your workspace. Save the Bot User OAuth Token (xoxb-...), not the signing secret, app-level token or user token. Invite the bot to private channels it must read. This connection is separate from user-oriented Slack access. History access has provider-specific rate limits; one page is requested and cursors are explicit. Posting requires chat:write and channel membership. Select the write command explicitly; plain text and optional thread replies are supported.

Official credential setup

Where to enter credentials

In the integration page, sign in, choose your workspace and open Connect. If a Credentials choice is shown, select Use my credentials. Fill the following connection fields and save. Provider credentials belong in this form, never in an MCP configuration or tool input.

Connection field Requirement
Bot for Slack API token Required

Open API keys and create a Tooluse.net key for the enabled commands.

Set TOOLUSE_API_KEY in your client and use the shared MCP configuration.

Configure Claude Code, Codex or Cursor once

Permissions and results

If you have more than one workspace, check the selected workspace in the connection or API-key dialog before saving. Roles, enabled commands, expiry and revocation use Tooluse.net's existing permissions. Disabling a connection or revoking a key immediately prevents new calls.

Send one Claude tool_use block per request. Keep the same Idempotency-Key when retrying the same request; use a new key for a new call. The response includes the shared Tooluse.net receipt and Claude tool_result. Check both HTTP status and the returned tool result before treating a call as successful.

Your connection's daily allowance and key permissions also apply. Adding a connection does not make a provider request.

Calls return the shared execution receipt and a Claude tool_result. Provider output varies by operation; consult the provider documentation for its response fields. Unconfirmed calls should be checked before retrying.

Call from your client

Use the shared MCP configuration. Refresh your client's tool list after saving the connection or changing key permissions, then call the returned tool name with the example input below.

Configure Claude Code, Codex or Cursor once

Discover your enabled tools

List permitted tools in Claude format. Read every page using page and size (maximum 100) until all results have been received. Use the returned name, not a catalog capability identifier, in the tool_use block.

curl 'https://api.tooluse.net/v1/tools' \
  -H "Authorization: Bearer $TOOLUSE_API_KEY"

Find this command in the tool list permitted by your key. Replace svc_FROM_YOUR_TOOL_LIST with its returned name. Use a new Idempotency-Key for each new call and retain it when retrying that same call.

HTTP call

curl 'https://api.tooluse.net/v1/tool-calls' \
  -H "Authorization: Bearer $TOOLUSE_API_KEY" \
  -H 'Content-Type: application/json' \
  -H 'Idempotency-Key: replace-with-a-new-call-id' \
  --data '{
  "type": "tool_use",
  "id": "toolu_example",
  "name": "svc_FROM_YOUR_TOOL_LIST",
  "input": {}
}'

Send one Claude tool_use block per request. Keep the same Idempotency-Key when retrying the same request; use a new key for a new call. The response includes the shared Tooluse.net receipt and Claude tool_result. Check both HTTP status and the returned tool result before treating a call as successful.

Commands

Verify this bot’s workspace identity — slack-bot.auth.test

Verify this bot’s workspace identity

This is a read operation. Provider rate limits and data access rules still apply.

Connect and use

Parameters

Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.

This tool has no input parameters.

Full JSON Schema

Full JSON Schema

Example input

{}

At most 1 provider requests per invocation; timeout: 30 seconds.

List one page of bot-visible conversations — slack-bot.channels.list

List one page of bot-visible conversations

This is a read operation. Provider rate limits and data access rules still apply.

Connect and use

Parameters

Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.

Parameter Type Required in parent Description Constraints
query object Optional additionalProperties: false
query.limit integer Optional minimum: 1; maximum: 100
query.cursor string Optional minLength: 1
query.types string Optional enum: ["public_channel","private_channel"]

Full JSON Schema

Full JSON Schema

Example input

{}

At most 1 provider requests per invocation; timeout: 30 seconds.

Read one page of a channel’s messages — slack-bot.messages.list

Read one page of a channel’s messages

This is a read operation. Provider rate limits and data access rules still apply.

Connect and use

Parameters

Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.

Parameter Type Required in parent Description Constraints
query object Required additionalProperties: false
query.channel string Required minLength: 1
query.limit integer Optional minimum: 1; maximum: 100
query.cursor string Optional minLength: 1
query.oldest string Optional minLength: 1
query.latest string Optional minLength: 1

Full JSON Schema

Full JSON Schema

Example input

{
  "query": {
    "channel": "example"
  }
}

At most 1 provider requests per invocation; timeout: 30 seconds.

Post a handoff to a selected Slack channel — slack-bot.messages.post

Post a handoff to a selected Slack channel. One explicit provider request; no retries or automatic follow-up pages. Customer permissions and quotas apply.

This operation can change provider data. Review the input before allowing an agent to call it.

Connect and use

Parameters

Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.

Parameter Type Required in parent Description Constraints
body object Required additionalProperties: false
body.channel string Required minLength: 2; maxLength: 80; pattern: "^[CGD][A-Z0-9]+$"
body.text string Required minLength: 1; maxLength: 4000
body.thread_ts string Optional minLength: 3; maxLength: 40; pattern: "^[0-9]+\\.[0-9]+$"

Full JSON Schema

Full JSON Schema

Example input

{
  "body": {
    "channel": "C0123456789",
    "text": "Renewal handoff ready: Alex owns the follow-up. Please review the linked account brief.",
    "thread_ts": "1794412800.000001"
  }
}

At most 1 provider requests per invocation; timeout: 30 seconds.

Errors

Check the key's expiry, revocation, workspace and allowed operations.

Reuse the same idempotency key only for the same request.

The connection or provider limit has been reached. Check the receipt before retrying.

Test the connection

Open the integration's commands below to inspect parameters and examples. Start with a read command for an account or resource you can access. Refresh your client's tool list, use the returned tool name, and check the execution result and usage. Provider charges and permissions still apply. Never test a write against production data without reviewing it.

Official provider documentation

Type to search…

↑↓ navigate↵ selectEsc close