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
The "Lark Files" node enables interaction with Lark's file management system, specifically supporting operations such as uploading files. The "Upload A File" operation allows users to send a file to Lark's platform, which is useful for automating document storage, sharing, or integration workflows involving Lark Docs or other file-based resources within the Lark ecosystem.
Typical use cases include:
- Automatically uploading generated reports or documents to Lark for team collaboration.
- Integrating external systems to push files into Lark without manual intervention.
- Managing file uploads in bulk or as part of larger automation sequences.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method used to authenticate API requests. Options: "Tenant Token" or "OAuth2". |
| Use Custom Body | Boolean flag indicating whether to send a custom JSON body instead of the default structure. |
| Custom Body | JSON object representing a custom request body to be sent when "Use Custom Body" is enabled. |
Output
The node outputs JSON data representing the response from the Lark API after attempting to upload a file. This typically includes metadata about the uploaded file such as its ID, name, size, and URLs for access or further manipulation.
If binary data is involved (e.g., the file content), it would be handled accordingly, but based on the provided code and properties, the focus is on JSON responses describing the upload result rather than returning the file content itself.
Dependencies
- Requires an API authentication token, either via a Tenant Token or OAuth2 credentials configured in n8n.
- Connects to Lark's open API endpoint at
https://open.larksuite.com/open-apis. - No additional external dependencies are indicated beyond standard HTTP requests to Lark's API.
Troubleshooting
- Authentication errors: Ensure that the correct authentication method is selected and valid credentials are provided. Expired or invalid tokens will cause failures.
- Invalid custom body: If "Use Custom Body" is enabled, ensure the JSON provided is correctly formatted and matches the expected schema by Lark's API.
- File upload failures: Check network connectivity and API limits. Also verify that the file data and metadata conform to Lark's requirements.
- Unexpected API responses: Enable detailed logging or inspect raw responses to diagnose issues related to permissions or malformed requests.