Weekly

Get a weekly summary of what changed in your docs

On Fridays you read a few lines per page explaining what was added or changed, instead of opening each one.

Runs: Weekly
Apps: Confluence
AI: Yes, uses the built-in AI allowance
Access: read

Send this to your assistant

Create a ClickRuntime automation: every Friday, summarise in two sentences each the Confluence pages created or edited this week in space DOCS, up to 20 pages, and email me the summary.

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

Managers and leads cannot read every page edit in their documentation, but they still need to know what shifted. A pricing page was rewritten, a security process changed, a roadmap was updated. A simple list of titles shows that something happened, but not what.

Every Friday, this finds the pages modified in the last seven days, fetches their content, has ClickRuntime's built-in AI write a short plain-language summary of each page, and emails you the result. No separate AI key is needed, and you read what changed rather than just the titles.

It is useful for team leads, product managers and executives who want to stay informed about documentation without opening each page. Each summary is written by ClickRuntime's built-in AI from the page as it stands now, so no separate AI account is needed and the email reads like a brief from a colleague.

What you get out of it

Understand changes in a few lines
A short summary tells you whether an edit was a typo fix or a substantive policy change. You can decide which pages deserve a full read. A one or two line summary shows whether an edit was a typo or a real change, so you read the full page only when needed.
Stay informed without reading every page
A weekly summary compresses dozens of edits into a few minutes of reading. Leaders keep a reliable picture of what is happening in the docs. A week of edits across a busy space becomes a few minutes of reading, and leaders keep an accurate picture of the documentation.
Spot important changes quickly
An edit that alters a process or a commitment stands out in plain language. You can follow up before the change spreads into practice. A change to a process or a commitment stands out in plain words, and you can ask about it before it becomes habit.
Help the wider team keep up
The email can be shared with people outside the space. Colleagues in sales or support get a readable account of changes affecting them. The email can be passed to colleagues in sales or support, who get a readable account of changes that affect their work.
Create a Friday record of the week
The emails build a narrative of how documentation evolved. During planning or retrospectives, they remind you what actually changed. Over months the Friday emails build a narrative of how the documentation evolved, which is useful in planning and retrospectives.

How it works

What happens, step by step

Once a week, ClickRuntime finds the Confluence pages changed in the past seven days.
It reads the current content of each page.
AI writes a short summary of what each page now says.
You get one email with a summary for every changed page.

Before it runs live

Connect Confluence

What you get

RunsWeekly

Get a weekly summary of what changed in your docstoday, 9:00Succeeded

Email · DOCS this week: 6 pagesRefund policy Refunds now go back to the original card within 5 days. Store credit is offered only on request.

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 Slack
Combine it with other Confluence 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_what_changed.pyexample

import re
from clickruntime import on_trigger, notify, http, credentials, ai

SITE = "https://northwind.atlassian.net"

@on_trigger
def run(event):
    auth = (credentials.secret("CONFLUENCE_EMAIL"), credentials.secret("CONFLUENCE_API_TOKEN"))
    pages = http.get(f"{SITE}/wiki/rest/api/search", auth=auth, params={
        "cql": 'space = DOCS and type = page and lastmodified >= now("-7d")', "limit": 20,
    }).json()["results"]
    summaries = []
    for r in pages:
        page_id = r["content"]["id"]
        body = http.get(f"{SITE}/wiki/api/v2/pages/{page_id}", auth=auth, params={"body-format": "storage"}).json()["body"]["storage"]["value"]
        text = re.sub(r"<[^>]+>", " ", body)[:3000]
        summary = ai.generate(f"Summarise this Confluence page in two sentences.\n\n{text}", max_output_tokens=120).text.strip()
        summaries.append(f"{r['content']['title']}\n{summary}\n{SITE}/wiki{r['content']['_links']['webui']}")
    notify.email_me(f"DOCS this week: {len(summaries)} pages", "\n\n".join(summaries) or "No pages changed in DOCS this week.")
    return {"pages": len(summaries)}

FAQ

Common questions

How accurate are the summaries?

They are generated by AI from the page text, so they can miss nuance. Treat them as a guide to what changed and follow the link to the page when the details matter. Summaries come from an AI reading the page text, so they can miss nuance, and the link in each entry leads to the full page.

Does it summarise the whole page or only the edit?

It summarises the current content of each changed page, not a diff. Comparing revisions is still done in Confluence, where version history shows exactly what changed. The summary describes the current page content and not a diff, and Confluence's version history shows the exact line changes.

Which pages are included?

Pages modified in the last seven days across the spaces the account can see. Tell your AI assistant to restrict it to particular spaces or labels if you want a narrower report. Any space or label can be used to narrow the report.

What permissions does it need?

read. 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.

On a schedule