Row → Create
AI-generatedOverview
This node allows you to create a new row in a specified table within a Baserow database. It is designed for scenarios where you need to automate the insertion of data into Baserow from other n8n workflows, such as syncing form submissions, importing data from external sources, or integrating with other business tools.
Practical examples:
- Automatically add new customer records to a Baserow CRM table when a signup form is submitted.
- Insert sales transactions into a Baserow table from an e-commerce platform.
- Log error events or notifications into a Baserow table for later analysis.
Properties
| Name | Type | Meaning |
|---|---|---|
| Database Name or ID | options | The Baserow database to operate on. You can select from a list or specify an ID using an expression. |
| Table Name or ID | options | The table within the selected database where the new row will be created. Select from a list or specify an ID using an expression. |
| Data to Send | options | Determines how the data for the new row is provided: - Auto-Map Input Data to Columns: Uses input properties that match destination column names. - Define Below for Each Column: Manually set each value. |
| Inputs to Ignore | string | (Only for "Auto-Map Input Data to Columns") Comma-separated list of input properties to exclude from being sent to Baserow. Leave empty to send all properties. |
| Fields to Send | fixedCollection | (Only for "Define Below for Each Column") Specify one or more fields and their values to include in the new row. Each field requires a name/ID and a value. |
Output
The node outputs the newly created row as a JSON object. The structure of the output matches the columns of your Baserow table, with field names mapped to their corresponding values. If the table uses internal field IDs, these are converted to human-readable field names in the output.
Example output:
{
"id": 123,
"Name": "John Doe",
"Email": "john@example.com",
"Created At": "2024-06-10T12:34:56Z"
}
- The output always includes the unique row
idand all fields defined in the table. - No binary data is produced by this operation.
Dependencies
- External Service: Requires access to a Baserow instance.
- API Key: Needs valid Baserow API credentials configured in n8n under the credential type
baserowApi. - Environment: The node must be able to reach the Baserow API endpoint.
Troubleshooting
Common issues:
- Invalid Database or Table ID: If the provided database or table ID does not exist or is incorrect, the node will throw an error indicating the resource was not found.
- Missing Required Fields: If required fields are not provided (either via auto-mapping or manual definition), Baserow may reject the request.
- Authentication Errors: If the API key is missing or invalid, you will receive authentication errors from Baserow.
- Field Mapping Issues: When using auto-mapping, ensure your input property names exactly match the Baserow column names.
Error messages and resolutions:
"Database not found"or"Table not found": Double-check the IDs or names provided."Missing required field": Ensure all mandatory fields are included in your input."Invalid credentials": Verify your Baserow API credentials in n8n.