Actions3
- Api Reference Actions
Overview
The node "Lark Approval" provides integration with Lark's approval management system, specifically allowing users to query task lists from a user's perspective. This is useful for workflows that need to fetch and process approval tasks assigned to or related to a specific user within an organization using Lark Suite.
A common scenario includes automating the retrieval of pending or completed approval tasks for a user, enabling further processing such as notifications, reporting, or triggering downstream automation based on approval status.
For example, you might use this node to:
- Fetch all pending approval tasks for a user to display in a custom dashboard.
- Retrieve completed tasks to generate reports or audit logs.
- Automate reminders or escalations based on task topics like "Pending" or "Done".
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authentication to use: either "Tenant Token" or "OAuth2". |
| User Id | The ID of the user whose task list you want to query. |
| Topic | The topic/category of the task group to query, e.g., "Pending", "Done", represented by a number (e.g., 1). |
| Options | Additional options: - Use Custom Body: Whether to send a custom request body instead of default parameters. |
Output
The node outputs JSON data representing the list of approval tasks retrieved from Lark's API for the specified user and topic. The structure typically includes details about each task such as task ID, status, title, submitter, timestamps, and other metadata relevant to approval workflows.
If binary data were involved (not indicated here), it would represent attachments or documents related to approval tasks, but this node focuses on JSON task data.
Dependencies
- Requires access to Lark Suite's Open APIs.
- Needs either a Tenant Token or OAuth2 credentials configured in n8n for authentication.
- Network connectivity to
https://open.larksuite.com/open-apis.
Troubleshooting
- Authentication errors: Ensure that the correct authentication method is selected and valid credentials are provided. Expired tokens or incorrect scopes can cause failures.
- Invalid User ID: If the user ID does not exist or is malformed, the API will return an error. Verify the user ID format and existence.
- Topic parameter issues: Using an unsupported topic number may result in empty results or errors. Confirm valid topic values according to Lark's API documentation.
- API rate limits: Excessive requests may be throttled. Implement retry logic or reduce request frequency.
- Custom Body usage: If "Use Custom Body" is enabled, ensure the custom body is correctly formatted; otherwise, the API may reject the request.
Links and References
- Lark Open Platform API Documentation
- Lark Approval API Reference (for detailed info on task topics and parameters)