Actions3
- Api Reference Actions
Overview
This node, named "Lark Approval," is designed to manage approval workflows within the Lark platform. It allows users to interact with Lark's approval system, which is useful for automating and integrating approval processes such as leave requests, expense approvals, or any custom workflow that requires authorization steps.
Common scenarios include:
- Automating submission and tracking of approval requests.
- Integrating Lark approval data into other systems or workflows.
- Customizing approval handling based on dynamic inputs.
Practical example: A company could use this node to automatically submit employee leave requests to Lark’s approval system and then route the approval status back into their internal HR software.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method used to authenticate API requests. Options: Tenant Token, OAuth2 |
| Options | Additional options for the request |
| - Use Custom Body | Boolean flag indicating whether to send a custom request body instead of default format |
Output
The node outputs JSON data representing the response from the Lark Approval API. This typically includes details about approval requests, statuses, or results of operations performed (e.g., creating or retrieving approval workflows).
If binary data were involved (not indicated here), it would represent files or attachments related to approvals, but this node focuses on JSON responses.
Dependencies
- Requires an API authentication token, either via a Tenant Token or OAuth2 credentials configured in n8n.
- Connects to the Lark Suite Open API endpoint at
https://open.larksuite.com/open-apis. - No additional external dependencies beyond standard HTTP requests.
Troubleshooting
- Authentication errors: Ensure the correct authentication method is selected and valid credentials are provided.
- API request failures: Check network connectivity and verify that the Lark API service is operational.
- Invalid custom body: If using the "Use Custom Body" option, ensure the JSON structure matches the expected API schema to avoid request rejections.
- Permission issues: The authenticated user or token must have sufficient permissions to perform approval-related actions in Lark.