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 interacts with the Lark Calendar API to obtain a list of invitees (attendees) for a specific calendar event. This is useful in scenarios where you need to retrieve detailed information about who has been invited to an event, such as for attendance tracking, sending reminders, or syncing event participants with other systems.
Practical examples:
- Automatically fetching the attendee list after creating or updating an event to update your CRM or communication tools.
- Generating reports on event participation by extracting invitee details.
- Sending personalized follow-up emails to all event invitees.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method used to authenticate API requests. Options: Tenant Token, OAuth2 |
| Calendar Id | The unique identifier of the calendar containing the event. Required to specify which calendar's event attendees to fetch. |
| Event Id | The unique identifier of the event whose invitee list is to be obtained. Required to specify the exact event. |
| Options | Additional optional settings. Currently supports: Use Custom Body (boolean) - whether to send a custom request body instead of the default format. |
Output
The node outputs JSON data representing the list of invitees for the specified calendar event. This typically includes details such as attendee names, email addresses, response status (accepted, declined, etc.), and possibly roles or permissions related to the event.
If binary data output is supported (not indicated here), it would represent attachments or related files, but this node primarily deals with JSON invitee data.
Dependencies
- Requires access to the Lark Suite Open API endpoint at
https://open.larksuite.com/open-apis. - Needs authentication via either a Tenant Token or OAuth2 credentials configured within n8n.
- Proper configuration of API credentials in n8n is necessary to authorize requests.
Troubleshooting
Common issues:
- Invalid or expired authentication tokens leading to authorization errors.
- Incorrect or missing Calendar Id or Event Id causing "not found" or "bad request" errors.
- Network connectivity problems preventing API calls.
Error messages and resolutions:
- 401 Unauthorized: Check that the API credentials are correctly set up and have not expired.
- 404 Not Found: Verify that the Calendar Id and Event Id are correct and exist in the Lark Calendar.
- 400 Bad Request: Ensure required parameters are provided and formatted properly.
- Timeouts or network errors: Confirm internet connectivity and API endpoint availability.
Links and References
- Lark Calendar API Documentation — For details on Calendar and Event IDs and API usage.
- n8n Credentials Setup — Guide on configuring API credentials in n8n.