Teable icon

Teable

Interact with Teable API - A powerful database platform with spreadsheet-like interface

Actions6

Record → Update Multiple Records

AI-generated

Overview

The node integrates with the Teable API, a database platform with a spreadsheet-like interface. Specifically, the "Update Multiple Records" operation under the "Record" resource allows users to update several records in a specified table at once. This is useful when you need to batch modify multiple entries efficiently without making individual update calls for each record.

Practical examples include:

  • Updating contact information for multiple customers simultaneously.
  • Changing status fields for a group of project tasks.
  • Bulk editing inventory item details such as prices or quantities.

Properties

Name Meaning
Table ID The unique identifier of the table where records will be updated. Found in the table URL or API docs.
Records A collection of records to update. Each record requires:
- Record ID: Unique identifier of the record to update.
- Fields: JSON object specifying the fields and their new values (e.g., {"Name": "John Doe", "Age": 31}).
Additional Options Optional settings including:
- Field Key Type Specifies how field keys are identified in the update payload. Options: Name, ID, or Database Field Name.
- Typecast Boolean flag indicating whether to automatically convert field value types during update.

Output

The node outputs JSON data representing the response from the Teable API after attempting to update the records. This typically includes confirmation of updated records, any errors per record, and possibly the updated record data itself.

If binary data were involved (not indicated here), it would represent file attachments or similar content related to records, but this operation focuses on JSON record updates only.

Dependencies

  • Requires an API key credential for authenticating with the Teable API.
  • Needs the base URL of the Teable instance configured in credentials.
  • The node sends HTTP requests with JSON payloads to the Teable API endpoints.

Troubleshooting

  • Invalid Table ID: If the provided Table ID is incorrect or does not exist, the API will return an error. Verify the Table ID from the Teable UI or API documentation.
  • Malformed JSON in Fields: The "Fields" property expects valid JSON. Errors occur if the JSON is invalid or improperly formatted. Use proper JSON syntax.
  • Field Key Type Mismatch: Ensure the selected field key type matches the keys used in the "Fields" JSON object; otherwise, updates may fail or target wrong fields.
  • Authentication Errors: Missing or invalid API credentials will cause authentication failures. Confirm that the API key and base URL are correctly set in n8n credentials.
  • Typecasting Issues: Enabling typecast may cause unexpected conversions if field values do not match expected types. Disable if unsure.

Links and References

Discussion