Back to integrations

Slack integration for background agents

Enable access to Slack Web API endpoints and Slack Events API callbacks.

Integration details

Connection

  • MCP via Slack app

Agent actions

Slack CLI

  • Use Slack CLI

    Run Slack CLI commands with the configured Slack connection.

Slack MCP

  • slack_auth_test

    Check Slack authentication state.

  • slack_conversations_list

    List Slack conversations.

  • slack_conversations_info

    Show details for a Slack conversation.

  • slack_conversations_history

    Fetch Slack conversation history.

  • slack_conversations_replies

    Fetch replies in a Slack thread.

  • slack_chat_post_message

    Post a Slack message to a conversation or thread with text, Block Kit blocks, block elements, and attachments.

  • slack_chat_update

    Update a Slack message with text, Block Kit blocks, block elements, and attachments.

  • slack_chat_delete

    Delete a Slack message.

  • slack_chat_get_permalink

    Get a permalink for a Slack message.

  • slack_reactions_add

    Add a Slack message reaction.

  • slack_reactions_remove

    Remove a Slack message reaction.

  • slack_files_info

    Show Slack file metadata.

  • slack_files_download

    Download a Slack file to a local path.

  • slack_files_upload

    Upload a local file to Slack.

  • slack_emoji_list

    List Slack emoji.

Credential safety

Credential-less sandboxes

Mistle lets agents access connected services without placing provider credentials inside the sandbox. Approved outbound requests are routed through Mistle's credential proxy, where authentication happens outside the agent runtime.

Credentials stay encrypted in Mistle's control plane and are applied only when a request is authorized for the calling sandbox and organization.

Read the credential-less sandboxes article
Diagram showing sandbox traffic routed through an egress proxy before credential injection.