Dingtalk NodeInstall

Summary

Update an approval instance of a Dingtalk OA workflow process by submitting form data or a raw JSON body to modify its variables and remark.

Inputs

• sendBody — Choose between sending the request body as defined form fields or as raw JSON.
• jsonBody — Provide the entire request body as JSON (used only if 'sendBody' is set to 'json').
• opUserId (required) — User ID of the operator making the update; must be an administrator.
• processCode — Unique code of the approval process, obtainable from the approval form's basic settings page.
• processInstanceId (required) — ID of the specific process instance to update.
• variables (required) — Mappings for approval form controls to their new values; supports setting extended values via objects.
• remark — Optional remark or comment to accompany the update.

Output shape

a JSON object representing the updated approval instance or the API response indicating success or failure

Send the request either using structured form data or raw JSON body according to the 'sendBody' parameter. The operation requires administrator privileges for the operator user ID and must specify the process instance ID. Variables are mapped dynamically based on the approval form controls of the specified processCode.

Examples

Example 1: Update an approval instance using form fields

Set sendBody to 'form', provide opUserId, processCode, processInstanceId, map variables for form fields, and optionally add a remark. The node updates the approval instance's variable values accordingly.

Example 2: Update an approval instance using raw JSON

Set sendBody to 'json' and supply a complete JSON object in jsonBody that includes opUserId, processCode, processInstanceId, variables, and remark if needed. The node sends this raw JSON as the update data.

Links

• n8n community nodes installation guide