ActionBaserowUpdated September 2026
How do I delete multiple Baserow rows in one call?
Short answer: You can batch delete rows in Baserow by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Baserow Batch Delete Rows action to a workflow, map its 2 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
Inputs
The fields this action accepts.
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 | The Table ID assigned by Baserow. Find via the corresponding list/search operation in this app. Use the exact ID, not a name or label. |
Row IDs (JSON Array) items | json | Required | JSON array of row objects. Each object should have field names as keys. Example: [{"Name": "Alice", "Email": "alice@example.com"}] |
Sample request
{"table_id": "{{trigger.table_id}}","items": "[1, 2, 3]"}
Returns
{"success": true}
Use these fields in downstream nodes for routing, logging, or error handling.
Triggered by
Apps that pair well as the trigger for Batch Delete Rows.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about Batch Delete Rows.
What does the Batch Delete Rows action do in Baserow?
Removes multiple rows by ID list. Useful for cleanup workflows — "delete all rows older than N days", "remove rows matching this status after archival to warehouse".
What inputs does Batch Delete Rows require?
Required: Table ID, Row IDs (JSON Array). Every input accepts a static value or a variable from any upstream node in your workflow.
Can I use dynamic inputs from earlier workflow nodes?
Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.
What happens if Baserow returns an error?
The run history shows the failed step with its input and the error message Baserow returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.
Does Batch Delete Rows support batch operations?
Run Batch Delete Rows inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Baserow's rate limits.
More actions
Other Baserow actions.
Action
Batch Create Rows
Creates multiple rows in one API call — much more efficient than per-row Create Row for ingestion workflows. Up to ~200 rows per call. For "ingest CSV upload into Baserow" or "sync 500 leads from CRM" workflows, this is the right path.
ActionBatch Update Rows
Updates multiple rows in one call. Each entry has the row ID + the fields to change. Useful for sync workflows that reconcile Baserow with an external source (e.g., "update prices on 200 product rows from a price-list sync").
ActionCreate Row
Inserts a single row into a Baserow table with field values keyed by field name or ID. For bulk ingestion (>20 rows), prefer Batch Create Rows which is significantly more efficient per-row.
ActionDelete Row
Removes a specific row by ID. Irreversible. For bulk deletes, use Batch Delete Rows. For "soft delete" semantics, add a deleted_at field rather than hard-deleting so you can audit.
ActionGet Row
Returns the row by ID with all field values typed per column. Use after List Rows or as a confirmation lookup before destructive operations.
ActionGet Table Fields
Returns the column definitions for a table — each field's name, ID, type, and configuration (e.g., link to another table, formula, single/multi-select options). Useful at workflow-build time to validate field types before writes.