FlowRunner
Pricing
Theme

Read and write structured Coda docs from your flows: rows, tables, columns, formulas, controls, buttons, and pages. Agents sync rows without duplicates and pull a person in before deleting rows others depend on.

22 actions available
A record arrives from a webhook, form, or another service
Agent reads the record and maps its fields to the table's columns
Agent confirms the record has the values the table requires
Agent checks the key columns to decide insert versus update
Agent runs Insert or Upsert Rows so no duplicate is created
Agent reads a status column and posts a note if it changed
A record that does not map cleanly to the table is routed for a person to resolve

What This Integration Enables

FlowRunner agents use Coda to keep structured docs current as decisions, not manual entry. An agent can insert or upsert rows against key columns so a repeat record updates rather than duplicates, read rows and named formulas to drive downstream logic, and press configured buttons to run automations. It can list and manage tables, columns, and pages, and generate new docs and pages seeded with content. Because Coda mutations are asynchronous, the connector returns a request ID immediately and the change settles a moment later. The routine sync runs on its own. The row deletes and button presses that are expensive to undo are where the agent stops to ask.

Without FlowRunner

Manual data entry Records are copied into Coda tables by hand as they arrive
Duplicate rows The same record gets entered twice when no one checks first
Stale downstream logic Formulas and controls read data that was never kept current

With FlowRunner

Rows sync themselves Records are inserted or upserted against key columns automatically
No duplicates The upsert matches on key columns, so a repeat record updates the existing row
Live doc logic The table stays current, so formulas and controls compute on real data

Use Case Scenarios

Deduplicated Table Sync

Records arrive from another system. The agent maps each to the table's columns and runs Insert or Upsert Rows with key columns set, so a record already present updates its existing row instead of creating a duplicate. The team's doc stays clean without anyone reconciling it by hand.

Status-Driven Notification

The agent reads a status column with Get Row on a schedule. When the status changes to a value that matters, it posts a note to the team with a link to the doc. Because the agent watches the specific column, the notification is tied to a real change, not a guess.

Bulk Row Delete with a Review Gate

A cleanup rule identifies rows that look stale. The agent lists the candidates with List Rows and prepares a Delete Multiple Rows call. Before it deletes a batch of rows that other people's formulas and views depend on, it pauses for the doc owner to review the list and approve the deletion.

Human-in-Loop Highlight

When an agent is about to run Delete Multiple Rows on a shared table, it does not just run the delete. Removing a batch of rows can break formulas, views, and controls that other people rely on, and the rows do not come back. The agent pauses and routes to the doc owner through their preferred channel: "Ready to delete [N] rows from [Table] that matched [criterion]. Other views may reference them. Approve the deletion or review the list first?" The owner decides, and the agent runs Delete Multiple Rows only on confirmation. Routine inserts and upserts run on their own; deleting rows people depend on reaches a person first.

Agent processes routinely
Detects exception requiring judgment
Clear match Continues automatically
Ambiguous Routes to human via preferred channel
Human decides
Agent resumes with decision

Agent Capabilities

22 actions

Docs

4
  • List Docs Lists the docs available to the account, with search and owner filters. Used to resolve which doc to work in.
  • Get Doc Retrieves a single doc's metadata, including its name, owner, and workspace. Used to inspect a doc.
  • Create Doc Creates a doc, optionally copying an existing one and placing it in a folder. Used to provision structure on demand.
  • Delete Doc Permanently deletes a doc. Used in cleanup.

Tables

2
  • List Tables Lists the tables and views in a doc. Used to resolve which table to read or write.
  • Get Table Retrieves a table's metadata, including its display column and row count. Used to inspect a table before acting.

Rows

6
  • List Rows Lists rows in a table as clean objects, with a column-value filter and paging. Used to find rows matching a criterion.
  • Get Row Retrieves a single row's cell values as a clean object. Used to read a specific record.
  • Insert or Upsert Rows Inserts rows, or upserts them against key columns so a matching record updates instead of duplicating. Used to keep a table in sync with an external system.
  • Update Row Updates a single row's cell values, changing only the columns provided. Used to correct or progress a record.
  • Delete Row Deletes a single row. Used in cleanup.
  • Delete Multiple Rows Deletes several rows by ID in one request. Used for batch cleanup, gated behind a human review on shared tables.

Columns

2
  • List Columns Lists a table's columns with their types and flags. Used to map incoming fields to the right columns.
  • Get Column Retrieves a single column's metadata, including whether it is a formula. Used to inspect a column.

Formulas and Controls

4
  • List Formulas Lists the named formulas defined at the doc level. Used to discover computed values to read.
  • Get Formula Retrieves a named formula and its current computed value. Used to read a doc-level calculation.
  • List Controls Lists the interactive controls in a doc, such as buttons and selects. Used to discover controls to read.
  • Get Control Retrieves a single control's type and current value. Used to read a control's state.

Buttons

1
  • Push Button Presses a button in a button column for a row, running its configured action. Used to trigger a doc automation from a flow.

Pages

3
  • List Pages Lists the pages in a doc with their hierarchy. Used to resolve which page to read or seed.
  • Get Page Retrieves a single page's metadata, including its name and link. Used to inspect a page.
  • Create Page Creates a page in a doc, optionally seeded with rich text or HTML. Used to generate structured content.

Start building with Coda

$100 in credits. No card required. Connect in minutes.