Dingtalk Node icon

Dingtalk Node

Interact with the Dingtalk API
Join our community

Actions16

Overview

This node integrates with the AI表格 (AI Table) service to update a specific field within a table. It is designed for scenarios where users need to programmatically modify metadata or properties of fields in an AI-powered spreadsheet or database, such as renaming a field or changing its options.

Practical examples include:

  • Updating the name of a column in an AI table.
  • Modifying the selectable choices of a dropdown field.
  • Adjusting field properties dynamically based on external data or user input.

This operation is useful in automated workflows that manage AI表格 structures without manual intervention.

Properties

Name Meaning
AI表格ID (baseId) The unique identifier of the AI表格 base. Can be obtained via the "解析URL" (Parse URL) operation.
数据表ID或名称 (sheetIdOrName) The ID or name of the sheet within the AI表格 base. Also retrievable via the "解析URL" operation.
字段ID或字段名称 (fieldIdOrName) The ID or name of the field (column) to update within the specified sheet.
操作人的 unionId (operatorId) The unionId of the operator performing the update. This can be fetched from user management details.
请求体 JSON (body) A JSON object representing the request body for the update. Typically includes new field name and properties like choices. Example:
json { "name": "字段名", "property": { "choices": [ { "name": "选项一" }, { "name": "选项二" } ] } }

Output

The node outputs JSON data representing the response from the AI表格 API after attempting to update the field. This typically includes confirmation of the updated field's properties or error information if the update failed.

No binary data output is involved.

Dependencies

  • Requires an active connection to the AI表格 API.
  • Needs an API authentication token or key configured in n8n credentials to authorize requests.
  • The operatorId must correspond to a valid user in the system.
  • The node relies on correct IDs/names for base, sheet, and field to function properly.

Troubleshooting

  • Common issues:

    • Invalid or missing baseId, sheetIdOrName, or fieldIdOrName will cause the update to fail.
    • Incorrect operatorId may result in authorization errors.
    • Malformed JSON in the body property can lead to request rejection.
    • Network or API downtime can cause connectivity errors.

  • Error messages and resolutions:

    • "Operation "<operation>" not found": Indicates the selected operation is invalid or not implemented; verify the operation name.
    • API errors related to permissions usually mean the provided operatorId lacks rights; check user permissions.
    • JSON parsing errors suggest the body input is not valid JSON; validate the JSON format before running.
    • If the node throws errors about missing credentials, ensure the API key/token is correctly set up in n8n.

Links and References

Discussion