Weekly

Get a weekly summary of what your team discussed

Every Friday you get one email with what was decided, who worked on what, and what's still open across your busiest channels.

Runs: Weekly
Apps: Slack
AI: Yes, uses the built-in AI allowance
Access: channels:history, users:read, chat:write

Send this to your assistant

Create a ClickRuntime automation: every Friday at 4pm, read this week's messages in #team and #project, summarise the decisions, open questions and what each person worked on, and email it to me.

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

A manager with six direct reports and eight active channels cannot read everything. By Friday, the picture of the week is hazy: who closed the customer issue, which decision about pricing was made in a thread on Tuesday, who spent three days on a task that nobody else knew about. Performance conversations and weekly updates to leadership are written from memory, and people who did quiet, valuable work are remembered less than people who posted a lot.

Every Friday, ClickRuntime gathers the week's messages and thread replies from the channels you choose, resolves user IDs into real names, and uses its built-in AI to write a summary per person of what they worked on and which decisions were made. The report goes to you by email or into a channel.

Team leads, chiefs of staff and founders who need a regular written record without sitting in every conversation will find it most useful.

What you get out of it

Weekly updates take minutes to write
The summary gives a manager a draft to edit instead of a blank page, and the facts in it come from what people actually said in channels, not from a hurried recollection on Friday evening.
Decisions are captured with their context
Choices made in threads are easy to lose. A summary that lists decisions with who made them gives the team a written trail and reduces later debates about what was agreed.
Quiet contributors get seen
Someone who handles hard problems in a few precise messages is easy to overlook next to a prolific poster. A summary by person gives each contributor space in the review. Reviews end up fairer, and engineers who prefer written work get due credit.
Leadership gets visibility without meetings
A weekly written digest replaces a recurring status call. Executives read the highlights in five minutes and ask follow-up questions only where they need to. That frees an hour or two of calendar time each week for everyone involved.
Review season starts with material
When it is time for mid-year or annual reviews, a manager has dozens of dated weekly summaries to draw from, so feedback rests on specifics rather than the last month.

How it works

What happens, step by step

Once a week ClickRuntime reads the past seven days of messages in the Slack channels you picked.
It replaces user IDs with people's real names so the summary makes sense.
AI writes a short report of the decisions made, open questions and who is working on what.
The report is emailed to you, so you can catch up in a couple of minutes.

Before it runs live

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

What you get

RunsWeekly

Get a weekly summary of what your team discussedtoday, 9:00Succeeded

Email · Weekly summary: #team and #projectDecisions: ship the Acme onboarding flow on 3 Nov; drop the CSV import. Open: who owns the Northwind renewal deck?

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.

weekly_ai_summary_of_channel_activity.pyexample

import time
from slack_sdk import WebClient
from clickruntime import on_trigger, credentials, ai, notify

CHANNELS = {"C01TEAM000": "#team", "C02PROJECT0": "#project"}

@on_trigger
def run(event):
    slack = WebClient(token=credentials.connection("slack", "work"))
    since = str(time.time() - 7 * 86400)
    names, lines = {}, []
    for cid, label in CHANNELS.items():
        for m in slack.conversations_history(channel=cid, oldest=since, limit=500)["messages"]:
            uid = m.get("user")
            if uid and uid not in names:
                names[uid] = slack.users_info(user=uid)["user"]["real_name"]
            lines.append(f"{label} {names.get(uid, 'bot')}: {m.get('text', '')[:300]}")
    summary = ai.generate(
        "Summarise this week's Slack messages: decisions, open questions, and what each person worked on.\n"
        + "\n".join(lines[:400]),
        max_output_tokens=1000,
    ).text
    notify.email_me("Weekly summary: #team and #project", summary)
    return {"messages": len(lines)}

FAQ

Common questions

Which channels and people are included?

You choose the channels, and anyone who posted in them during the week appears. You can narrow it to your own team by listing specific people. Private channels are only included where the Slack bot has been invited.

Can the AI get things wrong?

Yes. It summarizes text, so it can miss nuance or misread sarcasm. Treat the output as a starting draft for a manager to check, and use the links to the original threads whenever a detail matters.

Who can see the summary?

Only the recipients you set. Emailing it to yourself keeps it private, while posting to a channel makes it visible to that channel. Because it describes individuals' work, think about the audience before choosing a shared place.

What permissions does it need?

channels:history, users:read, chat:write. 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 (weekly). 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