Slack Scheduled Standup Collector

Task

Automate daily standups in Slack by scheduling standup prompts using @Slack/Schedule MessageName it "Slack/Schedule Message" and call it with @Slack/Schedule Message, collecting team responses using @Slack/Search MessagesName it "Slack/Search Messages" and call it with @Slack/Search Messages, and posting a compiled summary using @Slack/Send MessageName it "Slack/Send Message" and call it with @Slack/Send Message. Replace standalone standup tools with a workflow that lives entirely in Slack.

Input

The user will provide:

1. The Slack channel for standups (e.g., #engineering-standup, #team-daily)
2. The time to send the standup prompt (e.g., 9:00 AM EST)
3. Optional: custom standup questions (default: What did you do yesterday? What are you doing today? Any blockers?)
4. Optional: the time to collect responses and post the summary (e.g., 10:30 AM EST)
5. Optional: team members to expect responses from

Example: "Schedule a standup prompt in #eng-standup at 9am EST every day and compile the responses at 10:30am."

Context

Standup Workflow

Step 1: Schedule the Prompt Use @Slack/Schedule MessageName it "Slack/Schedule Message" and call it with @Slack/Schedule Message to schedule a standup prompt at the specified time:

Daily Standup — [Date]

Please reply in a thread with your update:

1. What did you complete yesterday?
2. What are you working on today?
3. Any blockers or things you need help with?

Step 2: Collect Responses Use @Slack/Search MessagesName it "Slack/Search Messages" and call it with @Slack/Search Messages to search the standup channel for replies posted after the prompt. Look for threaded responses to the standup message. Identify which team members have responded and which have not.

Step 3: Compile and Post Summary Use @Slack/Send MessageName it "Slack/Send Message" and call it with @Slack/Send Message to post a compiled summary:

What to Include in the Summary

• Each team member's update organized by person
• Common themes across the team (multiple people working on the same feature, shared blockers)
• Blockers that need attention — highlight these prominently
• Who has not posted an update yet
• Cross-team dependencies identified from the updates

What Makes a Good Standup Summary

• Keep it scannable — use bullet points and bold for names
• Lead with blockers since those need the fastest response
• Group related work to show alignment
• Flag missing updates without being punitive
• Include a count: "8/10 team members reported"

Output

Scheduled Standup Prompt: Confirm the prompt has been scheduled for the specified time and channel.

Standup Summary — [Date]:

Participation: [X/Y] team members reported

Blockers (Action Required):

• [Person]: [Blocker description]

Updates by Team Member:

• [Person 1]: Yesterday: [summary] | Today: [summary]
• [Person 2]: Yesterday: [summary] | Today: [summary]

Common Themes:

• [Theme 1]: [Who is working on it]
• [Theme 2]: [Who is working on it]

Missing Updates:

• [Person who has not posted]

Compiled by Cotera Standup Collector