Run an async daily standup in Slack, set up from your assistant
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.
- When
- Weekdays 9:30 and 12:00
- Uses
- Slack
- 12:00✓ Async standup · SucceededLast run12:00 · 7 replies, 1 blocker
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
The same steps work in ChatGPT, Claude, Cursor and any assistant that supports MCP connectors.
- Step 1Connect ClickRuntime to your assistantAdd 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.
- Step 2Paste the promptStart 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.
- Step 3Read the draftThe 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.
- Step 4Connect accounts and save keysThe 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.
- Step 5Test itThe 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.
- Step 6Turn it onThe 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.
- Step 7Check it in the ClickRuntime dashboardTwo 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.
“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.”
Connector setup for each assistant: ChatGPT, Claude, Claude Code, Cursor, and other assistants.
What the assistant writes
A typical script for this job. Yours matches your pages, accounts and wording, and you can read every version in the ClickRuntime dashboard.
- 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.
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.
- Any app or API
Add each person's Linear issues in progress to the summary
“Change my async standup so the summary also lists each person's Linear issues that are in progress.”
- Built-in AI
Turn blockers into a short action list with owners
“Change my async standup so the noon summary ends with an action list: one line per blocker with who should help.”
- Memory between runs
Track blockers that repeat across days
“Change my async standup so it remembers blockers and flags any that appear three days in a row.”
- Schedules
A Friday weekly recap built from the five daily summaries
“Add to my async standup: every Friday at 16:00, post a weekly recap in #team built from this week's summaries.”
- Multi-step logic
Skip people on leave, using a Google Calendar
“Change my async standup so people with an out-of-office event in our Team calendar today aren't listed as missing.”
- Any app or API
Save each day's summary to a Notion page
“Add to my async standup: also save each day's summary as a new page in our Standups database in Notion.”
- Trigger links
Let people reply by form instead of Slack
“Add a trigger link to my async standup that accepts updates from a form, and include them in the noon summary.”
Questions about daily standup in slack
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.
Other use cases
Scheduled tasks in ChatGPT and Claude
“Create a ClickRuntime automation: every weekday at 9, fetch yesterday's orders from our Shopify store and post the total to #sales in Slack.”
See the use case →Run code every hour
“Create a ClickRuntime automation: every hour, check our public API's /health endpoint and Slack #alerts if it returns anything but 200.”
See the use case →Webhook automation
“Create a ClickRuntime automation: when someone submits our Typeform, add their answers to a message in #leads.”
See the use case →Cron jobs without a server
“Create a ClickRuntime automation: every night at 2am UTC, call POST https://api.example.com/tasks/reindex with my ADMIN_TOKEN and email me if it doesn't return 200.”
See the use case →AI agent automations
“Create a ClickRuntime automation: every morning at 8, summarize new GitHub issues labelled 'bug' on our repo and post them to #eng.”
See the use case →Monitoring and alerts
“Create a ClickRuntime automation: every 5 minutes, check https://api.example.com/health and Slack #oncall if it fails twice in a row.”
See the use case →Stateful automations
“Create a ClickRuntime automation: every hour, check this product page and email me only when the price drops below the lowest price you've seen.”
See the use case →AI triage and summaries
“Create a ClickRuntime automation: every 15 minutes, label new support emails as billing, bug or other and post billing ones to #billing.”
See the use case →Website change alerts
“Create a ClickRuntime automation: every hour, check https://acme.com/pricing. Only look at the pricing table, not the whole page. When it changes, email me a short summary of what changed. Don't email me when nothing changed.”
See the use case →Price drop alerts
“Create a ClickRuntime automation: every 2 hours, check the price on https://shop.example.com/products/monitor-27. Email me when it drops below $280. Tell me only once per drop, and include the lowest price seen so far.”
See the use case →Uptime checks
“Create a ClickRuntime automation: every 5 minutes, check https://app.example.com/health. It's down if the status isn't 200, it takes longer than 5 seconds, or the body doesn't contain "ok". After 2 failures in a row post to #ops in Slack, and post again when it's back up with how long it was down.”
See the use case →RSS feed alerts
“Create a ClickRuntime automation: every 30 minutes, check https://www.postgresql.org/news.rss. Post each new item to #eng in Slack with its title, link and a one-line summary. Never post the same item twice. On the first run, don't post old items.”
See the use case →Job post alerts
“Create a ClickRuntime automation: every 2 hours, check the Greenhouse job boards for the companies acme and betaco. Email me new jobs that are product design roles open to remote work in Europe. Include title, location and link. Never send the same job twice.”
See the use case →Brand mention alerts
“Create a ClickRuntime automation: every 30 minutes, search Reddit and Hacker News for "Acme CRM". Post each new mention to #mentions in Slack with the title, link and a label: question, complaint, praise or other. Never post the same thread twice.”
See the use case →Daily Slack message
“Create a ClickRuntime automation: every weekday at 9:00 Europe/Berlin, post to #team in Slack: a good-morning line, the number of open issues labelled Bug in our Linear team ENG, and the 3 oldest ones with links.”
See the use case →Daily news digest
“Create a ClickRuntime automation: every day at 7:30 Europe/London, collect new items from these feeds: <feed URLs>. Pick the 5 most important for someone following AI policy in the EU, and email me a digest with a two-sentence summary and link for each. Don't include anything I was sent before.”
See the use case →Weekly metrics to Google Sheets
“Create a ClickRuntime automation: every Monday at 7:00 America/New_York, add a row to the KPIs tab of my sheet “Company metrics” with the week start date, last week's Stripe revenue (succeeded charges minus refunds), number of new customers and number of refunds.”
See the use case →Morning briefing
“Create a ClickRuntime automation: every weekday at 7:00 Europe/Lisbon, read today's events from my work Google Calendar, get today's forecast for Lisbon, and email me a short briefing: the weather in one line, each meeting with time and who's in it, what I should prepare, and my free blocks of 30 minutes or more.”
See the use case →Slack channel summary
“Create a ClickRuntime automation: every weekday at 17:30 America/Chicago, read today's messages and thread replies in #product, and post to #product-digest a summary with three parts: decisions made, open questions, and action items with who owns them.”
See the use case →Inbox summary each morning
“Create a ClickRuntime automation: every weekday at 7:30 America/Los_Angeles, read the emails that arrived in my Gmail inbox since the last summary. Email me a summary in three groups: needs a reply, FYI, and newsletters or notifications. One line per email with the sender. Skip anything I already read.”
See the use case →Form submissions to Google Sheets
“Create a ClickRuntime automation: when someone submits my Typeform contact form, add a row to the Leads tab of my Leads spreadsheet with the date, name, email, company and message. Check the Typeform signature so only real submissions are added.”
See the use case →Form leads to your CRM
“Create a ClickRuntime automation: when my website form posts a lead (name, email, company, message), create or update the contact in HubSpot by email, set lifecycle stage to lead, and add the message as a note on the contact.”
See the use case →Handle Stripe webhooks
“Create a ClickRuntime automation: when Stripe sends checkout.session.completed, post the customer email and amount to #sales in Slack. Check the Stripe signature and handle each event only once.”
See the use case →React to GitHub events
“Create a ClickRuntime automation: when a new issue is opened in acme/app, read the title and body and add one label: bug, feature or question. Check GitHub's webhook signature.”
See the use case →Sort Gmail automatically
“Create a ClickRuntime automation: every 15 minutes, look at new messages in my Gmail inbox and add one label: Invoice, Customer, Newsletter or Needs reply. Email me straight away when a customer message sounds urgent.”
See the use case →Recurring reminders
“Create a ClickRuntime automation: on the last weekday of every month at 10:00 London time, post “Reminder: send this month's invoices” to #finance in Slack.”
See the use case →Stale pull request reminders
“Create a ClickRuntime automation: every weekday at 9:30 Berlin time, find pull requests in acme/app and acme/api that are not drafts, have been open more than 24 hours and have no review yet. Post them to #eng in Slack with the title, age, author and requested reviewers. Post nothing if there are none.”
See the use case →Scheduled social posts
“Create a ClickRuntime automation: every 15 minutes, read my Post queue sheet (columns: When, Text, Status). Publish each row whose When has passed and whose Status is empty to my LinkedIn profile, then set Status to the post link.”
See the use case →Sync data between apps
“Create a ClickRuntime automation: every 30 minutes, find records in my Airtable Customers table that changed since the last run, and create or update the HubSpot contact with the same email, copying name, company and plan.”
See the use case →Summarise customer feedback
“Create a ClickRuntime automation: every Monday at 9:00, read the rows added to my Feedback sheet since last time (columns: Date, Source, Text), group them into up to 6 themes with a count and one short quote each, and post it to #product in Slack.”
See the use case →
Set up your first automation in ChatGPT or Claude
Free plan. No credit card.