Slack

Slack is a connector: it links a MeDo app to one Slack workspace, so the app can find channels, search messages, read recent channel history, and post a message to a channel or thread. The app sees what the connected account can see.

#What you can build

• A team knowledge page. Search project discussions by keyword and open the channel context behind each match.
• A project communication page. Show recent messages from one selected channel next to follow-up notes stored in the app.
• An incident update tool. Compose an alert, preview the destination channel, and post only after confirmation.
• A channel update composer. Draft a message or a thread reply and review it before it goes out.

Slack fits when a team needs its own conversations inside a purpose-built tool — onboarding hubs, release pages, support dashboards. It is not a bot platform: there are no event subscriptions or background listeners, see Limits.

#Build examples

Copy one of these into the prompt box. The first one is the smallest useful starting point.

Use @Slack to build a private team knowledge page where I can search project discussions by keyword and read recent messages from a selected channel.

Use @Slack to build a private project communication page with recent channel messages and follow-up notes stored in the app.

Use @Slack to build an incident update tool where I can preview an alert and its target channel, then confirm before posting.

Use @Slack to build a private channel update composer where I can review a message or thread reply before sending it to the selected conversation.

#Prepare and connect

You need a Slack account with access to the workspace the app should use. No Slack app, bot token, or admin approval is involved on your side.

1. Open Skills & Connectors in the sidebar and search for Slack.
2. Open the Slack card and click Connect.
3. Sign in to Slack and approve the access MeDo asks for.
4. The button changes to Connected.

If you start building before connecting, MeDo shows a Slack connection button under its reply. You can connect there instead.

#Use it in your app

• The app uses your connected workspace, not each visitor's own Slack account. Everyone who opens a channel view sees the same workspace. Put the page behind your app's own sign-in and keep internal channels limited to the intended people.
• Pick one channel or thread as the destination. A public form or update composer should send to a fixed channel that the owner chose, not to whatever a visitor types.
• Messages are read when the app loads or refreshes. There is no live stream; add a refresh control if the page needs newer messages.
• Posting is confirmed first. MeDo previews the destination and the message text before sending.
• Notes belong to the app. Follow-up status and internal notes live in your app's tables, not in Slack.

#Limits and troubleshooting

"Connection required" appears in the app. Ask the app owner to open the connector card and click Connect, then reload.

Channel history returns only a handful of messages. History is returned one page at a time. Add a load-more control instead of assuming messages are missing.

A post fails with a rate-limit message. Slack rate limits apply to the connected account. Wait and retry by hand; MeDo does not retry automatically.

Search finds nothing useful. Free-text search across a whole workspace is broad. Ask the app to search a narrower phrase, or read the specific channel instead.

#Related

• Connector catalog — the other connectors and what they are for.
• Skills & Connectors — how Skills are called, priced, and limited.
• Managing access & roles — restrict who can read connected data.