Lark Calendar icon

Lark Calendar

Lark Calendar Management

Actions32

Overview

The "Unsubscribe From A Calendar" operation in the Lark Calendar node allows users to remove their subscription from a specified calendar. This is useful when you no longer want to receive updates or view events from that calendar within your Lark environment. Typical scenarios include managing calendar subscriptions for team members, cleaning up unused calendars, or automating calendar management workflows.

For example, an organization might automate unsubscribing employees from project-specific calendars once a project ends, ensuring their calendar views remain relevant and uncluttered.

Properties

Name Meaning
Authentication Method of authenticating API requests. Options: Tenant Token, OAuth2.
Calendar Id The unique identifier of the calendar to unsubscribe from. Required to specify which calendar to unsubscribe.
Use Custom Body Boolean option to indicate whether to send a custom JSON body with the request instead of the default.
Custom Body A JSON object representing a custom request body to send if "Use Custom Body" is enabled. Allows advanced users to override the default payload.

Output

The node outputs JSON data representing the response from the Lark Calendar API after attempting to unsubscribe from the specified calendar. This typically includes confirmation of the unsubscription or error details if the operation failed.

No binary data output is involved in this operation.

Dependencies

  • Requires valid authentication credentials via either:
    • A tenant token credential.
    • An OAuth2 credential.
  • The node communicates with the Lark Suite Open APIs at https://open.larksuite.com/open-apis.
  • Proper configuration of these credentials in n8n is necessary for successful API calls.

Troubleshooting

  • Common Issues:

    • Invalid or expired authentication tokens can cause authorization failures.
    • Incorrect or missing Calendar Id will result in errors indicating the calendar cannot be found.
    • Using a malformed custom JSON body may lead to request validation errors.

  • Error Messages:

    • Authorization errors: Check that the provided API key or OAuth2 token is valid and has sufficient permissions.
    • Not Found errors: Verify the Calendar Id is correct and accessible by the authenticated user.
    • Bad Request errors: If using a custom body, ensure the JSON structure matches the API requirements.

Resolving these usually involves verifying credentials, confirming calendar identifiers, and validating any custom JSON payloads.

Links and References

Discussion