Dingtalk Node icon

Dingtalk Node

Interact with the Dingtalk API

Overview

This node operation updates an existing AI table (a data sheet) in the Dingtalk platform. It allows users to modify properties of a specified data table, such as renaming it or changing other attributes by sending a JSON request body with the desired updates.

Common scenarios where this node is beneficial include:

  • Automating updates to data tables managed within Dingtalk without manual intervention.
  • Integrating Dingtalk AI tables with other systems to keep data synchronized.
  • Renaming or modifying metadata of data sheets programmatically as part of workflows.

For example, you might use this node to rename a data sheet after processing its contents or to update its configuration based on external triggers.

Properties

Name Meaning
AI表格ID (baseId) The unique identifier of the AI table (base). Can be obtained via the "Parse URL" operation.
数据表ID或名称 (sheetIdOrName) The ID or name of the specific data sheet to update. Also retrievable via the "Parse URL" operation.
操作人的 unionId (operatorId) The unionId of the operator performing the update. Obtainable from user management queries.
请求体 JSON (body) A JSON object representing the update payload. For example, {"name":"New Sheet Name"}. See official API docs for supported fields.

Output

The output of this node is a JSON object reflecting the response from the Dingtalk API after attempting to update the data sheet. This typically includes confirmation of the updated properties or error details if the update failed.

No binary data output is produced by this operation.

Dependencies

  • Requires an active connection to the Dingtalk API with appropriate authentication credentials (an API key or token).
  • The node depends on correct IDs for the AI table and data sheet, which can be retrieved using other operations like "Parse URL".
  • The operator's unionId must be valid and authorized to perform updates on the target data sheet.

Troubleshooting

  • Invalid or missing IDs: Ensure that the baseId and sheetIdOrName are correctly provided and correspond to existing resources in Dingtalk.
  • Unauthorized operator: The operatorId must have permission to update the specified data sheet; otherwise, the API will reject the request.
  • Malformed JSON body: The body property must be valid JSON matching the expected schema. Invalid JSON or unsupported fields will cause errors.
  • API errors: Network issues or API rate limits may cause failures. Check connectivity and API usage quotas.
  • Error messages typically include descriptive text from the Dingtalk API, such as "not found", "unauthorized", or "invalid parameter". Use these messages to adjust input parameters accordingly.

Links and References

Discussion