Slack integration
Communication · 8 actions · OAuth or Bearer token auth
Team communication and collaboration platform for messaging, channels, and workspace management
The ModuleX Slack integration lets a ModuleX agent operate Slack on your behalf, running list actions across channels, messages and reactions, directly from a plain-English request, using your organization's own Slack credentials. No pre-built workflow is required: the agent picks the right Slack action for the task.
Slack is a communication platform. ModuleX adds the agent layer: ask for an outcome and it selects and runs the right Slack action. Or, when you want a repeatable process, the composer assembles a Slack workflow for you, streaming the nodes onto the canvas as it builds.
Drive Slack in plain English
Type what you want. A ModuleX agent picks the right Slack action, or chains several, and runs it. No workflow to build.
- “Add a reaction emoji to a message”resolves to
add_reaction - “Show me the channels that match what I describe”resolves to
list_channels
What you can automate with Slack
- Pull a list of channels for a report
list_channels - Post a message on your behalf
post_message - Reply to a to thread in context
reply_to_thread - Add a reaction on the fly
add_reaction - Look up a channel history on demand
get_channel_history
Slack integration at a glance
VendorSlack
CategoryCommunication
Actions available8
AuthenticationOAuth or Bearer token
Uses your own credentialsYes
Works with the assistantYes
Works in the composerYes
Multi-step / tool-chainingYes
Technical referenceView docs
Integration version1.0.0
Last updatedJul 2026
All 8 Slack actions
Channels1
list_channelsMessages1
post_messageTo Threads1
reply_to_threadReactions1
add_reactionChannel Histories1
get_channel_historyThread Replies1
get_thread_repliesUsers1
get_usersUser Profiles1
get_user_profileSee full parameters and response schemas in the Slack integration docs
Two ways to use Slack in ModuleX
Ask the assistantType what you want done and a ModuleX agent picks the right Slack action and runs it. No workflow to build.
Compose a workflowNeed it to happen every time? Describe the process and the composer wires Slack into a repeatable workflow you can run on a schedule, from chat, or as an API.
Connecting Slack
OAuthSlack uses OAuth. You connect your Slack account once; ModuleX stores the access token encrypted and scoped to your organization, so your team shares a single secure connection.
Bearer tokenSlack uses bearer-token authentication. You provide a Slack access token; ModuleX encrypts it and scopes it to your organization so the whole team can use Slack.
Works with Slack
Agents often chain Slack with these. Connect them once and one agent can use all of them in a single task.
Recipes that use Slack
Inbound Lead RoutingNew leads get scored the moment they arrive and the hot ones land in #sales while your reps are still at their desks. A ModuleX agent rates buying intent, posts the strong leads to Slack, and files every contact in HubSpot.5 steps · on every new lead
Failed Payment Follow-upA failed invoice stops being a silent number on a dashboard and becomes a tracked case your team can act on. When Stripe reports a payment failure, a ModuleX agent pulls the details, re-sends the invoice, and posts the case to Slack.6 steps · on payment failure
Support Ticket TriageNew tickets get read, prioritized, and routed the moment they land, and the urgent ones surface in Slack instead of sitting in a queue. A ModuleX agent classifies each Freshdesk ticket, sets its priority and tags, assigns it, and posts the ones that cannot wait.6 steps · on every new ticket
Brief yourself on a candidate before the callA brief covering the role, the application, and what earlier rounds already established. Built for an interviewer who opens the CV two minutes before the interview.4 steps · before each meetingCatch up on a channel you stopped readingA summary of decisions and open questions, with the items waiting on you called out. Built for anyone returning to a busy channel after two days away.4 steps · on demand
Check database health without opening the dashboardA short, regular status that tells you when something moved out of range, and stays quiet otherwise. Built for a small team with no dedicated operations engineer.4 steps · on demandPut an external MCP server to workA tool that was not in the catalog, usable in the same place as the 175+ that are. Built for teams with internal tools that no catalog will ever cover.4 steps · on demand
See which accounts went quiet this weekOne weekly digest naming the accounts that have gone quiet, with what each signal was. Built for a customer success manager who finds out about churn after it happens.5 steps · weekly
Start the day with one brief instead of five tabsOne brief covering the meetings, the messages that need a reply, and the work that is due. Built for anyone who begins the morning reconstructing the day from four apps.5 steps · weekdays 8am
Start the day knowing what moved in the repoA short brief showing what shipped and what is waiting on a person. Built for an engineering manager reconstructing yesterday from notifications.4 steps · weekdays 8am
Investigate an error spike while it is still spikingAn investigation note that starts with a timeline instead of a blank page. Built for an on-call engineer who gets an alert and a blank page to start from.5 steps · on alertDraft the next sprint from the backlog you haveA candidate list that people can argue with, ready before the meeting rather than during it. Built for a team that spends the first hour of planning finding the candidates.4 steps · weeklyPrepare everything a new joiner needs on day oneA per-role onboarding checklist with real owners and dates, created before the start date. Built for an operations lead who assembles the same onboarding list every time, from memory.4 steps · on demandPrepare for the next meeting in the gap before itA short brief on who you are meeting, what was last agreed, and what is still open. Built for anyone with back-to-back calls and no preparation time between them.5 steps · before each meetingRequest the access a new joiner needs, with a person approvingAn access request with an explicit approver and a written record of the decision. Built for an IT lead who grants access by message and remembers it later, if at all.4 steps · on demandRoute a purchase request to the right approverA request that reached the right person, with a record of who approved what. Built for an operations manager who is the bottleneck on every small purchase.5 steps · on demand
Ship the latest commit and watch the buildA deploy that was confirmed by a person, watched to completion, and reported where the team reads. Built for a small team where deploying means remembering four steps in order.5 steps · on demandTurn an overnight inbox into a short listA short digest that names the messages needing a reply and compresses everything else. Built for anyone who opens the laptop to fifty unread messages.4 steps · weekdays 8amTriage the support queue before your shift startsA queue that is grouped and ordered, with repeated issues visible as one cluster. Built for a support lead who opens the queue to sixty tickets and no order to them.4 steps · on every new ticket
Notice a ranking drop in the same week it happensA weekly digest that names the pages and queries that moved, while it is still recent. Built for an SEO owner who finds out about a drop from the quarterly review.4 steps · weekly
Get told before you sell out of somethingAn alert naming the items that are running low, before the storefront says sold out. Built for a store operator who discovers a stockout from a customer complaint.4 steps · on alert
Get the ad numbers without opening the ads managerA weekly digest with the movement per campaign, without opening the ads manager. Built for a growth marketer who checks campaigns daily out of anxiety, not insight.4 steps · weekly
Watch the funnel without building a dashboardA weekly stage-by-stage view of the funnel, assembled from the tools you already run. Built for a founder who wants the funnel numbers without another BI project.5 steps · weeklyFrom the guides
Best integrations for engineering teamsThe tools an engineering team should connect to ModuleX first, the actions each one actually exposes, and where the narrow ones still earn their place.Jul 25, 2026 · 4 min read
Best integrations for marketing teamsThe tools a marketing team should connect to ModuleX first, what the assistant can actually do inside each one, and the recipes that already chain them together.Jul 25, 2026 · 4 min readHow to connect your first toolYou don't have to plan your integrations up front. Ask for the work you actually want, and the assistant tells you what it needs access to — here's how that flow goes and how to choose the first tool well.Jul 25, 2026 · 4 min read
Best integrations for support teamsThe integrations a support team should connect to ModuleX first, and the real actions an agent can run inside each one.Jul 24, 2026 · 5 min readFrom the research
1,784 actions, 62 verbsOur catalog exposes 1,784 actions. Across 65 published task recipes, 62 of them get called — and two account for a quarter of every call. Here is what the used slice looks like.Jul 25, 2026 · 5 min readSixty-five tasks, forty-one toolsWe built a library of 65 task recipes, then counted what went into them. The tasks we could describe turned out to be small: a median of two tools, four steps, and most with no schedule at all.Jul 25, 2026 · 5 min read
Slack + ModuleX FAQ
A ModuleX agent can run any of Slack's 8 actions, across channels, messages, reactions and channel histories, from a plain-English request, using your organization's own Slack credentials.
Put Slack to work in ModuleX.
Connect Slack once with your own credentials and let your agent run all 8 actions on demand.
Last updated: Jul 2026Browse all 179 integrations