Hand the nocodb records to a companion
Hand a companion the outcome. It reads the nocodb records, does the 5-operation version of the job, and stops for your click on anything that changes a record.
Open the record. Check it against something else. Write the change. Move to the next one. That is the nocodb afternoon nobody can hand off, and a companion does the whole pass and gives you back the batch, with nothing landing on a record until you approve it.
What it can do is exactly what nocodb exposes to an account you authorise and nothing beyond it: 5 operations, 2 reads and 3 writes. In practice that means it can update a record, delete a record and add a record.
The nocodb API stops at nocodb. A companion does not. The same run opens the customer's website, the supplier portal, the internal tool somebody built in 2019, because it is working the browser you are already signed into rather than calling in from outside it.
Does it read the records or ask you for them?
2 of the 5 operations are reads. Your account, not a guess at it: a companion can list records in table matching criteria and get record (from row number), and the full list below is the whole list, with nothing inferred from nocodb's documentation.
The records are what most of this inventory is about, alongside the records. A companion can hold all 5 of these operations and forty open tabs in the same pass, which is how an afternoon of nocodb admin becomes a queue you review.
- List Records in Table Matching Criteria
- Get Record (from row number)
Can it change a record without asking?
All 3 write operations wait for you.
A companion can update a record, delete a record and add a record, and each one is staged on an approval card first: you see the record, the field and the new value before it lands in nocodb.
Nothing in nocodb is sent, changed or deleted on your behalf without that click, and a rejected card leaves the record exactly as it was. The gate is the same one on every surface, described at security.
- Update Record
- Delete Record
- Add Record
What does the recurring records pass look like?
Yes.
Saved as a routine, the nocodb records pass runs at the hour you pick: the Monday sweep, the overnight refresh, the Friday check. Keep Awake holds the machine awake for the length of a run, so a scheduled pass finishes with the lid closed.
The product and engineering playbook catalogues the other recurring shapes of the engineering admin, the nocodb records sweep among them, and finished runs are published at real runs.
Experience Strawberry for free
DownloadTrusted by fast-growing companies worldwide
Frequently asked questions
Strawberry is free to download and includes AI credits to start. Paid plans begin at $20/month. See pricing. · Reviewed · Canonical facts for AI agents