BASEROW n8n INTEGRATION: AUTOMATE BASEROW WITH N8N

The "Update a row" action modifies existing records in your Baserow tables. Whether you're changing a status field, updating contact information, or incrementing a counter, this action writes changes precisely where you need them.

Key parameters: Credential to connect with (select your Baserow credentials, required), Database Name or ID (the database containing the row to modify, required), Table Name or ID (the specific table where the row exists, required), Row ID (the unique identifier of the row you want to update, critical and required), Data to Send (select "Define Below for Each Column" to specify which fields to update), and Fields to Send (add only the fields you want to modify—unchanged fields don't need to be included).

Practical use cases: Mark a lead as "Contacted" when an email is sent successfully, update inventory quantities when orders are placed or fulfilled, change project status based on external events (GitHub commits, Jira updates), or record timestamps for audit trails when records are processed.

Important: You only need to specify fields you're changing. Omitted fields retain their existing values—this isn't a full row replacement.

When you need to retrieve a specific record from Baserow—perhaps to check if it exists, grab current values before updating, or pull data for use later in your workflow—the "Get a row" action delivers exactly what you need.

Key parameters: Credential to connect with (your authenticated Baserow account, required), Database Name or ID (the database containing your target data, required), Table Name or ID (the specific table to query, required), and Row ID (the unique identifier of the row you want to retrieve—this is Baserow's internal row ID, a number, not a field value, required).

Practical use cases: Fetch customer details before sending a personalized email, retrieve the current status of a record before deciding which workflow branch to execute, pull product information to include in invoice generation, or verify a record exists before attempting an update operation.

💡 Pro tip: The Row ID is returned whenever you create rows or retrieve multiple rows, so store it in earlier workflow steps if you need to reference specific records later.

The "Create a row" action is your go-to for adding new data to Baserow tables programmatically. Every time your workflow needs to insert a new record—whether it's a new lead, a new order, or a new task—this action handles it cleanly and reliably.

Key parameters: Credential to connect with (select your configured Baserow account from the dropdown, required), Database Name or ID (specify which database contains your target table—accepts the database name or its numeric ID, required), Table Name or ID (identify the specific table where the new row will be created, required), Data to Send (choose "Define Below for Each Column" to map specific values to table columns), and Fields to Send (dynamically add field mappings by clicking "Add Field"—each field corresponds to a column in your Baserow table).

Practical use cases: Automatically create new contact rows when someone submits a website form, add order records from Shopify webhooks into an inventory tracking table, insert task entries from Slack messages into a project management database, or log API events or error reports for monitoring purposes.

This action pairs exceptionally well with form tools (Typeform, Tally, Google Forms) and webhook triggers from virtually any application.

When records need to be removed—completed tasks, cancelled orders, test data cleanup—the "Delete a row" action permanently removes the specified row from your Baserow table.

Key parameters: Credential to connect with (your authenticated Baserow account, required), Database Name or ID (database containing the row to delete, required), Table Name or ID (table where the row currently exists, required), and Row ID (the unique identifier of the row to remove, required).

Practical use cases: Remove completed tasks after they've been archived elsewhere, delete cancelled order records as part of a cleanup workflow, purge test entries from production tables during maintenance windows, or implement data retention policies by removing records older than a threshold.

⚠️ Warning: Deletion is permanent in Baserow—there's no trash/recycle bin for API-deleted rows. Consider adding a confirmation step or moving records to an "Archive" table instead if you might need the data later.

Need to pull multiple records at once? The "Get many rows" action retrieves batches of data from your Baserow tables, perfect for reporting, bulk processing, or syncing data to other systems.

Key parameters: Credential to connect with (your Baserow account credentials, required), Database Name or ID (target database identifier, required), Table Name or ID (the table to retrieve rows from, required), Return All (toggle this on to fetch every row in the table—use cautiously with large tables), and Limit (when "Return All" is off, this numeric field caps how many rows to retrieve; default is 50).

Practical use cases: Export all contacts from Baserow to a Google Sheet for executive reporting, retrieve pending orders for batch processing through a fulfillment system, pull all team members to send a mass notification via Slack or email, or sync product catalogs to external platforms periodically.

Performance note: For tables with thousands of rows, consider using the Limit parameter and processing in batches to avoid timeout issues or memory constraints in complex workflows.