Actions8
Overview
The node integrates with the Xano API to manage data within workspaces and tables. Specifically, the "Create Row" operation under the "Table" resource allows users to add a new row of data into a specified table within a workspace. This is useful for automating data entry tasks, syncing external data sources into Xano, or dynamically populating tables based on workflow outputs.
Practical examples include:
- Adding a new customer record into a CRM table when a form is submitted.
- Logging event data into an analytics table automatically.
- Creating inventory entries in a product management system from an external source.
Properties
| Name | Meaning |
|---|---|
| Workspace Name or ID | Select or specify the workspace where the target table resides. |
| Table Name or ID | Select or specify the table within the chosen workspace where the new row will be created. |
| Fields | Define one or more fields to set in the new row. Each field requires: |
| - Field Name or ID | The name or identifier of the field/column in the table to populate. |
| - Field Value | The value to assign to the specified field in the new row. |
Output
The node outputs JSON data representing the newly created row in the table. This typically includes all fields of the row as stored in Xano, including any auto-generated IDs or timestamps. If the node supports binary data output (not indicated here), it would represent file attachments or similar content related to the row.
Dependencies
- Requires an API key credential for authenticating with the Xano API.
- The node depends on n8n's ability to load options dynamically for workspaces, tables, and fields via dedicated methods.
- Proper configuration of the API credential in n8n is necessary to access the Xano environment.
Troubleshooting
Common issues:
- Invalid workspace or table ID: Ensure that the selected workspace and table exist and the API key has access rights.
- Missing required fields: All mandatory fields must be provided; otherwise, the API may reject the request.
- Network or authentication errors: Verify API credentials and network connectivity.
Error messages:
- Authentication failures usually indicate invalid or expired API keys.
- Validation errors from the API often point to incorrect field names or incompatible field values.
Resolving these typically involves checking the input parameters, refreshing credentials, and confirming permissions in the Xano dashboard.