start here

start using Slack with your agents

sign up, open a project, and authorise Slack from its connectors settings.

Start 7-day trial with Slack
integrationsconnectorupdated
schematic diagram of the work aldena agents do through Slack
Slack

ai agent for slack: read the channel, answer in the thread, wake on a mention

connect slack to a project and its agents read channels and threads, post, schedule and react where the bot is a member, and wake on messages, mentions and reactions.

events
10
resource types
2
access grants
8

slack is where questions get asked and alerts get noticed, and it is usually where the answer should land too. connecting slack to a project gives its agents both halves: they read channels and threads, and post, reply, schedule and react in the channels the bot is in. an agent can also subscribe from a chat, so the next matching message, mention or reaction starts a run with the text in hand, in that chat or in a new chat in the same project when the routine opens one per event. the tools come with the connector, so there is no slack mcp server to add.

reading channels and threads

slack_read_channel returns a channel's newest messages along with its topic and purpose, and slack_read_thread follows the replies under one message. each message carries its ts, author, text, thread and reaction summary, and the files attached to it. slack_read_file opens a text file someone shared, up to 1 mb, and refuses images, pdfs and other binary files, as well as files hosted outside slack. slack_search_channels, slack_search_users and slack_search_emojis find things by name, slack_list_channel_members says who is in a channel, slack_read_user_profile resolves one person, and slack_get_reactions reads what people signalled without typing.

message text, thread replies, file contents and a channel's topic and purpose reach the agent fenced off as untrusted data, the same way event text does, so a message can inform the agent but cannot instruct it.

posting, scheduling and reacting

slack_send_message posts to a channel, or replies in a thread when it is given the parent message's ts, and returns a permalink to what it posted. slack_schedule_message queues a post for a time up to 120 days ahead, slack_add_reaction acknowledges a message with an emoji, and slack_create_conversation opens a new public or private channel. everything appears as the app's bot user, not as the person who connected slack.

all four ask before they run by default. the project's Settings → Permissions lists every slack tool with its own allow, ask or deny control, and a call to a tool set to deny is refused without running.

subscribing from a chat

slack_subscribe takes a resource, the events to watch, and what the agent should do when one arrives. a channel routine takes a channel id or a name like #support, resolved to an id at subscribe time so a later rename does not break it, and fires on posted messages, reactions added or removed, members joining or leaving, files shared and app mentions. a workspace routine fires when a channel is created or archived and when someone joins the workspace. slack_unsubscribe takes an event routine off again, and the project's Settings → Routines lists every routine the agents hold.

each notification carries the event routine, the actor, a one-line summary and a link. a posted message or an app mention also carries the full message text, while the summary only says posted a message or mentioned the app. the text is fenced off as untrusted data and capped at 4,000 characters.

which channels the bot works in

agents read and post only in channels the bot is a member of: public channels, and private channels someone invited it to. the tools never join a channel on their own, so a read or a post in a channel the bot is not in fails and tells the agent to ask for an invite. subscribing is the one exception: when an agent subscribes to a public channel the bot is not in yet, the bot joins it at that moment. private channels always need an invite in slack.

direct messages and group dms are not supported. nothing lists, reads or posts in them, and no routine watches them. messages posted by any bot never start a run.

slack's history limit

slack lets aldena's app make one conversations.history call and one conversations.replies call per minute per slack workspace, with at most 15 messages each, and every project connected to the same workspace shares that minute. so slack_read_channel and slack_read_thread return up to 15 messages and never page or retry on their own. when there is more, they hand back the cursor the next call needs, and a call that lands inside the minute fails with the number of seconds to wait.

to follow a busy channel, subscribe to it instead of reading it over and over: each message event already carries the full message text.

example tasks

  • 01

    answer the question in the #support thread once you have checked the code.

    the agent reads the thread, syncs the repository to the conversation's sandbox, checks the real behaviour over bash, and replies in the same thread once you approve the post.

    slack_read_threadgithub_git_syncbashslack_send_message
  • 02

    when someone mentions the app in #incidents, read the thread and reply with what you find.

    each app mention starts a run in this chat with the message text. the agent reads the thread around it, looks into the problem, and answers in that thread, asking before it posts unless the project allows it.

    slack_subscribeslack_read_threadslack_send_message
  • 03

    remind #releases at 5pm on friday that the code freeze starts monday.

    after you approve it, the agent schedules the post in #releases for friday at 5pm and reports the scheduled message id and time, so the reminder lands on time whether or not anyone is around.

    slack_schedule_message
  • 04

    stop watching #alerts.

    the agent lists its routines, finds the event routine on #alerts, and removes it, so new messages there no longer start runs.

    list_routinesslack_unsubscribe

what it will not do

the connector does not read or post in direct messages or group dms, search messages, or edit or delete any message, its own included. it does not join a channel to read or post there, cannot reach a private channel the bot was never invited to, and asks slack for no user scopes, so nothing it does acts as the person who connected it. workspace administration, user management and app configuration are out of reach, and no event starts a run while the connection waits for a reconnect.

what starts a run

every Slack event an agent can subscribe to, grouped by resource. an agent subscribes from a chat with slack_subscribe, and each matching event starts a run in that chat, or in a new chat in the same project when the routine opens one per event.

channel7 events
  • message_posted
  • reaction_added
  • reaction_removed
  • member_joined
  • member_left
  • file_shared
  • app_mention
workspace3 events
  • channel_created
  • channel_archived
  • user_joined_team

what agents can call

every Slack tool an agent in a connected project can reach. the project's permissions can set each one to allow, ask or deny.

