Twice a day

Run your daily standup in Slack

Everyone gets asked for their update in the morning, and the team gets a summary with blockers by lunchtime.

Runs: Twice a day
Apps: Slack
AI: Yes, uses the built-in AI allowance
Access: chat:write, channels:history

Send this to your assistant

Create a ClickRuntime automation: at 9am on weekdays, ask for standup updates in #team. At 11am, summarise everyone's replies and call out any blockers.

Paste it into your assistant. It tells you what it will send or change before it runs live.

Add to ChatGPT Add to Claude

First time? Adding ClickRuntime to your assistant takes about two minutes.

Why use it

Why teams use this automation

Daily standups across time zones are hard to schedule. A team in Berlin, Austin and Bangalore cannot meet at once, so someone posts "what are you working on?" in a channel and then spends the morning chasing replies. Answers arrive scattered in threads, the manager copies them into a doc, and anyone who joins late has to read forty messages to learn that the API migration is blocked. The meeting is cancelled, and the information goes with it.

Twice a day, ClickRuntime posts your standup prompt to the channel and notes the message timestamp. Later it reads the replies in that thread, uses its built-in AI to turn them into a short summary of progress, plans and blockers per person, and posts the summary back to the channel. Replies stay in the thread; the summary sits where everyone looks.

It is most useful for remote or hybrid teams of five to fifteen people where a live meeting would not fit everyone.

What you get out of it

Time zones stop mattering
People answer when their day starts, and the summary arrives once the replies are in. Nobody has to join a call at 6 a.m. or 10 p.m. to keep the team informed.
Blockers rise to the top
A one-line mention of waiting on design review is easy to lose in thread replies. A summary that lists blockers separately helps the manager see which people need help before the day is lost.
Managers stop doing the chasing
The prompt goes out on schedule and replies are collected for them. A lead gets back the time they used to spend nudging individuals and pasting updates into a document.
Late joiners catch up in a minute
Someone returning from leave or joining mid-sprint can read one summary message to learn what the team has done and plans next, instead of scrolling a long thread and guessing which replies still apply.
A running record exists
Because each summary is posted in the channel, a search for a feature name shows when work started, who touched it and when it got stuck, which is handy for retrospectives and performance reviews.

How it works

What happens, step by step

Every weekday at 9am ClickRuntime posts the standup question in your team's Slack channel.
Team members reply in the thread with what they did, what's next and any blockers.
At 11am it reads the replies and AI writes a short summary: one line per person, plus a list of blockers.
The summary is posted back in the channel so everyone sees the day's plan at a glance.

Before it runs live

Connect Slack, then invite the app to the channel (type /invite @ClickRuntime there)

What you get

RunsTwice a day

Run your daily standup in Slacktoday, 9:00Succeeded

Slack · #team• Sam: finished Acme export, starting invoices • Riya: on Northwind migration Blockers: Riya waiting on staging DB access

Build your own

Need it to work differently?

This template is a starting point. Copy the prompt and change it, or describe a different automation from scratch, with your own conditions, more apps or an AI step. Your assistant writes it, tests it and runs it on ClickRuntime.

Your own rules
Conditions, thresholds, filters and exceptions, written the way you'd explain them to a colleague.
Any number of apps
One automation can read from one app and update several others. Over 248 apps are ready, and anything with an API works too.
AI where it helps
Summaries, classification, extraction and drafts use ClickRuntime's built-in AI, with no extra key.
On a schedule or on each event
Runs as often as every 5 minutes, or the moment an app sends an event, and keeps track of what it already handled.

Changes you can ask for

Run it at a different time, more or less often, or only on weekdays
Change what the AI looks for, or how it writes the result
Add another app, for example also send it to Google Sheets
Combine it with other Slack steps into one automation

Under the hood

The code that runs this automation

This is the Python script that runs each time the automation starts. Your AI assistant writes it for you when you send the prompt, and you allow each step in your assistant. To change how the automation works, describe the change to your assistant and it updates the script for you. For every function it can use, see the script reference.

daily_standup_collector.pyexample

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

TEAM = "C01TEAM000"
TZ = ZoneInfo("America/New_York")

@on_trigger
def run(event):
    slack = WebClient(token=credentials.connection("slack", "work"))
    local = datetime.fromisoformat(event.scheduled_time.replace("Z", "+00:00")).astimezone(TZ)
    if local.hour < 10:  # the 9am run asks, the 11am run summarises
        msg = slack.chat_postMessage(channel=TEAM, text="Standup: what did you do yesterday, what's next, any blockers? Reply in the thread.")
        state.set("standup_ts", msg["ts"])
        return {"asked": True}
    replies = slack.conversations_replies(channel=TEAM, ts=state.get("standup_ts"))["messages"][1:]
    text = "\n".join(f"<@{r['user']}>: {r['text'][:500]}" for r in replies)
    summary = ai.generate(
        "Summarise these standup replies in short bullets per person and list blockers separately:\n" + text,
        max_output_tokens=600,
    ).text
    slack.chat_postMessage(channel=TEAM, thread_ts=state.get("standup_ts"), text=summary, reply_broadcast=True)
    return {"replies": len(replies)}

FAQ

Common questions

What time are the two prompts sent?

You choose both times, for example a morning prompt for plans and an end-of-day prompt for results. Each run records its own message, so replies to the morning prompt are not mixed with answers collected later.

What if someone forgets to reply?

The summary covers the people who answered. If you want, it can also list team members who did not respond, so a manager can follow up quietly without posting a public reminder in the channel.

Can replies be in any format?

Yes. People write plain sentences, bullet points or a few words, and the AI reads them all. It works best when replies mention what was done, what is next and anything blocking, but no template is required.

What permissions does it need?

chat:write, channels:history. Nothing else in your accounts is used.

Does it need AI?

Yes. It uses ClickRuntime's built-in AI, so you don't need an OpenAI or Anthropic key. Every plan includes a monthly AI allowance.

How many runs does it use?

One run each time it runs (twice a day). Checks that find nothing to do and stop right away aren't counted.

Can I change how it works?

Yes. Describe the change to your AI assistant, for example a different schedule, channel or filter. It updates the automation, tests it and tells you what changed.

DailyAI