Slack

Communication OAuth, or a bot token Windmill docs

Post messages, open modals and route approvals through Slack from any Windmill script, flow or app. Connect once — with OAuth or a bot token — then reuse the same resource everywhere, and let Slack events, slash commands and interactive buttons trigger your flows back.

What you can do with Slack

Complete, deployable projects built around Slack — the fastest way to get something real running.

Set up in 2 steps

1

Connect from the Resources page

Open Resources, click Add a resource/API and pick slack from the OAuth APIs list. Click Connect, allow access in the window that opens, then name the resource and save it. You are redirected to the Slack workspace your browser is signed in to.

2

Run your first script

Fork any script below and run it against a test channel. Messages are posted by the connected Slack app, not under your own name.

Scripts

Building blocks, if none of the projects above fit. Fork one, run it, or call it as a step inside your own flow.

Flows

Multi-step workflows that already wire Slack to something else.

All flows →

Trigger flows from Slack

Slack is not only a destination. These inbound paths are supported today.

Slash commands

A command like /deploy staging hits a webhook and starts a flow with the arguments as inputs.

Events API

Subscribe to message, reaction_added or app_mention and run a script once per event.

Interactive blocks

Buttons and modals resume a suspended flow step.

Resource type

slack — the shape of the credential every script on this page expects.

View raw schema →
FieldTypeRequiredWhat it is
tokenstringNoThe slack token

Questions

OAuth or a bot token?

Both give the workspace a bot token, so messages go out as the app either way. OAuth is one click and needs no Slack app of your own, but its scopes are fixed: posting, joining channels and uploading files. Create your own app when a script needs a scope outside that set — reading channel history, for instance.

Do I need a paid Slack plan?

No. A free workspace covers everything the scripts here do.

Is my token stored on the hub?

Never. It lives only in your own Windmill workspace, encrypted at rest.

There is no Connect button on my instance

Self-hosted instances need an OAuth client configured once by an admin before the tile appears. Until then, use a bot token.