Actions21
- App Actions
- Table Actions
- View Actions
- Record Actions
- Field Actions
Overview
The "Lark Base" node serves as a foundational integration point for interacting with the Lark Suite API. It is designed to facilitate communication with Lark's open APIs by managing authentication and request setup. This node is useful when building workflows that require sending requests to Lark services, such as messaging, calendar events, or user management, by providing a base configuration and authentication handling.
Typical use cases include:
- Automating interactions with Lark Suite applications.
- Sending messages or notifications through Lark.
- Managing users or organizational data within Lark.
- Integrating Lark functionalities into broader automation workflows.
Properties
Name | Meaning |
---|---|
Authentication | Method of authenticating API requests. Options: "Tenant Token" (using a tenant token) or "OAuth2" (using OAuth2 authentication). |
Options | Additional optional settings for the request. |
- Use Custom Body | Boolean flag indicating whether to send a custom request body instead of the default one. |
Output
The node outputs data in JSON format representing the response from the Lark Suite API based on the executed request. The structure of this JSON depends on the specific API endpoint called but generally includes standard API response fields such as status codes, messages, and data payloads.
There is no indication that the node outputs binary data.
Dependencies
- Requires an active connection to the Lark Suite API.
- Needs either a Tenant Token credential or OAuth2 credential configured in n8n for authentication.
- Uses the base URL
https://open.larksuite.com/open-apis
for all API requests. - Requires proper API credentials set up in n8n’s credential manager.
Troubleshooting
- Authentication errors: Ensure that the correct authentication method is selected and that the corresponding credentials are valid and not expired.
- API request failures: Check network connectivity and verify that the API endpoint is accessible.
- Invalid custom body: If "Use Custom Body" is enabled, ensure the custom body is correctly formatted as per Lark API specifications.
- Missing required properties: Make sure all mandatory parameters for the intended API call are provided.