Actions3
- Api Reference Actions
Overview
The "Approval Task Addsign" operation in the Lark Approval node allows users to add additional signatories (approvers) to an existing approval task within the Lark Suite platform. This is useful in scenarios where an approval process requires more reviewers after it has started, such as when new stakeholders need to be involved or compliance demands extra verification.
Practical examples include:
- Adding a manager or department head to an ongoing expense approval.
- Including legal or compliance officers to review contracts mid-process.
- Dynamically adjusting approval workflows based on evolving project requirements.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating API requests; options are "Tenant Token" or "OAuth2". |
| Add Sign Type | Numeric code indicating the type of add sign action (e.g., 0 for normal add sign). |
| Add Sign User Ids | List of user IDs to be added as additional approvers to the task. |
| Approval Code | Code representing the approval action or status. |
| Approval Method | Numeric code specifying the method of approval (e.g., manual, automatic). |
| Comment | Optional comment or note accompanying the add sign request. |
| Instance Code | Identifier for the approval instance related to the task. |
| Task Id | Unique identifier of the approval task to which signatories are being added. |
| User Id | ID of the user performing the add sign operation. |
| Custom Body | JSON object allowing full customization of the request body instead of using individual fields. |
| Options: Use Custom Body | Boolean flag to determine whether to send a custom JSON body instead of structured fields. |
Output
The node outputs JSON data representing the response from the Lark Suite API after attempting to add signatories to the approval task. This typically includes confirmation of the operation's success, updated task details, or error information if the operation failed.
If binary data were returned by the API (not indicated here), it would represent file attachments or similar content related to the approval task.
Dependencies
- Requires valid authentication credentials via either a Tenant Token or OAuth2 token configured in n8n.
- Depends on access to the Lark Suite Open APIs endpoint at
https://open.larksuite.com/open-apis. - Proper permissions in the Lark Suite environment to modify approval tasks and add signatories.
Troubleshooting
Common Issues:
- Invalid or expired authentication tokens causing authorization failures.
- Incorrect or missing Task Id or Instance Code leading to "task not found" errors.
- User IDs provided in Add Sign User Ids not existing or lacking permission to approve.
- Misformatted custom JSON body causing request validation errors.
Error Messages & Resolutions:
- 401 Unauthorized: Check that the API credentials are correct and have not expired.
- 404 Not Found: Verify that the Task Id and Instance Code correspond to an active approval task.
- 400 Bad Request: Ensure all required fields are correctly formatted; if using custom body, validate JSON structure.
- Permission Denied: Confirm that the authenticated user has rights to add signatories to the specified task.