On a schedule
Get your open Coda tasks each morning
Every morning one email lists the tasks in your table that aren't done yet.
- Runs
- On a schedule
- Apps
- Coda
- AI
- Not needed
- Access
- read
Send this to your assistant
Create a ClickRuntime automation: every weekday at 8am email me the rows in the Tasks table of my Coda doc where Status isn't Done, sorted by Due Date.
First time? Adding ClickRuntime to your assistant takes about two minutes.
Why use it
Why teams use this automation
Shared tables only help when someone reads them. A team keeps its open requests, support follow-ups or hiring pipeline in a Coda table, but each person must remember to open the doc and filter for what is open. On busy days the doc is forgotten, and items that should have moved sit untouched.
Each morning, this queries the table using a filter you define, such as status is Open, and emails you the matching rows as a short list. The work comes to your inbox instead of waiting for you to go and find it.
It suits managers and coordinators who run their operations from a Coda table but live in email during the day. The list is built with a filter you define, so the email shows exactly the rows your team considers open, such as overdue, unassigned or urgent items.
What you get out of it
Start the day with a clear to-do list
A morning email listing open rows removes the step of opening the doc and applying filters. You see what needs attention before the first meeting. The email arrives before the first meeting, so the day starts with a plan and you spend no time applying filters.
Stop items going stale
Rows that appear in the email day after day become hard to ignore. That visible repetition nudges owners to close or reassign them. A row that appears in the email day after day becomes hard to ignore, and owners tend to close or reassign it.
Include people who rarely open Coda
Stakeholders who prefer email still see the state of the table. They are informed without needing a Coda seat or knowing how the doc is organised. People who prefer email still see the state of the table, and do not need a Coda seat to stay informed.
Reduce status meeting time
If everyone reads the same list beforehand, the standup can skip reading it aloud. The meeting becomes about decisions and blockers. If everyone reads the same list beforehand, the standup can move straight to blockers and decisions and skip the roll call.
Work with your own definition of open
The filter is yours, whether it is overdue, unassigned or high priority. The digest reflects how your team actually works instead of a fixed template. Since the filter is yours, the digest follows how the team really works and does not impose a fixed idea of what counts as open.
How it works
What happens, step by step
Every morning at 8, ClickRuntime reads your Coda tasks table.
It keeps the tasks that are still open.
You get one email listing them with their due dates and status.
Before it runs live
- Connect Coda
What you get
Build your own
Need it to work differently?
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
- 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 Coda steps into one automation
Under the hood
The code that runs this automation
from clickruntime import on_trigger, notify, http, credentials
DOC, TABLE = "AbCDeFGH", "Tasks" # your doc id and table
@on_trigger
def run(event):
rows = http.get(f"https://coda.io/apis/v1/docs/{DOC}/tables/{TABLE}/rows", headers={
"Authorization": "Bearer " + credentials.secret("CODA_API_TOKEN")}, params={
"useColumnNames": "true", "valueFormat": "simple", "limit": 500,
}).json()["items"]
open_rows = [r for r in rows if r["values"].get("Status") != "Done"]
open_rows.sort(key=lambda r: r["values"].get("Due Date") or "9999")
lines = [f"{(r['values'].get('Due Date') or 'no date')[:10]} {r['name']} ({r['values'].get('Status')})" for r in open_rows]
notify.email_me(f"{len(open_rows)} open tasks", "\n".join(lines) or "Everything is done.")
return {"open": len(open_rows)}FAQ
Common questions
Which rows appear in the email?
Can I send the digest to several people?
What if no rows match?
What permissions does it need?
Does it need AI?
How many runs does it use?
Can I change how it works?
Related
You might also like
Clear out finished Coda tasks every week
Rows marked Done over 30 days ago are removed each week, and you get an email listing exactly what went.
See how it worksGet an email for each new Coda row
Within minutes of a row being added to your table, its values arrive in your inbox.
See how it worksPost edited Coda rows to Slack
When someone changes a row in your projects table, the updated row shows up in your Slack channel.
See how it worksKeep exploring
Set up “Get your open Coda tasks each morning” from your assistant
Copy the prompt above, or connect your assistant first. Free plan, no credit card.