Teable icon

Teable

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

Actions6

Record → Update Record

AI-generated

Overview

The node integrates with the Teable API, a database platform with a spreadsheet-like interface. Specifically, the "Update Record" operation under the "Record" resource allows users to update existing records in a specified table by providing the record's unique identifier and the fields to modify.

This node is beneficial when you need to programmatically update data entries in your Teable tables, such as modifying user information, updating inventory counts, or changing status flags based on workflow conditions.

Example use case:
You have a customer management table and want to update a customer's contact details automatically after receiving new information from a form submission.

Properties

Name Meaning
Table ID The unique identifier of the table where the record exists. Found in the table URL or API documentation.
Record ID The unique identifier of the record to update within the specified table.
Fields JSON object specifying the fields to update and their new values. Example: {"Name": "John Doe", "Age": 31}.
Additional Options Collection of optional settings:
- Field Key Type: Specifies how field keys are identified; options are "Name", "ID", or "DB Field Name". Default is "Name".
- Typecast: Boolean flag indicating whether to automatically convert field value types (e.g., string to number). Default is false.

Output

The node outputs JSON data representing the updated record as returned by the Teable API. This typically includes the record's unique identifier and the updated field values reflecting the changes made.

If the node supports binary data output, it is not indicated here and likely not applicable for this operation.

Dependencies

  • Requires an active connection to the Teable API.
  • Needs an API authentication token or key configured in n8n credentials to authorize requests.
  • The base URL for the API is taken from the credential configuration.

Troubleshooting

  • Common issues:

    • Invalid or missing Table ID or Record ID will cause the update to fail.
    • Incorrectly formatted JSON in the "Fields" property can lead to parsing errors.
    • Using wrong field key type may result in fields not being recognized or updated.
    • Lack of proper API credentials or expired tokens will cause authentication errors.

  • Error messages and resolutions:

    • "Record not found": Verify that the Record ID and Table ID are correct and exist in the target database.
    • "Invalid JSON format": Ensure the "Fields" input is valid JSON.
    • "Unauthorized" or "Authentication failed": Check that the API key or token is correctly set up and has necessary permissions.
    • "Field key type mismatch": Adjust the "Field Key Type" option to match how your fields are identified in the table schema.

Links and References

Discussion