Collects as they arrive, acts daily

Get a Friday round-up of Storyblok activity

Each Friday you get one email grouping the stories published and changed during the week.

Runs: Collects as they arrive, acts daily
Apps: Storyblok
AI: Not needed
Access: read

Send this to your assistant

Create a ClickRuntime automation: collect every Storyblok publish event this week and email me a digest on Friday at 4pm, grouped by folder.

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

The head of content at a company with six Storyblok editors gets asked every Friday what actually changed on the site this week. To answer, they open the space, sort by updated date and scroll, trying to separate real publishes from small edits. It takes the better part of an hour, and the answer is usually incomplete.

Throughout the week, ClickRuntime receives Storyblok events as they happen and stores a compact record of each published or changed story. On Friday it groups the records into one email: stories published, stories updated, and who touched what, so the week is summarized in a single scan. A single grouped email replaces the manual hunt through the space.

It is aimed at managers, agencies and editorial leads who report on content output but do not want to compile the list manually.

What you get out of it

Friday reporting takes minutes, not an hour
The list is already assembled when you sit down. You read, add a line of context and forward it, rather than reconstructing the week from the space's activity view. That hour goes back to planning the next week's stories.
Output becomes visible to leadership
A grouped list of published stories gives executives a concrete view of what the content team delivered. That helps justify headcount and shows when a slow week really was slow.
Late changes to live pages are not missed
Updates to already published stories are listed separately from new ones. A pricing tweak made on Wednesday shows up in the digest instead of being buried among new pages. Readers see at once which live pages were touched after launch.
Agencies can show clients real work
For client spaces, the digest doubles as a weekly activity record. It supports invoices and status calls with specifics rather than a general claim that edits were made. Clients and managers see evidence instead of promises.
A steady record for retrospectives
Stored digests let you compare weeks, spot editors who go quiet and see which launches clustered together. Planning becomes easier when the history is written down. Over a quarter, the pattern is hard to argue with.

How it works

What happens, step by step

Each time a story is published in Storyblok during the week, ClickRuntime notes it.
On Friday afternoon it groups the stories by the folder they live in, such as blog or docs.
You get one email with the number of publishes this week and the grouped list.
The list is then cleared for the next week.

Before it runs live

Connect Storyblok
Paste your automation's link into the other app's webhook settings

What you get

RunsCollects as they arrive, acts daily

Get a Friday round-up of Storyblok activitytoday, 9:00Succeeded

Email · Storyblok weeklyStoryblok: 9 publishes this week blog/ • acme-launch-recap • northwind-case-study docs/ • getting-started

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

Act only on the items that match your own rules, and skip the rest
Add an AI step, for example to summarize, sort or draft a reply
Add another app, for example also send it to Slack
Combine it with other Storyblok 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_content_activity_digest.pyexample

from collections import defaultdict
from clickruntime import on_event, on_trigger, state, notify

@on_event
def handle(event):
    body = event.json or {}
    if body.get("action") == "published":
        items = state.get("published") or []
        items.append(body.get("full_slug") or str(body.get("story_id")))
        state.set("published", items)
    return {"ok": True}

@on_trigger
def run(event):  # Friday 4pm
    by_folder = defaultdict(list)
    for slug in state.get("published") or []:
        folder, _, name = slug.rpartition("/")
        by_folder[folder or "(root)"].append(name)
    text = "\n\n".join(f"{folder}/\n" + "\n".join(f"  • {n}" for n in names) for folder, names in sorted(by_folder.items()))
    notify.email_me(f"Storyblok: {sum(map(len, by_folder.values()))} publishes this week", text or "Nothing published this week.")
    state.delete("published")
    return {"folders": len(by_folder)}

FAQ

Common questions

Why does it collect events through the week instead of querying on Friday?

Storing each event as it arrives preserves what happened even if a story is later edited again or unpublished. A Friday query would only show the current state, which can hide earlier publishes and changes.

Does the digest show which editor made each change?

It includes whatever Storyblok sends in the event, which is the story, the action and the time. Author details are available when the payload or a follow-up fetch provides them, and can be added to the grouped list.

What if nothing was published this week?

You still get an email that says no stories were published or changed, so silence is confirmation rather than a question mark. If you prefer to skip empty weeks, say so and the send is skipped.

What permissions does it need?

read. Nothing else in your accounts is used.

Does it need AI?

No. It runs without AI, so it doesn't use your plan's AI allowance.

How many runs does it use?

One run each time it checks. Checks that find nothing new 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.

The moment it happens