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 is designed to manage permissions of collaborators on files within the Lark (Feishu) ecosystem, specifically focusing on deleting permissions for a collaborator on a document or file. It allows users to revoke access rights from a specified member by identifying the file and the member whose permissions should be removed.
Common scenarios include:
- Removing a user's editing or viewing rights from a shared document.
- Managing access control in automated workflows where permissions need to be updated dynamically.
- Ensuring compliance by revoking permissions when a collaborator no longer requires access.
For example, an organization might use this node to automatically remove a contractor's access to project documents once their contract ends.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating API requests. Options: "Tenant Token" or "OAuth2". |
| Type | The type of the file, passed as a query parameter (e.g., doc). This helps specify the kind of file whose permissions are being managed. |
| Member Type | The category/type of the member whose permissions are to be deleted. This is included as a query parameter and corresponds to the member ID provided. |
| Token | Required. The unique token identifier of the file. This token is necessary to identify the specific file for which permissions will be deleted. |
| Member Id | Required. The identifier of the member whose permissions are to be deleted. This must correspond to the specified member type. |
| Options | Additional optional settings. Currently supports: - Use Custom Body (boolean): Whether to send a custom request body instead of the default. |
Output
The node outputs JSON data representing the result of the permission deletion operation. Typically, this would include confirmation of success or details about any errors encountered during the process.
If the node supports binary data output, it would relate to file content or metadata, but based on the provided information, the output focuses on JSON responses from the API regarding permission management.
Dependencies
- Requires authentication via either a Tenant Token or OAuth2 credentials to access the Lark Suite APIs.
- Depends on the Lark Suite Open API endpoint at
https://open.larksuite.com/open-apis. - Proper configuration of credentials in n8n is necessary to authorize API calls.
Troubleshooting
- Invalid or missing token: If the file token is incorrect or missing, the API call will fail. Ensure the token is correctly obtained and provided.
- Incorrect member ID or type: Mismatched or invalid member identifiers can cause errors. Verify that the member ID corresponds to the specified member type.
- Authentication errors: Using expired or invalid credentials will prevent successful API calls. Refresh or reconfigure authentication tokens as needed.
- API rate limits or network issues: Temporary failures may occur due to rate limiting or connectivity problems. Implement retries or check network status.
- Custom body usage: If "Use Custom Body" is enabled but the body is malformed or incomplete, the request may fail. Validate custom payloads carefully.