Lark Auth

Lark Auth Management

Actions10

Api Access Token Actions
- Code2sessionused In Gadget Scenarios
Store App Actions
Custom App Actions
- Get Appaccesstoken
- Get Tenantaccesstoken
User ID Actions

Overview

This node, named "Lark Auth," is designed to manage authentication for the Lark platform within n8n workflows. It provides a way to authenticate API requests to Lark services using either a Tenant Token or OAuth2 method. This node is beneficial when you need to integrate Lark's APIs securely and flexibly in your automation workflows, such as sending messages, managing users, or accessing other Lark resources that require authenticated access.

Practical examples include:

Automating message sending in Lark chats by authenticating with a Tenant Token.
Accessing user profile information or calendar events via OAuth2 authentication.
Managing Lark workspace resources programmatically with secure token management.

Properties

Name	Meaning
Authentication	Method of authentication to use: either "Tenant Token" or "OAuth2".
Options	Additional options for the request:
- Use Custom Body	Boolean flag indicating whether to use a custom request body instead of default format.

Output

The node outputs data in JSON format representing the response from the Lark API after authentication or related operations. The exact structure depends on the specific API call made downstream but generally includes authentication tokens or confirmation of successful authentication setup.

There is no indication that this node outputs binary data.

Dependencies

Requires an API key credential for either Tenant Token or OAuth2 authentication configured in n8n.
Connects to the Lark Open Platform API at https://open.larksuite.com.
Uses standard HTTP headers for JSON content type and accepts JSON responses.

Troubleshooting

Common issues:
- Incorrect or expired credentials will cause authentication failures.
- Misconfiguration of the authentication method (e.g., selecting OAuth2 but not providing required OAuth2 credentials) can lead to errors.
Error messages:
- Authentication errors typically indicate invalid tokens or missing permissions.
- Network or connectivity errors may occur if the base URL is unreachable.
Resolutions:
- Verify that the correct authentication method is selected and credentials are valid.
- Ensure network connectivity to the Lark API endpoint.
- Check that any required scopes or permissions are granted for OAuth2 tokens.