Docs · Writing
Writing to Airtable
Rowvela compares the source with the table and writes only what differs. How it does that is set under How should records be written? and Match existing records by.
Write modes
| Option | What happens |
|---|---|
| Create new records only | Every source row becomes a new record on every run. Use it only when the source returns new items each time; a scheduled run otherwise duplicates rows. |
| Update matching records, create new ones | Updates records with the same key and creates the rest. The usual choice. |
| Update matching records only | Updates records with the same key; rows without a match are listed as skipped. |
Match keys
Choose one to three fields in Match existing records by, for example Order ID, or Order ID + Line. Every part of the key must have a value. If two source rows or two Airtable records share a key, the preview blocks the write instead of guessing. Records are never matched by their position.
Only changed fields are updated. Fields you did not map keep their values.
Deleting records missing from the source
With an update mode, Delete records that are no longer in the source removes records whose key the source no longer returns.
- Deletions are listed in the preview like every other change.
- Nothing is deleted when the source returns no rows.
- Above the share set in Ask for confirmation when more than this share of the table would be deleted, a manual run asks you to confirm and an automated run waits for your review.
- With a Destination view, only records in that view can be deleted.
- Reverting the run brings deleted records back as new records. Their comments and links from other tables cannot be restored.
Errors while writing
Rowvela writes in batches of ten. Under Error handling:
- When Airtable rejects a batch: Stop the run, or Skip that batch and continue up to Stop after this many rejected batches.
- Pause automation after failed runs in a row pauses a scheduled import after repeated failures (3 by default) and emails verified members.
- Source status codes that mean “no data” treats, for example, a 404 as an empty result instead of an error.
If a batch times out, Rowvela does not know whether Airtable stored it, so it never sends it again on its own. The run details mark those rows as uncertain; check them in Airtable before running again.
Run for each record
Instead of importing a list, Run for each record sends the request once for each record of an Airtable table or view and writes the answer back to that record, for example to enrich companies by their domain. Add record values such as {{record.Domain}} to the URL, headers or body. Set Maximum input records per run to control cost. Records are matched by their Airtable ID and are never created.