DashboardSign inStart your trial

Data Nodes

Reference for the workflow nodes that read, write, aggregate, and react to workspace tables.

These are the workflow nodes that operate on your tables and files . Add them from the node catalog in the workflow builder. Each writes typed output that downstream nodes can reference through the variable picker.

#Data node

The Data node reads and writes rows in a workspace table. It picks a table by its slug, then runs one of four operations:

OperationDoes
AddInsert a new row. Supply a match selector to upsert instead (update the matching row, or insert if none exists).
FindQuery rows with an optional filter, sort, and limit (up to 1000 rows).
UpdatePatch a specific row by its id.
DeleteRemove a specific row by its id.

Cost: 1 Workflow Credit per run. The node’s output (the inserted row’s id, or the rows returned by a find) flows into later steps as variables.

#Aggregate Rows

The Aggregate Rows node rolls a table up instead of returning individual rows. Group by up to three fields and compute one or more aggregations:

  • sum, avg, min, max over a numeric field
  • count of rows
  • percentile at a threshold you set

You can also bucket by time (hour, day, week, or month) on a date field, apply a filter, and cap the number of groups returned. Use it for a daily total, a per-owner count, a p90 response time, and similar rollups.

Cost: free. Reading and aggregating rows costs nothing.

#Data Change trigger

The Data Change trigger starts a workflow when a table changes. Configure:

  • Table: which table to watch.
  • Change type: row added (a new row lands in the table) or form submitted (a bound form is submitted).
  • Form (optional): when the change type is form submitted, scope the trigger to a single form, or leave it open to fire on any submission to the table.

Cost: free, like every trigger. When it fires, the new row is passed to the workflow as trigger data, so downstream nodes can read the row’s fields immediately. Only published workflows are eligible to fire.

#Variables flowing downstream

Each data node writes structured output the next nodes can reference:

  • The Data Change trigger exposes the new row (and, for form submissions, the form it came from).
  • The Data node exposes the inserted row’s id or the rows a find returned.
  • The Aggregate Rows node exposes the computed groups and their aggregate values.

Pick these values from the variable picker in any later node’s configuration.

#Example flow

A lead-capture loop wired end to end:

  1. Data Change trigger (form submitted) fires when someone completes your intake form. The submitted row is the trigger data.
  2. AI node scores or classifies the lead from the row’s fields (billed as an AI Credit).
  3. Human Review queues the proposed next action for approval , free, and the workflow pauses at $0 until you swipe.
  4. On approval, an Integration Action writes the lead into your CRM or notifies the owner.

Every consequential step waits for your sign-off, and each decision is recorded.

#Related