Integration · Automate and collaborate

Slack and Meteor AI agents

Connect Slack to a WhatsApp Met: search messages and channels, alert your team, read threads and write canvases through Slack's official MCP server.

Book a demo See every integration

How does Slack connect to Meteor?

With the Slack ready connector, your WhatsApp Met works in your company's Slack workspace with the account the admin authorizes. It finds a channel or a person, sends a message summarizing what a customer needs, reads the thread where your team replied and brings that answer back to the customer. It also searches messages and files, schedules messages and creates or updates canvases. It is Slack's official server: it needs a Slack app from your company approved by the workspace admin, and usage runs on your Slack account and its API limits.

What it automates

What a Meteor Met does with Slack

Hand the team a case that needs a person

When the customer asks for something the Met cannot solve, it finds the support channel or the person in charge and sends them a message with a summary of the conversation and the phone number.

Bring the team's answer to the customer

When the customer writes again, the Met reads the Slack thread where your team replied and answers with that information, without anyone copying it over to WhatsApp.

Find what the team already answered

Before escalating, the Met searches public channels to see whether someone already solved that same question and uses that answer, so the question is not asked twice.

Leave a summary in a canvas

The Met creates or updates a canvas with the day's cases or the questions that come up most, so the team reads it inside Slack.

14 tools

Everything your Met can ask Slack for

Each one is a real action in the connector. You can switch off the ones you would rather it never used.

Tool	What it does
`slack_search_public`	Searches messages and files in public channels, with date, person and type filters.
`slack_search_public_and_private`	Also searches messages and files in private channels and direct messages, with consent.
`slack_search_channels`	Finds channels by name or description.
`slack_search_users`	Finds people in the workspace by name, email or ID.
`slack_send_message`	Sends a message to a channel, a direct message or as a thread reply.
`slack_schedule_message`	Schedules a message to be sent later.
`slack_read_channel`	Reads the message history of a channel or a direct message.
`slack_read_thread`	Reads a full thread, with the original message and its replies.
`slack_create_canvas`	Creates a formatted canvas.
`slack_update_canvas`	Changes the content of an existing canvas.
`slack_read_canvas`	Reads a canvas's content and returns it as formatted text.
`slack_read_user_profile`	Fetches a person's profile, with their custom fields and status.
`slack_get_file_upload_url`	Returns a signed link to upload a file to Slack; it is the first of two steps.
`slack_complete_file_upload`	Completes the file upload and, if you want, shares it in a channel; it is the second step.

The limits

What the Slack integration does NOT do

We would rather say it here than have you find out during rollout.

It does not ask for confirmation in the chat before sending a message in Slack. The admin chooses in Connections which actions stay on, and sending messages is not switched off on its own.
It does not connect without a Slack app from your company: Slack requires the MCP client to be an app published in its directory or an internal app, with a client ID and client secret, and it does not accept automatic registration.
It does not find out on its own what happens in Slack: there is no trigger that wakes the Met when your team replies. It reads the thread when the customer writes again or when someone asks it to.
It does not search private channels or direct messages without the consent of the authorizing person; without it, search stays within public channels.
It does not get around Slack's limits: each action has its Web API tier, for example about 20 user or channel searches per minute, and they apply the same as outside the connector.
It sees no more than the account that authorized the connection, and usage runs on your Slack account.

Before you start

What you need to connect Slack

1

A Slack app from your company

You create an app at api.slack.com, add the return URL Met shows you under OAuth and permissions, and copy its Client ID and Client Secret. It has to be an internal app of your workspace or one published in the Slack directory.
2

Approval from the Slack workspace admin

If your Slack workspace requires app approval, the administrator approves the app through Slack's normal approval process before Met can connect.
3

Connect it in Met

In Met, open Connections → Slack → Connect, paste the Client ID and the Client Secret and authorize with your Slack account. Then you choose which actions stay on.

Frequently asked questions

Questions about Slack and Meteor

As the person who authorizes the connection: Slack's server uses a user token. That is why it helps to connect with an account the team recognizes as the support desk's.

Only if the authorizing person consents to searching private channels and direct messages. Without that consent, it only searches public channels.

Because Slack only lets registered apps with a fixed ID use its MCP server, and they must be internal to your workspace or published in its directory.

Yes. Slack records the actions that go through its MCP server in its audit logs, on the Slack plans that include them, the same as for any connected app.

Step by step