Skip to main content

Documentation Index

Fetch the complete documentation index at: https://learn.actionist.ai/llms.txt

Use this file to discover all available pages before exploring further.

Slack is the most common surface Actionist agents talk through. Use it as a notification destination, an inbox to triage, or a trigger source for incoming events.

​
What you can do

  • Send messages to channels, threads, or DMs — formatted with blocks, mentions, and attachments.
  • Read channels and threads on a schedule or on demand.
  • React to messages with emoji from a workflow.
  • Trigger workflows from new messages, mentions, reactions, or slash commands.

​
Setup

1

Install the Slack MCP server

Open Integrations → Discover, search for “Slack”, and click Install. Actionist starts the server locally.
2

Authenticate

The OAuth flow opens in your browser. Grant the workspace and channel scopes you want Actionist to use. The token lands in the Credentials Vault.
3

Bind to an agent

Open the agent you want to use Slack from → Tools → toggle Slack on. The agent can now call any of Slack’s actions.

​
Common workflows

  • Morning Slack digest — pull yesterday’s unread DMs and important channel mentions, summarize into a Notion page, post a link in your #daily channel.
  • PR review nudges — react :eyes: to every GitHub PR posted in #engineering that’s been open >24h.
  • Inbox triage — for every new DM, draft a reply in the thread (as a draft only), tag the most important ones with :fire:.
  • Standup capture — gather Monday standup messages from #team and produce a 5-bullet summary for the manager’s inbox.

​
Limits & gotchas

  • Rate limits. Slack throttles tier-based — agents posting in many channels at once may hit rate_limited. Wrap channel-blast actions in a Steps loop with a 1s delay.
  • Reactions can’t be removed in bulk. Plan accordingly.
  • Threaded replies need thread_ts. The first message in a thread is the parent.
  • Private channels need the bot to be invited. Slack will error otherwise.