# Run an async daily standup in Slack, set up from your assistant

Source: https://clickruntime.com/use-cases/daily-standup-in-slack

> Your assistant sets up two scheduled steps in one automation: post the standup question each weekday morning, then read the replies in the thread and post a summary with blockers called out.

## Can ChatGPT or Claude run our daily standup in Slack?

An assistant can summarise a standup thread if you paste it in. Running the standup every day means posting at 9:30, waiting for replies and summarising at noon, with no one asking. With ClickRuntime, the assistant sets up an automation that does both on a weekday schedule, using a Slack account you connect, and remembers which thread belongs to today.

### Why the assistant can't do this on its own

- It has to happen every weekday at fixed times, whether or not anyone opens a chat.
- The summary needs today's thread, which the morning step remembers in state for the noon step.
- Reading replies needs a Slack connection that lasts. ClickRuntime keeps it outside the chat.

## Set it up from your AI assistant

Prompt to copy:

> Create a ClickRuntime automation for our async standup: every weekday at 9:30 Berlin time, post “Standup: what did you do yesterday, what's next, anything blocking?” in #team. At 12:00, read the replies in that thread and post a short summary in the thread, listing blockers first and who hasn't replied.

1. **Connect ClickRuntime to your assistant.** Add ClickRuntime as a connector (MCP server) in ChatGPT, Claude, Cursor or another MCP client, using https://clickruntime.com/api/mcp. You sign in with Google or email; there is no API key to copy. This is done once per assistant.
2. **Paste the prompt.** Start a new chat and paste: “Create a ClickRuntime automation for our async standup: every weekday at 9:30 Berlin time, post “Standup: what did you do yesterday, what's next, anything blocking?” in #team. At 12:00, read the replies in that thread and post a short summary in the thread, listing blockers first and who hasn't replied.” Change the details (times, channels, addresses) to yours.
3. **Read the draft.** The assistant restates what will happen, asks for anything missing, such as your timezone or which channel to post to, and saves a draft automation. A draft never runs on its own, so nothing happens until you agree.
4. **Connect accounts and save keys.** The assistant asks you to connect a Slack account in the ClickRuntime dashboard with permission to post and read channel history (the workspace's own Slack app), and to invite it to #team.
5. **Test it.** The assistant runs the morning step now so the question appears, asks you to reply in the thread, then runs the summary step and shows the result.
6. **Turn it on.** The assistant tells you what will run, when, and which services it will contact, then asks your permission to turn it on. From then on it runs on ClickRuntime's servers, and you can close the chat.
7. **Check it in the ClickRuntime dashboard.** Two runs per weekday: the 9:30 run with the thread it started, and the 12:00 run with the number of replies and blockers. State holds today's thread id. Pause the automation during holidays.

Connector setup for each assistant: https://clickruntime.com/assistants

## What the assistant writes

`async_standup.py`

```python
from datetime import datetime
from zoneinfo import ZoneInfo
from slack_sdk import WebClient
from clickruntime import on_trigger, credentials, state, ai

CHANNEL = "C0123456789"        # #team
TEAM = ["U01AAA", "U01BBB", "U01CCC"]
TZ = ZoneInfo("Europe/Berlin")

@on_trigger
def run(event):
    slack = WebClient(token=credentials.connection("slack", "team"))
    now = datetime.now(TZ)
    today = now.date().isoformat()

    if now.hour < 11:
        msg = slack.chat_postMessage(channel=CHANNEL,
            text="Standup: what did you do yesterday, what's next, anything blocking? Reply in this thread.")
        state.set("thread", {"date": today, "ts": msg["ts"]})
        return {"summary": "Question posted"}

    thread = state.get("thread") or {}
    if thread.get("date") != today:
        return {"summary": "No standup thread today"}
    replies = slack.conversations_replies(channel=CHANNEL, ts=thread["ts"])["messages"][1:]
    people = {m.get("user") for m in replies}
    missing = [u for u in TEAM if u not in people]
    if not replies:
        summary = "No updates yet."
    else:
        text = "\n".join(f"<@{m.get('user')}>: {m.get('text', '')[:600]}" for m in replies)
        try:
            summary = ai.generate(text, system="Summarise this standup in at most 8 bullets. "
                                  "List blockers first, keep the <@id> mentions.", max_output_tokens=400).text
        except ai.AIError:
            summary = f"{len(replies)} updates in the thread."
    if missing:
        summary += "\nNot heard from: " + " ".join(f"<@{u}>" for u in missing)
    slack.chat_postMessage(channel=CHANNEL, thread_ts=thread["ts"], text=summary)
    return {"replies": len(replies), "missing": len(missing)}
```

- One automation, two schedule times (9:30 and 12:00). The hour decides which step runs.
- The morning step stores today's thread timestamp; the noon step reads it, so the summary is always for today's thread.
- Channel and member ids come from a one-time discovery script the assistant runs with your Slack connection.

## A schedule, not a trigger link

Use a schedule with two times on weekdays. The script decides which step to do.

To summarise as soon as everyone has replied, add a trigger link for Slack's event subscriptions; the noon run stays as a fallback.

## Limits

- The Slack account needs to be in the channel and allowed to read its history.
- Very long threads are trimmed to 600 characters per reply before the AI step.
- AI tokens count toward the workspace's monthly allowance.

## Troubleshooting

### The run fails with not_in_channel.

Invite the connected Slack app to #team, then run the automation now.

### The summary says no thread today.

The morning run didn't post, or ran after 11:00. Check the morning run in the ClickRuntime dashboard and the schedule's timezone.

### It lists people who replied as missing.

Their Slack ids in TEAM are wrong. Ask the assistant to look them up again with a discovery script.

## Related

- [Slack automations](https://clickruntime.com/apps/slack)
- [Linear automations](https://clickruntime.com/apps/linear)
- [Jira automations](https://clickruntime.com/apps/jira)
- [GitHub automations](https://clickruntime.com/apps/github)
- [daily-standup-collector](https://clickruntime.com/templates/daily-standup-collector)
- [async-standup-bot](https://clickruntime.com/templates/async-standup-bot)
- [daily-standup-project-status-digest-to-slack](https://clickruntime.com/templates/daily-standup-project-status-digest-to-slack)
- [Slack channel summary](https://clickruntime.com/use-cases/summarise-slack-channel)
- [Stale pull request reminders](https://clickruntime.com/use-cases/stale-pull-request-reminders)
- [Daily Slack message](https://clickruntime.com/use-cases/daily-slack-message)
- [Assistant scheduled tasks alternative](https://clickruntime.com/alternatives/chatgpt-claude-scheduled-tasks)
- [Zapier alternative](https://clickruntime.com/alternatives/zapier)
- [Docs: state](https://clickruntime.com/docs/state)
- [Docs: connections-and-secrets](https://clickruntime.com/docs/connections-and-secrets)

## Extend it: what you can add next

The first version is rarely the last. Because the automation is a Python script with memory, AI and any API available, you grow it by asking your assistant for the change. Each change is a new version, and a failed deploy never replaces the working one.

- **Add each person's Linear issues in progress to the summary** (Any app or API)
  Prompt: "Change my async standup so the summary also lists each person's Linear issues that are in progress."
- **Turn blockers into a short action list with owners** (Built-in AI)
  Prompt: "Change my async standup so the noon summary ends with an action list: one line per blocker with who should help."
- **Track blockers that repeat across days** (Memory between runs)
  Prompt: "Change my async standup so it remembers blockers and flags any that appear three days in a row."
- **A Friday weekly recap built from the five daily summaries** (Schedules)
  Prompt: "Add to my async standup: every Friday at 16:00, post a weekly recap in #team built from this week's summaries."
- **Skip people on leave, using a Google Calendar** (Multi-step logic)
  Prompt: "Change my async standup so people with an out-of-office event in our Team calendar today aren't listed as missing."
- **Save each day's summary to a Notion page** (Any app or API)
  Prompt: "Add to my async standup: also save each day's summary as a new page in our Standups database in Notion."
- **Let people reply by form instead of Slack** (Trigger links)
  Prompt: "Add a trigger link to my async standup that accepts updates from a form, and include them in the noon summary."

## Questions

### Can people answer in a thread instead of a form?

Yes. The morning post starts a thread, people reply in it, and the summary run reads the thread replies through the connected Slack account before posting the roll-up.

### Can ChatGPT run a standup in Slack?

With ClickRuntime connected, ChatGPT can set up an automation that posts the standup question and summarises replies on a weekday schedule, without anyone opening a chat.

### Do I need a standup bot subscription?

No. The automation uses your own Slack connection and ClickRuntime's built-in AI. A standup is two runs per weekday.

### Can it skip holidays?

Yes. Pause it, or ask the assistant to skip public holidays or people with an out-of-office event.

### Does it work with Microsoft Teams?

Yes, through Microsoft Graph with your own Microsoft OAuth app added in the ClickRuntime dashboard.
