Short answer: Drop the "Teable → Create Record" 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 |
|---|---|---|---|
Table ID table_id | string | Required | — |
Fields fields | object | Required | Field map. Keys are field names (or IDs); values match field type. |
{"table_id": "{{trigger.table_id}}","fields": "{ \"Name\": \"My Item\", \"Status\": \"Todo\" }"}
{"records": [{"id": "recXXXX","fields": {"Name": "My Item"}}]}
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.