Lark Auth

Overview

This node is designed to obtain the logged-in user's ID from the Lark platform. It supports two authentication methods: using a Tenant Token or OAuth2. The node can either send a default request or allow users to provide a custom JSON body for more advanced use cases.

Common scenarios include:

• Identifying the current user in workflows that require user-specific data.
• Automating processes that depend on the authenticated user's identity.
• Integrating with other systems where the user ID is needed as a reference.

For example, a workflow might start by obtaining the logged-in user's ID and then use it to fetch user details or permissions in subsequent steps.

Properties

Output

The node outputs JSON data containing the logged-in user's ID and potentially other related user information returned by the Lark API. The exact structure depends on the API response but typically includes fields such as user ID, name, email, and other profile details.

No binary data output is involved.

Dependencies

• Requires valid authentication credentials: either a Tenant Token or OAuth2 token configured in n8n.
• Connects to the Lark Open Platform API at https://open.larksuite.com.
• No additional external dependencies beyond standard HTTP requests.

Troubleshooting

• Authentication errors: Ensure that the provided Tenant Token or OAuth2 credentials are valid and have the necessary permissions.
• Invalid custom body: If using a custom JSON body, verify that the JSON is correctly formatted and matches the expected API schema.
• API connectivity issues: Check network access to the Lark API endpoint and confirm no firewall or proxy blocks exist.
• Unexpected API responses: Review the API documentation to ensure the request parameters and body align with the latest API version.

Links and References

• Lark Open Platform API Documentation
• Lark Authentication Guide