Actions28
- File Actions
- Multipart Upload File Actions
- Permission Member Actions
- Permissionpublic Actions
- Statistic Actions
- Media Actions
- Multipart Upload Media Actions
- Comment Actions
- Subscription Actions
- Document Import Actions
Overview
This node operation allows users to mark a comment in a document as either solved or restored (unsolved). It is useful in collaborative document editing scenarios where comments represent tasks, questions, or issues that need resolution. By toggling the "solved" status of a comment, team members can track progress and manage feedback efficiently.
Practical examples:
- Marking a comment as solved after addressing the issue it raised.
- Restoring a comment to unsolved if further discussion or action is needed.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authentication to use: either "Tenant Token" or "OAuth2". |
| File Type | The type of the document (e.g., doc, sheet). Optional but used for routing query parameters. |
| File Token | The unique token identifying the document. |
| Comment Id | The numeric ID of the comment to be marked as solved or restored. |
| Is Solved | Boolean flag indicating whether to mark the comment as solved (true) or restored (false). |
| Custom Body | JSON object allowing a custom request body to be sent instead of the default one. |
| Options > Use Custom Body | If enabled, the node will send the Custom Body JSON instead of the standard body. |
Output
The output contains the response from the API call that updates the comment's status. This typically includes confirmation of the updated comment state and any relevant metadata returned by the service. The main data is available in the json field of the output item.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to the Lark Suite API.
- Needs either a Tenant Token or OAuth2 credentials configured in n8n for authentication.
- The base URL for API requests is
https://open.larksuite.com/open-apis.
Troubleshooting
- Invalid or missing File Token: Ensure the file token corresponds to an existing document accessible with your credentials.
- Incorrect Comment Id: Verify the comment ID exists within the specified document.
- Authentication errors: Confirm that the selected authentication method is properly configured and authorized.
- API rate limits or network issues: May cause failures; check connectivity and API usage quotas.
- Using Custom Body: If enabled, ensure the JSON is correctly formatted and contains all required fields expected by the API.
Links and References
- Lark Suite Open API Documentation
- n8n Documentation on HTTP Request Node (for understanding how API calls are made)