Weekly Stand-up Reminder in Slack

Keep your team aligned without anyone remembering to post the prompt. This blueprint automatically sends a structured weekly stand-up template to a Slack channel every Monday morning, asking the team to share last week's achievements, this week's priorities, current risks or blockers, and where they need support. It replaces the manual, easy-to-forget ritual of typing the same message every week and gives async and distributed teams a consistent, threaded check-in cadence.

How it works

A scheduled trigger fires the workflow, which posts a preformatted message to your Slack channel.

1. The weekly_monday_morning trigger of type io.kestra.plugin.core.trigger.Schedule runs on the cron 0 9 * * 1 (every Monday at 09:00 UTC). It ships disabled: true so you can review and adjust it before going live.
2. The post_weekly_standup_prompt task of type io.kestra.plugin.slack.app.chats.Post authenticates with your bot token and posts the stand-up template to the target channel.
3. The messageText includes the current date via {{ now() }} and four prompts (Last week, This week, Risks / Blockers, Support needed), inviting the team to reply in a thread.

What you get

• A consistent, structured stand-up posted automatically every week.
• Threaded replies that keep the channel organized.
• A full execution history of every prompt that was sent and when.
• One declarative file you can version control and review.

Who it's for

• Engineering and product managers running async stand-ups.
• Distributed and remote teams across time zones.
• Team leads who want a repeatable check-in ritual without manual effort.

Why orchestrate this with Kestra

A Slack reminder or scheduled message handles a single channel in isolation, but it gives you no run history, no retry on transient API failures, and no way to chain the prompt into broader workflows. With Kestra you get a declarative YAML definition under version control, an event-driven Schedule trigger, automatic retries, and full execution lineage showing exactly what was posted and when. You can branch into other tasks (pulling open tickets, summarizing the previous week, paging an on-call) that a standalone Slack scheduler simply cannot do.

Prerequisites

• A Slack workspace and a Slack app with the chat:write scope.
• The app installed into your workspace and invited to the target channel.
• The channel ID for the destination channel.

Secrets

• SLACK_TOKEN: your Slack bot token (begins with xoxb-).
• SLACK_CHANNEL_ID: the target channel ID (begins with C).

Quick start

1. Create a Slack app, add the chat:write scope, and install it to your workspace.
2. Invite the bot to the channel where the stand-up should appear.
3. Store the bot token as the SLACK_TOKEN secret and the channel ID as the SLACK_CHANNEL_ID secret.
4. Adjust the cron expression in weekly_monday_morning for your team's timezone.
5. Remove disabled: true from the trigger to activate the schedule.

How to extend

• Customize the messageText template with your team's own stand-up questions.
• Add tasks before the post to pull open issues, PRs, or metrics and embed them in the prompt.
• Fan out to multiple channels by adding more Post tasks or looping over channel IDs.
• Post a follow-up reminder later in the day, or summarize threaded replies on Friday.

Links

• Slack plugin documentation
• Slack orchestration with Kestra