Skip to content
ClickRuntime

Automate Coda

Coda docs often run on tables: request logs, project lists, task trackers. Automations watch those tables for new and edited rows, send you the items still open each morning, and tidy away tasks that were finished weeks ago. Explain the table and the rule to your assistant, confirm the steps it lays out, and ClickRuntime carries on with it in the background.

Add to ChatGPTAdd to Claude
Works inChatGPTClaudeClaude CodeCursorCodexVS CodeGemini CLIZedopencodeAny MCP client

Try asking

Create a ClickRuntime automation: every 10 minutes check the Requests table in my 'Team Ops' Coda doc and email me the Name, Type and Details of any new rows.

Paste it into your assistant. It tells you what it will send or change before it runs live.

Ideas

What you can automate in Coda

Emails for new rows, Slack posts for edited ones, a morning list of open tasks, and a weekly clear-out of old finished rows. These are ready-made starting points. Anything else you can describe works too.
Every 5–15 minutes

Get 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 works
Every 15 minutes

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

See how it works
On a schedule

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 works Your own logic

Any other automation you can describe in words

Your own rules, schedule and AI steps with Coda, plus any other app. Describe it and your assistant builds it.

See how to build your own

Build your own

Build any Coda automation you can describe

The ideas above are ready-made starting points, not a fixed list. Describe what Coda should do in your own words, with your conditions, other apps or an AI step, and 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.

For example, ask your assistant

Every morning, read my Coda Tasks table, use AI to set a Priority for rows that have none, and mark rows past due as Overdue.

When a row in my Coda Requests table is marked Approved, post the request and requester in #ops on Slack.

Every Monday, copy last week's rows from my Coda Projects table to my Archive sheet in Google Sheets and email the open ones to me through Gmail.

Beyond chat

Have Coda work when you're not in the chat

Connecting Coda to ChatGPT or Claude lets you ask about it while you chat. ClickRuntime handles the part that should happen on its own: checks on a schedule and actions on each new event, set up from the same chat and running after you close it.

Setup

Connect Coda

Coda connects with an API token you generate in your own Coda account settings. You can limit the token to specific docs so it sees nothing else.

Coda

Docs

  1. In Coda, open your account settings and find the API settings section.
  2. Generate an API token, and restrict it to the docs your automation needs if you prefer.
  3. For automations that delete or change rows, make sure the token is not read-only.
  4. In the ClickRuntime dashboard, go to Connections & secrets and save the token as a secret for Coda.

Good to know

Coda limits that affect automations

  • Coda limits API calls per user: about 100 reads and 10 writes every 6 seconds, and listing docs is limited to 4 calls every 6 seconds.
  • Writing content into a doc is slower still, at 5 calls every 10 seconds, so bulk edits are batched into as few calls as possible.
  • Calls over the limit get an error and are retried, which can delay a run by a few seconds.
  • Deleting rows works only on base tables, not on views of them.

FAQ

Questions about automating Coda

What can ClickRuntime do in my Coda docs?
Read rows from tables in the docs your token can reach, and, if the token allows writing, add or remove rows. Restricting the token to chosen docs keeps everything else out of reach.
How quickly do new or changed rows show up?
These automations check the table on a schedule, every 5 to 15 minutes, and compare against what they saw last time. So you hear about a new row within that window rather than instantly.
Is it safe to let it delete old rows?
The clean-up automation emails you the values of every row it is about to remove before deleting them, so you keep a copy. It only touches rows that match your rule, like Done and completed over 30 days ago.
Do I need a paid Coda plan?
No. The Coda API works on free and paid workspaces.
Does it need an AI key?
No. These Coda automations are plain filters and alerts. If you add a summary step, it uses the AI bundled with every ClickRuntime plan.
Is this a Coda connector for ChatGPT or Claude?
Not for chatting with Coda data. A chat connector lets your assistant read and change Coda while you're in the conversation. ClickRuntime is for the work that should happen without you: you set up an automation from the chat once, and it keeps running on a schedule or on each Coda event.

Related pages

Keep exploring

Tell your assistant what Coda should do

Free plan. No credit card.

Add to ChatGPTAdd to Claude