Collects as they arrive, acts daily

Get one evening email of new to-dos

Instead of separate notices, you get one email each evening with every to-do added that day.

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

Send this to your assistant

Create a ClickRuntime automation: collect every new to-do in my Basecamp projects during the day and email me one list at 6pm.

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

When a busy Basecamp project has a dozen contributors, every new to-do triggers a notification. Someone who is subscribed to the project gets a stream of small emails, dozens a day, and learns to ignore them. Real assignments get lost among minor additions, so a to-do assigned to a person on Tuesday is not seen until Friday, because it was one of thirty notifications that morning.

ClickRuntime collects each new to-do as Basecamp reports it and stores it in memory. At the time you choose, it sends one email listing everything that was added, then clears the memory and begins again. You get a single readable summary, not a stream of interruptions.

It suits project leads who want to stay informed without the cost of constant notifications. You pick the rhythm, daily for fast launches or weekly for quiet projects.

What you get out of it

Attention is protected during the day
One digest replaces many pings. You can focus on your own work and still know what was added, without a constant stream of small interruptions. You can focus on your own work and still stay informed.
Real assignments stop getting lost
In a single list, to-dos assigned to you stand out more than they do among thirty separate emails. You are less likely to miss something that needs your action. You are less likely to miss something that needs your action.
Leads get an overview of project growth
Seeing everything added in a day shows how the scope is changing. A lead can spot to-dos that duplicate each other or that belong in a different list. Duplicates and misplaced items become easy to spot.
Fewer mutes and unsubscribes
People who are overwhelmed by notifications eventually mute the project. A manageable digest means they stay subscribed and keep the visibility the team needs. The visibility the team needs is kept alive.
A daily or weekly rhythm fits your pace
Choosing how often the digest is sent lets you match the project. Fast-moving launches might want daily, while a slow client project can use a weekly summary. Fast launches get daily summaries and slow projects get weekly ones.

How it works

What happens, step by step

Each time a to-do is added in your Basecamp project, ClickRuntime notes it down.
Every evening at 6, it sends you one email listing all the new to-dos from the day, with who added them and links.
The list is then cleared, so tomorrow's email only has new to-dos.

Before it runs live

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

What you get

RunsCollects as they arrive, acts daily

Get one evening email of new to-dostoday, 9:00Succeeded

Email · 5 new Basecamp to-dos todayWebsite Redesign: Review footer copy (by Sam at Northwind) https://3.basecamp.com/4400000/buckets/2700000/todos/7100000

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

daily_weekly_digest_of_new_to_dos.pyexample

from clickruntime import on_event, on_trigger, state, notify

@on_event
def remember(event):
    body = event.json or {}
    if body.get("kind") != "todo_created":
        return {"stored": False}
    todo = body["recording"]
    pending = state.get("todos") or []
    pending.append(f"{todo['bucket']['name']}: {todo['title']} (by {body['creator']['name']})\n{todo['app_url']}")
    state.set("todos", pending)
    return {"stored": True}

@on_trigger
def send(event):
    todos = state.get("todos") or []
    if todos:
        notify.email_me(f"{len(todos)} new Basecamp to-dos today", "\n\n".join(todos))
    state.delete("todos")
    return {"sent": len(todos)}

FAQ

Common questions

What does the digest list for each to-do?

It lists the title, the to-do list it was added to, who it is assigned to and a link. If a to-do has a due date, that can be included too. This is enough to decide quickly which items need attention and which can wait.

What happens if nothing was added?

The flow can skip sending when the memory is empty, or send a short note that nothing new happened. Most people prefer silence on quiet days, since an empty email trains you to ignore the digest.

Is anything missed between sending and clearing?

Events are stored as they arrive and the memory is cleared only after the email has been sent. A to-do created while the email is being prepared is kept for the next digest, so none are lost or reported twice.

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