Catch up on a busy Slack channel in one daily summary
Pick the channel and when you want the summary. Each day ClickRuntime reads the new messages, has AI pull out decisions, questions and action items, and posts the summary where you'll see it.
- When
- Weekdays at 17:30 (America/Chicago)
- Uses
- Slack #product, Slack #product-digest
- Tue 17:30✓ #product daily digest · SucceededLast runTue 17:30 · 142 messages
Can ChatGPT or Claude summarise a Slack channel for me every day?
They can summarise messages you paste in, but they won't read your channel every evening by themselves. With ClickRuntime connected, your assistant sets up an automation that reads the day's messages with your Slack connection, summarises them with the built-in AI, and posts the summary to a channel or emails it to you.
Why the assistant can’t do this on its own
- Reading a channel needs a Slack connection with read access that keeps working after the chat.
- A daily summary needs a schedule and a record of where the last summary stopped, so nothing is summarised twice.
- Summarising long threads is what AI is good at; the fetching, cutting and posting is plain code.
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: 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.” 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 keysReading needs a Slack account connected in the ClickRuntime dashboard (the workspace's own Slack app) with permission to read channel history; the assistant gives you the button. Posting the summary uses the notifications Slack.
- Step 5Test itThe assistant runs it once for today so you see the summary, then tunes the format with you.
- 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 dashboardEach run shows how many messages were read and that the summary was posted. State holds the timestamp of the last message summarised.
“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.”
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.
- Reading uses your connected Slack account through slack_sdk; posting uses notify.slack.
- Bot messages are skipped and long messages are cut before they reach the AI.
- The last message's timestamp is kept in state, so tomorrow's summary starts where today's stopped.
A schedule, not a trigger link
A daily schedule at the end of the working day, or first thing in the morning for the day before.
Limits
- Private channels are readable only if the connected Slack account is a member.
- Each AI call takes about 32,000 input tokens; very busy channels are trimmed to fit, or summarised in two parts.
- Only the channels you name are read.
Troubleshooting
It fails with not_in_channel or missing_scope.
The connected Slack account can't read that channel. Join the channel, or reconnect Slack with history access in the ClickRuntime dashboard.
The summary misses thread replies.
Ask the assistant to include threads; it fetches replies for messages that have them.
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.
- Multi-step logic
Summarise several channels in one digest, one section each
“Change my Slack digest so it also covers #design and #support, with one section per channel.”
- Any app or API
Create Linear issues for each action item
“Add to my Slack digest: create a Linear issue for each action item, assigned to its owner when the name matches.”
- Any app or API
Archive each day's summary to a Notion page
“Add to my Slack digest: add each day's summary to my Notion database Channel notes.”
- Built-in AI
Flag messages that mention you and still have no answer
“Change my Slack digest so it lists questions addressed to me that nobody answered.”
- Schedules
A weekly version for people who only check on Fridays
“Add to my Slack digest: every Friday at 16:00, post a summary of the whole week to #product-digest.”
- Memory between runs
Track how many decisions and open questions there are each week
“Add to my Slack digest: count decisions and open questions each day, and show the week's totals on Fridays.”
Questions about slack channel summary
Can ChatGPT summarise Slack channels automatically?
With ClickRuntime connected, yes. ChatGPT sets up an automation that reads the channel each day and posts an AI summary.
Can Claude read my Slack and summarise it daily?
Yes, through ClickRuntime, using a Slack account you connect in the ClickRuntime dashboard.
Does it read all my channels?
No. Only the channels named in the automation, and only those the connected account can see.
Do I need an AI API key?
No. The summary uses ClickRuntime's built-in AI, including on the free plan.
What can I add later?
More channels, Linear issues for action items, a Notion archive or a weekly version. See Extend it.
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 →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 →Daily standup in Slack
“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.”
See the use case →
Set up your first automation in ChatGPT or Claude
Free plan. No credit card.