Overview
The node provides functionality to update an existing record in a datasheet within the Aitable.ai platform. It allows users to specify which fields of a record to modify, supporting various field types including text, number, checkbox, date, select options, multi-select, and linked records. This operation is useful when you need to programmatically change data stored in Aitable datasheets, such as updating project statuses, modifying user information, or correcting data entries.
Practical examples include:
- Updating the status field of a project record after a milestone is reached.
- Changing the due date of a task record.
- Modifying linked records to reflect new relationships between entities.
Properties
| Name | Meaning |
|---|---|
| Space ID | The unique identifier of the space containing the datasheet (e.g., spcX9P2xUcKst). |
| Datasheet ID | The unique identifier of the datasheet that contains the record to edit (e.g., dstXXXXXXXXXXX). |
| Record ID | The unique identifier of the record to update (e.g., recXXXXXXXXXXX). |
| Use Field Names | Boolean flag indicating whether to use field names instead of field IDs when updating the record. Using field names is recommended for clarity and ease of use. |
| Fields | Collection of fields to update on the record. Each field includes: - Field Name or ID: The name or ID of the field (e.g., "Title" or fldXXXXXXXXXXX).- Field Type: Type of the field (Checkbox, Date, Link (One-Way), Link (Two-Way), MultiSelect, Number, Select, Text). - Field Value: The value to set for the field. For linked fields, enter record IDs separated by commas. To explicitly clear a linked field, type "null". Empty values are ignored for security reasons. |
| Fetch Fields | Boolean flag to fetch datasheet field metadata before updating. This helps map field names to IDs and validate fields but may add an extra API call. |
Output
The output JSON object contains the updated record data returned from the Aitable API, including:
- The updated fields with their new values.
- The record's unique ID.
- The datasheet ID where the record resides.
If the update fails, the output will contain a success flag set to false, an error message, and the raw API response for debugging.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the Aitable.ai API via an API key credential configured in n8n.
- The node uses HTTP requests authenticated against the Aitable API endpoint at
https://aitable.ai. - Optional fetching of datasheet field metadata requires additional read permissions on the datasheet.
Troubleshooting
- Missing Required IDs: Errors occur if Space ID, Datasheet ID, or Record ID are not provided. Ensure these are correctly set.
- Field Mapping Issues: If "Fetch Fields" is enabled but the API call to retrieve field metadata fails, the node throws an error. Disable this option or verify API connectivity.
- Invalid Field Values: Providing empty strings for field values results in those fields being ignored. To clear linked fields, explicitly use
"null". - API Errors: Network issues or invalid credentials cause errors during the API request. Check your API key and network access.
- Continue On Fail: If enabled, the node outputs error details in the JSON instead of stopping execution, allowing workflows to handle failures gracefully.
Common error messages include:
"Datasheet ID is required"or"Record ID is required": Missing essential parameters."Failed to fetch field metadata": Problems retrieving field info; check API access."Record update failed or error occurred": General failure updating the record; inspect the response for details.
Links and References
- Aitable.ai Official Website
- Aitable API Documentation (Unofficial) (Note: The node uses an unofficial integration)
- n8n Documentation on Creating Custom Nodes