readallowed by default
  • slack_read_channel

    Read recent messages in a channel.

  • slack_read_thread

    Read the replies of a message thread.

  • slack_read_file

    Read the contents of a text file shared in Slack.

  • slack_read_user_profile

    Read a workspace user's profile.

  • slack_list_channel_members

    List the members of a channel.

  • slack_search_channels

    Find channels by name.

  • slack_search_users

    Find workspace users by name.

  • slack_search_emojis

    Find the workspace's custom emoji.

  • slack_get_reactions

    Read the reactions on a message.

writeasks by default
  • slack_send_message

    Post a message to a channel or thread.

  • slack_schedule_message

    Schedule a message to be posted later.

  • slack_add_reaction

    Add an emoji reaction to a message.

  • slack_create_conversation

    Create a new public or private channel.

  • slack_subscribe

    Create an event routine on a Slack channel or the workspace.

  • slack_unsubscribe

    Remove one of the agent's Slack event routines.

what you grant

aldena asks Slack for exactly this access on the consent screen, the same set for every project. there is nothing to pick, and nothing else is requested.

  • Channels
    channels:readgroups:read

    Agents find public channels and the private channels the bot is in, and read their details and members. Member and channel events arrive through it.

  • Message history
    channels:historygroups:history

    Agents read messages and threads in channels the bot is in. Message events arrive through it.

  • Members and workspace
    users:readteam:read

    Agents look up people, and Aldena names the workspace when you connect. New-member events arrive through it.

  • Files, emoji and reactions
    files:reademoji:readreactions:read

    Agents read text files, find custom emoji and read reactions. File and reaction events arrive through it.

  • Join public channels
    channels:join

    Join a public channel when an agent subscribes to it. Private channels need an invite.

  • Post messages and react
    chat:writereactions:write

    Agents post, reply, schedule messages and add reactions, asking first by default.

  • Create channels
    channels:managegroups:write

    Agents create public or private channels, asking first by default.

  • Mentions
    app_mentions:read

    Slack delivers @-mentions of the app to app_mention routines. The trigger already maps these events, but until now Aldena never requested the scope, so they never arrived.

how to connect Slack

connecting Slack takes one authorisation round trip, started from inside the project that needs it.

  1. open the project's connectors settings

    connections belong to a project, not to your account or the team. open the project that needs Slack, go to settings → connectors, and press connect. other projects stay untouched.

  2. authorise with a real account

    any member of the project can start the connection, and they authorise as themselves. Slack asks only for the fixed access listed above, with no scopes to choose.

  3. an agent subscribes from a chat

    ask an agent in a project chat to watch something in Slack. it calls slack_subscribe with the resource, events and intent, and settings → routines lists each routine it holds.

  4. a matching event starts a run

    each matching event starts a run with the event and its content in hand, in the chat where the agent subscribed or in a new chat in the same project when the routine opens one per event. disconnecting Slack stops every subscription to it.

data handling and security

a connector holds one credential and turns Slack events into runs. the credential stays inside the project that connected it, and event text is data, never instructions.

  • one connection, one project

    the Slack credential is stored against the project it was authorised in. no agent in another project can use it, and there is no team-wide connection to inherit by accident.

  • tokens encrypted at rest

    the Slack token is encrypted before it is stored, and it never appears in a chat or in an agent's prompt. agents get the events, not the credential.

  • events only where a routine watches

    aldena verifies each delivery came from Slack. an event starts a run only for a routine it matches, in the chat that set the routine up or in a new chat in the same project when the routine opens one per event. nothing starts while the connection needs a reconnect.

  • event content is untrusted

    event text may come from a stranger. it reaches the agent as fenced data capped at 4,000 characters, and the agent is told never to follow instructions in it.

  • revocation is one click

    disconnect Slack and the project's event routines on it stop at once, along with the stored credential.

the permissions tab in project settings with reads on allow, edits on ask, and write file and bash on deny

each Slack tool agents hold has its own allow, ask or deny row in the project's permissions. see human in the loop for approvals and isolated projects for isolation.

faq

can an ai agent post or reply in slack?

yes. agents post, reply in threads, schedule posts and add reactions, asking first by default. the bot posts as the app, and only in channels it belongs to.

does the bot need to be invited to a channel?

to read or post there, yes. the tools never join a channel on their own, so invite the bot in slack first, and a call in a channel it is not in tells the agent to ask for that invite. subscribing is the one exception: when an agent subscribes to a public channel the bot is not in yet, the bot joins it at that moment. private channels always need an invite.

can the agent read direct messages or search the workspace?

no. the tools work in public channels and in private channels the bot is in, and nothing lists, reads or posts in a direct message or group dm. there is no message search either: aldena asks slack for bot scopes only and holds no token that acts as a person. agents find channels and people by name and read the channels they are pointed at.

why does the agent read only 15 messages at a time?

slack lets aldena's app make one channel history call and one thread call per minute per workspace, with at most 15 messages each, and every project connected to that workspace shares that minute. the read tools never retry or page on their own. they hand back the cursor for the next call, and a call inside the minute fails with the number of seconds to wait.

what does a slack event notification contain?

the event routine, the actor, a one-line summary and a link. a posted message or an app mention also carries the full message text, and the summary itself only says posted a message or mentioned the app. the text is fenced off as untrusted data and capped at 4,000 characters.

will an agent wake up on bot messages?

no. messages posted by any bot, including other apps in the workspace, never start a run, so a channel full of automated alerts from another bot will not wake the agent. subscribe to app mentions or to human messages in that channel instead.

ready when you are

spin up your first project.

one project per client, product, or piece of work, staffed with intake, requirements, build and code review agents.