Lark Calendar icon

Lark Calendar

Lark Calendar Management

Overview

This node interacts with the Lark Calendar API to obtain the list of members who are group invitees (attendees) of a specific calendar event. It is useful when you want to retrieve detailed information about all participants invited as a group to an event, such as for managing communications, attendance tracking, or syncing attendee data with other systems.

Practical examples:

  • Fetching all members of a group invitee to send them notifications or reminders.
  • Integrating event attendee data into CRM or collaboration tools.
  • Auditing or reporting on event participation by group members.

Properties

Name Meaning
Authentication Method of authentication to use: either "Tenant Token" or "OAuth2".
Calendar Id The unique identifier of the calendar containing the event.
Event Id The unique identifier of the event whose group invitee members you want to list.
Attendee Id The unique identifier of the group invitee (attendee) whose member list you want to obtain.
Options Additional options; currently supports:
- Use Custom Body Boolean flag indicating whether to send a custom request body instead of the default one (default is false).

Output

The node outputs JSON data representing the list of members belonging to the specified group invitee of the event. This typically includes details such as member IDs, names, and possibly their roles or statuses within the group.

If binary data were involved (not indicated here), it would represent attachments or media related to the attendees, but this node focuses on JSON attendee data only.

Dependencies

  • Requires access to the Lark Suite Calendar API.
  • Needs either a Tenant Token or OAuth2 credentials configured in n8n for authentication.
  • Network connectivity to https://open.larksuite.com/open-apis.

Troubleshooting

  • Missing or invalid IDs: Ensure that the Calendar Id, Event Id, and Attendee Id are correct and correspond to existing entities in your Lark Calendar.
  • Authentication errors: Verify that the selected authentication method is properly configured and the token or OAuth credentials are valid and have sufficient permissions.
  • API rate limits or network issues: If requests fail intermittently, check for API rate limiting or network connectivity problems.
  • Use Custom Body option: If enabled incorrectly without providing a proper body, the request may fail. Use this option only if you know the exact request payload structure required.

Links and References

Discussion