Turn nested API data into clean Airtable rows

From tree to table

• Pick the record list anywhere in the response, for example data.items.
• Map by path: customer.address.city or items[0].sku into any field.
• Expand lists into rows: an order with three line items becomes three rows, with the order fields repeated. Several levels of nesting work, and object keys can become rows too.
• Join lists into one cell with a separator of your choice, when you want tags rather than rows.
• Fixed values for fields that should always hold the same thing, such as the source name.

Airtable field types

Each mapping has an explicit type, and Rowvela checks the target field in the Airtable schema before writing:

• Text, number, checkbox, date and date-time
• Single select and multiple select (unknown options are reported before writing)
• Linked records, matched by a field in the linked table, optionally creating the missing linked records
• Attachments from public file URLs; Airtable downloads them when the preview is applied
• Collaborator, multiple collaborators and barcode

If a mapped field does not exist yet, Rowvela offers to create it with a matching type.

Expressions and JMESPath

A small expression per field runs before type conversion: value / 100, round(value, 2), upper(trim(value)), concat("SKU-", text(value)), coalesce(value, "n/a"). It cannot run code, loops or regular expressions, so it is safe to share imports.

For bigger reshaping, a JMESPath expression transforms the whole response before mapping, in an isolated worker with time and size limits.

Workspace variables

Define values like {{region}} or {{api_base}} once per workspace and reuse them in URLs, headers and bodies. Secret variables are encrypted and never shown again after saving.

Export, import and Data Fetcher migration

Any import can be exported as a JSON configuration without its secrets and imported into another workspace. A Data Fetcher export converts into a Rowvela import, with a list of anything that could not be carried over.