Dingtalk Node icon

Dingtalk Node

Interact with the Dingtalk API
Join our community

Actions16

Overview

This node interacts with the AI表格 (AI Spreadsheet) service via the Dingtalk API to create new data tables within an AI spreadsheet base. It is useful when you want to programmatically add structured data tables to your AI spreadsheets, for example, automating the creation of new sheets based on dynamic input or workflow conditions.

Typical use cases include:

  • Automatically generating new data tables in AI spreadsheets as part of a larger automation pipeline.
  • Creating customized data tables for different projects or users without manual intervention.
  • Integrating AI spreadsheet table creation into business workflows that require dynamic data organization.

Properties

Name Meaning
AI表格ID (baseId) The unique identifier of the AI spreadsheet base where the new data table will be created. This ID can be obtained using the "解析URL" operation of AI表格.
操作人的 unionId (operatorId) The unionId of the operator performing the action. This can be retrieved from user management by querying user details.
请求体 JSON (body) The JSON request body defining the new data table's properties. By default, it contains {"name":"新建数据表"}. Refer to the official API documentation for full schema details.

Output

The node outputs JSON data representing the response from the AI表格 API after attempting to create the new data table. This typically includes information about the newly created sheet such as its ID, name, and other metadata returned by the API.

No binary data output is produced by this node.

Dependencies

  • Requires an API key credential for authenticating with the Dingtalk API.
  • The node depends on the Dingtalk AI表格 API endpoint for creating sheets.
  • Proper configuration of the API authentication token in n8n credentials is necessary.
  • The user must have valid AI表格 baseId and operatorId values to perform the operation.

Troubleshooting

  • Common issues:

    • Invalid or missing baseId or operatorId will cause the API call to fail.
    • Malformed JSON in the body property may result in request errors.
    • Insufficient permissions or expired API tokens can lead to authorization errors.

  • Error messages:

    • "Operation "<operation>" not found": Indicates the specified operation is not implemented or incorrectly named.
    • API error responses will be passed through in the output JSON under an error field if "Continue On Fail" is enabled.

  • Resolutions:

    • Verify that baseId and operatorId are correct and current.
    • Ensure the JSON in body matches the expected schema from the official API docs.
    • Check that the API key credential is valid and has required scopes.
    • Enable "Continue On Fail" to handle errors gracefully during batch executions.

Links and References

Discussion