Collects as they arrive, acts daily

Get all project updates in one weekly email

Once a week you get every project update and each project's health in a single summary.

Runs: Collects as they arrive, acts daily
Apps: Linear
AI: Yes, uses the built-in AI allowance
Access: read

Send this to your assistant

Create a ClickRuntime automation: collect Linear project updates as they're posted, and every Friday at 4pm email me a summary per project with its latest health.

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 head of product or an executive sponsor who oversees six or eight Linear projects cannot read every project update as it is posted. The updates are valuable, with their on track, at risk or off track health markers, but they are scattered across projects and appear at random times. Leadership ends up asking for status in meetings, which costs the people doing the work time they would rather use for building.

ClickRuntime stores each project update as it arrives. On Friday it asks its built-in AI to write a short summary for each project, noting its health and the main points, and emails you one digest covering all of them. The stored updates are then cleared, so next week's digest starts fresh.

It is useful for program managers, directors and sponsors who need an overview without joining every check-in.

What you get out of it

Status meetings can shrink
When leadership has read a clear summary of every project, the meeting can focus on blockers and decisions. Fewer people spend an hour listening to progress they could have read in five minutes.
At-risk projects are not buried
The digest shows project health beside each summary. A project that slipped to off track gets noticed in the same read as the ones that are fine, instead of hiding in a feed.
Project leads write once
Leads already post updates in Linear. Because the digest reuses those posts, nobody has to write a separate status report for managers or stakeholders. That removes a duplicate task from the project lead's week.
Weekly rhythm builds accountability
An email that goes out every Friday encourages teams to post their updates before then. Projects that go quiet become visible when their section is empty. Silence becomes a signal instead of a blind spot.
Stakeholders outside engineering stay informed
Sales, support and finance often want to know when a feature will ship. A readable summary written in plain language answers that without exposing them to the details of tickets.

How it works

What happens, step by step

Whenever someone posts a project update in Linear, ClickRuntime saves it.
On Friday, AI reads the week's updates and writes a short summary for each project, including its health, such as on track or at risk.
You get one email with every project summarised in a line or two.
The saved updates are then cleared, ready for next week.

Before it runs live

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

What you get

RunsCollects as they arrive, acts daily

Get all project updates in one weekly emailtoday, 9:00Succeeded

Email · Project updatesBilling v2 (onTrack): invoices API done, migration starts Monday. Mobile app (atRisk): App Store review delayed a week.

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

project_update_digest.pyexample

from clickruntime import on_event, on_trigger, state, ai, notify

@on_event
def collect(event):
    body = event.json or {}
    if body.get("type") != "ProjectUpdate":
        return {"stored": False}
    u = body.get("data", {})
    updates = state.get("updates") or []
    updates.append({"project": (u.get("project") or {}).get("name"), "health": u.get("health"), "body": (u.get("body") or "")[:1500]})
    state.set("updates", updates)
    return {"stored": True}

@on_trigger
def digest(event):
    updates = state.get("updates") or []
    if not updates:
        return {"projects": 0}
    text = "\n\n".join(f"{u['project']} ({u['health']}): {u['body']}" for u in updates)
    summary = ai.generate(f"Summarise each project in 2 lines, ending with its latest health:\n{text}", max_output_tokens=600).text
    notify.email_me("Project updates this week", summary)
    state.set("updates", [])
    return {"updates": len(updates)}

FAQ

Common questions

What if a project has no update that week?

Its section says there were no updates this week, so silence is visible. That is often the most useful part of the digest, since a project that stopped reporting may be in trouble. Projects can also be excluded if you do not want them listed.

How does the AI decide what goes in the summary?

It reads the updates posted for each project during the week, including the health status, and condenses them into two or three sentences. It is told not to add facts that are not in the updates, so the summary only reflects what the team wrote.

Can the digest go to a Slack channel instead of email?

Yes. The summary can be posted to a channel for the leadership team, or sent by email, or both. Email suits people who want a record to forward, while a channel suits teams who discuss the updates right after reading them.

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

On a scheduleAI