Skip to content
EN
Open app

Data Table

1 min read
Copy as Markdown
View as MarkdownOpen the raw .md file.md

Data Table is a static grid on the canvas. You define columns (each needs a key) and optional rows. Downstream reads {{node_X.rows}}. A table with no usable column blocks Save. Zero rows is valid (empty set).

A short SKU list, office locations, canned replies — data that is not worth an API. Live inventory still belongs in Connect To External Service.

The editor’s lookup mode is not shipped. Treat it as a producer: columns + rows out.

First setup — three SKUs the agent can read

Section titled “First setup — three SKUs the agent can read”
  1. Any trigger. Data Table. Columns: sku, name, in_stock (boolean). Three rows you can say on a call.

  2. Filter or If/then on a During Call parameter vs sku.

  3. AI Response with name / in_stock.

  4. Save & go live, attach, ask for one of those SKUs.

  • Needs setup — no column key.
  • {{node_X.rows}} is empty objects — keys missing or you pointed at the wrong node.
  • Stale stock — you edited the live warehouse in a static table.
Table vs Google Sheet?

Table ships with the workflow. A Sheet is shared and edited outside the builder. Use the Sheet when ops own the rows.