Slack integration

Communication · 8 actions · OAuth or Bearer token auth

Team communication and collaboration platform for messaging, channels, and workspace management

Put Slack to work View Slack integration docs

Overview

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.

Ask the assistant

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 toadd_reaction
Show me the channels that match what I describe
resolves tolist_channels

Use cases

What you can automate with Slack

Pull a list of channels for a reportlist_channels
Post a message on your behalfpost_message
Reply to a to thread in contextreply_to_thread
Add a reaction on the flyadd_reaction
Look up a channel history on demandget_channel_history

At a glance

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 updatedJun 2026

Reference

All 8 Slack actions

Channels1

list_channels

List public channels in the Slack workspace with pagination

Messages1

post_message

Post a new message to a Slack channel

To Threads1

reply_to_thread

Reply to a specific message thread in Slack

Reactions1

add_reaction

Add a reaction emoji to a message

Channel Histories1

get_channel_history

Get recent messages from a Slack channel

Thread Replies1

get_thread_replies

Get all replies in a message thread

Users1

get_users

Get a list of all users in the Slack workspace with their basic profile information

User Profiles1

get_user_profile

Get detailed profile information for a specific user

See full parameters and response schemas in the Slack integration docs

Two ways

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.

Security

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.

Step-by-step setup in the Slack docs

Pairs well with Slack

Agents often chain Slack with these — connect them once and the agent can use all of them in a single task.

Zoom23 actions

AgentMail21 actions

Microsoft Outlook20 actions

Telegram Bot17 actions

Twilio17 actions

Microsoft Teams12 actions

FAQ

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.

No. The agent selects the right Slack action from your prompt. A workflow is only needed when you want a repeatable process — and the composer builds that for you from a description.

Through OAuth — you connect your Slack account once and ModuleX stores the token encrypted, scoped to your organization.

8, spanning channels, messages, reactions and channel histories.

Slack runs on your own credentials, so any Slack usage is billed by Slack directly. ModuleX meters the agent run — and if you connect your own model keys, there's no ModuleX markup on model usage.

Put Slack to work in ModuleX.

Connect Slack once with your own credentials and let your agent run all 8 actions on demand.

Put Slack to work View technical docs

Last updated: Jun 2026Browse all 175 integrations →