Actions32
- Calendar Actions
- Acl Actions
- Event Actions
- Event Attendee Actions
- Event Attendee Chat Member Actions
- Freebusy Actions
- Timeoff Actions
- Setting Actions
- Exchange Binding Actions
Overview
The node "Lark Calendar" provides integration with the Lark Calendar service, enabling users to manage calendar events programmatically. Specifically, the "Subscribe To Event Changes" operation under the "Event" resource allows users to subscribe to changes in a specified calendar's events. This is useful for scenarios where you want to react to event updates, creations, or deletions in real-time or near-real-time, such as syncing calendar data with another system, triggering workflows on event changes, or monitoring calendar activity.
Practical examples include:
- Automatically updating a CRM system when a calendar event is modified.
- Sending notifications or reminders when new events are added.
- Logging event changes for audit purposes.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating API requests. Options: "Tenant Token" (using a tenant-level API token) or "OAuth2" (using OAuth2 authentication flow). |
| Calendar Id | The unique identifier of the calendar to subscribe to. Required to specify which calendar's event changes to monitor. |
| Use Custom Body | Boolean flag indicating whether to send a custom JSON body in the subscription request instead of the default structure. |
| Custom Body | A JSON object representing a custom request body to send when subscribing to event changes. Only used if "Use Custom Body" is enabled (true). |
Output
The node outputs JSON data representing the response from the Lark Calendar API after attempting to subscribe to event changes. This typically includes confirmation details about the subscription, such as subscription ID, status, and any metadata returned by the API.
If the node supports binary data output (not indicated here), it would represent attachments or files related to calendar events, but this operation primarily deals with JSON responses.
Dependencies
- Requires access to the Lark Suite Open APIs endpoint at
https://open.larksuite.com/open-apis. - Requires either a Tenant Token credential or OAuth2 credentials configured in n8n for authentication.
- No additional external dependencies beyond standard HTTP requests to the Lark API.
Troubleshooting
- Invalid Calendar Id: If the provided calendar ID is incorrect or does not exist, the API will return an error. Verify the calendar ID against Lark documentation or your account.
- Authentication Errors: Using invalid or expired tokens will cause authentication failures. Ensure that the Tenant Token or OAuth2 credentials are valid and have appropriate permissions.
- Custom Body Issues: When using a custom body, malformed JSON or missing required fields may cause the API to reject the request. Validate the JSON syntax and required parameters.
- API Rate Limits: Frequent subscription attempts might hit rate limits imposed by Lark API. Implement retry logic or backoff strategies if needed.
- Network Issues: Connectivity problems can cause request failures. Check network settings and proxy configurations if applicable.
Links and References
- Lark Calendar API Documentation — For details on calendar-related IDs and API usage.
- Lark Suite Developer Portal — Official developer resources and API references.