Apitable icon

Apitable

Interact with Apitable API

Actions11

Record → Record Update

AI-generated

Overview

This node operation updates records in a specified datasheet within the Apitable platform. It allows users to modify existing records by specifying the datasheet, the records to update (including field values), and optional parameters such as which view to use or how fields are identified.

Common scenarios where this node is beneficial include:

  • Automating bulk updates of data entries in a collaborative table.
  • Synchronizing external data sources with Apitable records.
  • Modifying specific fields of records based on dynamic input during workflow execution.

For example, you might use this node to update the status of multiple project tasks stored in an Apitable datasheet or to correct data entries after validation.

Properties

Name Meaning
Datasheet Id The unique identifier of the Apitable datasheet where records will be updated.
Records JSON array containing the record objects to update, including field keys and their new values.
Field Key The key used to identify fields when querying and returning them; options are "Name" or "Id".
Additional Fields Optional extra parameters; currently supports specifying a View Id to filter records and fields returned.

Output

The node outputs JSON data representing the result of the record update operation. This typically includes confirmation of updated records and any relevant metadata returned by the Apitable API.

If binary data were involved, it would represent file attachments or similar content, but this operation focuses on JSON record data only.

Dependencies

  • Requires an API key credential for authenticating with the Apitable API.
  • Needs the base URL of the Apitable instance configured in credentials.
  • Uses internal methods to load options dynamically for Datasheets and Views, ensuring up-to-date selectable options.

Troubleshooting

  • Invalid Datasheet Id: If the provided datasheet ID does not exist or is incorrect, the API will return an error. Verify the datasheet ID is correct and accessible.
  • Malformed Records JSON: The Records property expects valid JSON. Errors parsing this input will cause failures. Ensure the JSON syntax is correct.
  • Field Key Mismatch: Using the wrong field key ("name" vs "id") may lead to fields not being found. Confirm the correct key type matches your datasheet schema.
  • Missing API Credentials: Without proper authentication, requests will fail. Make sure the API key credential is set up correctly.
  • View Id Filtering Issues: Specifying a view that does not exist or is inaccessible can cause empty results or errors. Double-check the view ID if used.

Links and References

Discussion