Home Slack standup bot

A Slack standup bot, from the morning DM to the summary

Questions by DM at each person's local hour, one summary in the channel, slash commands and an App Home tab. Nobody opens a dashboard to take part.

Add to Slack installs Morgenruf on the free hosted instance CloudDrove runs. Self-hosting is the same MIT code.

The Today page showing the morning's answers and blockers

The dashboard is for whoever runs it. Everyone else stays in Slack.

Morgenruf is a free Slack standup bot. It DMs each person your questions at their local hour, posts one summary to the channel, and adds slash commands and an App Home tab. It is open source (MIT), free on a hosted instance or self-hosted, and also runs coffee chats and kudos.

Last reviewed September 26, 2026

What a Slack standup bot does, and what this one does

A standup bot asks each person the same few questions every working morning and puts the answers somewhere the team will actually read them. That is the whole category. Morgenruf does it entirely inside Slack: a direct message at your local hour, a summary in the channel an hour later, and nothing to log into. The dashboard is for whoever sets it up, and most weeks they do not open it either.

This page is the general one. The two questions that follow it usually are the licence and the hosting, which have pages of their own: what the MIT licence covers and where the container and the database end up.

  • A direct message at your local hour with your team's questions.
  • A summary in the channel, grouped by person or by question, blockers pulled out, optionally in a thread.
  • Slash commands: /standup, /skip, /kudos @teammate a reason, /help.
  • An App Home tab with your standups, your streak, your remaining kudos, and buttons for vacation and pausing coffee chats.
  • Group introductions for coffee chats, with the time vote in the message.
09:30 The bot DMs each person 09:31 They answer in their own time 10:30 One summary posts to the channel 10:10 A private nudge to whoever has not
Everything a teammate sees happens in Slack: the DM, the nudge if they are late, and the summary.

The scopes it asks for

Standups need to read channel membership, write messages, and open DMs. Coffee chats add three scopes for group DMs and timezones. Kudos needs emoji read access to use your own token. There is no scope for reading channel history, because it never does. Every scope, with the reason.

Coffee chat settings with a live preview of the Slack message

The settings page shows the Slack message it will produce, as you edit it.

What it is not

  • Not a meeting recorder or a transcript bot.
  • Not a productivity score. There is no ranking of people by output.
  • Not something you have to run. The hosted instance is free; self-hosting is the option for teams that want the data in their own database.

Adding it to your workspace

The quick way is the Add to Slack button: it installs Morgenruf on the free hosted instance in about two minutes. To self-host, create the app from the manifest, install it, invite the bot to a channel, and make your first standup. That route is about twenty minutes. Either way, the ten minutes after that go on the standup itself: questions, hour, timezones, who is in it, what happens when someone is on leave. If you are still deciding, how this lines up against the hosted standup bots is the page for that.

Questions

About the Slack app

Does it work on Slack's free plan?

Yes. It uses standard app APIs available on the free plan.

Can it post to a different channel from the one it asks in?

Yes. Questions go by DM, and the summary can post anywhere the bot has been invited.

Does it read our channel messages?

No. It reads replies to its own DMs and channel membership where you point it. It has no history scope.

What about Microsoft Teams or Google Chat?

Google Chat is in beta; Teams as a platform is in progress. Slack is first class.

Free for every seat, and that is the whole pricing page

Add to Slack puts Morgenruf on the free hosted instance CloudDrove runs, in about two minutes. Or self-host the same MIT code with Docker Compose or Helm and pay only for the server.