Slack integration

    Bring governed workflows into Slack.

    Use Slack as the human coordination surface for durable AgentRuntime workflows: discover accessible channels and users, read conversation context, post messages, reply in threads, and add reactions.

    See the incident blueprint →Back to integrations
    GitHubPostHogGmail
    Workflow layerAgentRuntime
    IntegrationSlackOAuth token

    Coordinate messages, threads, reactions, channels, and users while AgentRuntime keeps the workflow state.

    8
    Slack actions
    API + webhook
    Workflow starts

    Connect Slack with other workflow systems through AgentRuntime instead of wiring each service directly.

    Slack capabilities

    Read context and coordinate work in Slack.

    List channels and users, read message context, post updates, reply in threads, and add reactions. Available actions depend on the token scopes and workspace access you provide.

    01Read
    Channels

    List accessible channels

    List public and private channels available to the token or a configured channel allowlist.

    slack_list_channels
    02Read
    Messages

    Read channel history

    Get recent messages from an accessible Slack channel.

    slack_get_channel_history
    03Read
    Messages

    Read thread replies

    Get the messages and replies attached to a Slack thread.

    slack_get_thread_replies
    04Read
    Users

    List workspace users

    List workspace users with basic profile information.

    slack_get_users
    05Read
    Users

    Read a user profile

    Get detailed profile information for a Slack user.

    slack_get_user_profile
    06Write
    Messages

    Post a message

    Post a new message to a channel or direct message.

    slack_post_message
    07Write
    Messages

    Reply in a thread

    Post a reply beneath an existing Slack message.

    slack_reply_to_thread
    08Write
    Reactions

    Add a reaction

    Add an emoji reaction to an existing message.

    slack_add_reaction
    Connected workflow blueprint

    Use Slack as the response surface, not the state machine.

    The incident-response blueprint uses Slack to post the incident message, keep updates in its thread, read replies, and record acknowledgements while AgentRuntime retains workflow state.

    Explore the incident path →
    1. 01TriggerReceive a typed alert
    2. 02DecisionApply severity and routing rules
    3. 03SlackPost the incident message
    4. 04HumanConfirm owner and authority
    5. 05SlackKeep the response thread current
    6. 06OutcomePublish the resolution record
    Setup and access

    Connect Slack with only the access the workflow needs.

    The connector accepts a Slack bot or user OAuth token (xoxb- or xoxp-). Required scopes depend on the methods used. Start the workflow from AgentRuntime or an external alert, then use Slack for conversation context, coordination, and updates.

    Access planning

    Choose scopes and a channel boundary.

    Common scopes are shown for planning. Private-channel and direct-message patterns can require additional access. Match the final scopes to the actions selected for the workflow.

    channels:readchannels:historychat:writeusers:readreactions:write
    Read the Slack Web API documentation ↗
    slack_api_tokenRequired
    Bot or user OAuth token with scopes for the Slack methods the workflow uses.
    slack_team_idConditional
    Workspace team ID used by channel and user discovery when no channel allowlist is configured.
    slack_channel_idsOptional
    Comma-separated channel allowlist that restricts channel discovery.
    slack_api_baseOptional
    Override for the Slack Web API base URL.
    Related Communication connectors

    Define the Slack boundary before the workflow acts.

    Bring the target channels, required actions, token model, scopes, and human decision points. We will map them into a governed execution path.

    Discuss the Slack workflow →See incident response