How do I connect Discordbot and Slack to Operator?

You authorize Discordbot and Slack once each from your Operator dashboard. Operator holds both connections and refreshes the access tokens for you, so your agent keeps working across them without you signing in again.

What can my agent do across Discordbot and Slack?

Tell it the job and it moves between Discordbot and Slack as one task, choosing which actions to run on each side. There is nothing to map and no trigger to configure; you give instructions the way you would to a person.

Can my agent keep Discordbot and Slack in sync?

Yes. It can watch Discordbot and act in Slack, or keep both in step, reading from one and running the matching update in the other. This runs on demand when you ask or on a schedule you set.

Do I need to build a workflow or write code?

No. There is no workflow to build, no fields to map, and no API keys to paste. Operator manages both connections, and you give the agent instructions in plain language.

← All integrations

Connect Discordbot to Slack

Try for free

Automate Discordbot and Slack with AI

Discord communities and Slack workspaces split when announcements need to reach both audiences. Operator.io points your OpenClaw agent at Discordbot and Slack so a message you approve in one app can post to the other with formatting preserved, and flagged items in Slack can open a Discord thread for the community team. Ask for the last cross post on a topic and it shows both copies and timestamps.

It reaches both apps directly or through connectors like Composio MCP and Pipedream MCP, which handle the sign in and token refresh, so there is no Zap to build and no API keys to paste.

What your agent can do with Discordbot and Slack

What your agent does in Discordbot

Add recipient to group channel
Adds a user to a Discord group DM channel. Requires a user OAuth2 access token with the gdm.join scope. Bot tokens cannot be used for this endpoint.
Add guild member
Adds a user to a Discord guild using their OAuth2 access token (which must have guilds.join scope). Returns the guild member object on 201 Created, or indicates the user is already a member on 204.
Assign role to guild member
Assigns a role to a guild member. Requires MANAGE_ROLES permission and the role must be lower in hierarchy than the bot's highest role. Returns 204 on success.
Add Reaction To Message
Adds an emoji reaction from the bot to a message. Requires READ_MESSAGE_HISTORY, and ADD_REACTIONS if no one else has reacted with this emoji yet.
Add thread member
Adds a user to a specific, unarchived thread. The user must have access to the parent channel.
Ban user from guild
Permanently bans a user from a Discord guild, optionally deleting their recent messages.

All 165 Discordbot actions →

What your agent does in Slack

Add call participants
Registers new participants added to a Slack call.
Add emoji
Adds a custom emoji to a Slack workspace given a unique name and an image URL; subject to workspace emoji limits.
Add an emoji alias
Adds an alias for an existing custom emoji in a Slack Enterprise Grid organization.
Add Enterprise user to workspace
Adds an Enterprise user to a workspace. Use when you need to assign an existing Enterprise Grid user to a specific workspace with optional guest restrictions.
Add reaction to message
Adds a specified emoji reaction to an existing message in a Slack channel, identified by its timestamp; does not remove or retrieve reactions.
Add a remote file
Adds a reference to an external file (e.g., Google Drive, Dropbox) to Slack for discovery and sharing, requiring a unique `external_id` and an `external_url` accessible by Slack.

All 145 Slack actions →

How it works

Tell the agent what you want to happen between Discordbot and Slack, for example to watch one and act in the other, or to keep the two in step. It reads what it needs from Discordbot, works out what to do, and runs the matching action in Slack without you mapping a single field.

You can have it run once, on a schedule, or whenever something changes. Ask it for a status any time and it reads the latest from both apps back to you in the same chat.

Common questions about Discordbot and Slack

How do I connect Discordbot and Slack to Operator?: You authorize Discordbot and Slack once each from your Operator dashboard. Operator holds both connections and refreshes the access tokens for you, so your agent keeps working across them without you signing in again.
What can my agent do across Discordbot and Slack?: Tell it the job and it moves between Discordbot and Slack as one task, choosing which actions to run on each side. There is nothing to map and no trigger to configure; you give instructions the way you would to a person.
Can my agent keep Discordbot and Slack in sync?: Yes. It can watch Discordbot and act in Slack, or keep both in step, reading from one and running the matching update in the other. This runs on demand when you ask or on a schedule you set.
Do I need to build a workflow or write code?: No. There is no workflow to build, no fields to map, and no API keys to paste. Operator manages both connections, and you give the agent instructions in plain language.

Discordbot and Slack integrations

Discordbot

Slack

More pairings

Active campaign + Slack Affinity + Slack Airtable + Slack Amplitude + Slack Apollo + Slack Asana + Slack Attio + Slack Better stack + Slack

Put your agent on Discordbot and Slack

Sign in, connect both apps, and hand your agent the work. The same setup reaches every app in the catalog. Your first week is free.

Try for free