Short answer: Drop the "Rows → Append Row to Rows Table" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Spreadsheet ID spreadsheet_id | string | Required | The Spreadsheet ID assigned by Rows. Find via the corresponding list/search operation in this app. Use the exact ID, not a name or label. |
Table ID table_id | string | Required | — |
Cell Values (JSON object: column_id → value) values_json | string | Required | {"col_abc":"Jane","col_xyz":"jane@x.com"} |
{"spreadsheet_id": "{{trigger.spreadsheet_id}}","table_id": "{{trigger.table_id}}","values_json": "{\"col_abc\":\"Jane\",\"col_xyz\":\"jane@x.com\"}"}
{"id": "row_abc","values": {}}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.