On this page
Table Agent Actions
MiniUp derives candidates from Tables belonging to the app. Source IDs keep enabled actions attached when a Table is renamed. Deleting a Table removes its action configuration; changing its schema changes the effective action inputs.
| Operation | Inputs | Risk |
|---|---|---|
| List | limit, offset, optional filters | Read only |
| Search | q, optional filters and pagination | Read only |
| Get | recordId | Read only |
| Create | record with actual Table fields | Can change data |
| Update | recordId, fields with actual Table fields | Can change data |
| Delete | recordId | Destructive |
Read inputs support the existing Table API’s field/value equality filter, dateField/dateFrom/dateTo date filter, and includeTotal. Page size defaults to 25 and is limited to 100. Offset is limited to 100,000. Use successive pages when needed.
{ "q": "Ada", "limit": 25, "offset": 0 }{ "record": { "name": "Ada", "email": "ada@example.com" } }Inputs use actual field types. Unknown fields and client-supplied site, owner, or role identifiers are rejected. Each mutation changes one record. Table quotas, record limits, validation, and notification behavior remain in the existing Table handlers.
Actions require an owner, admin, or editor for mutations, including Tables whose normal API supports public form submission. Read access still follows the Table’s access rules. Enabling an action never shares its write key.