Feishu Node

Overview

This node interacts with a calendar service to retrieve the list of attendees for a specific calendar event. It is useful in scenarios where you need to manage or analyze participants of meetings or events, such as sending notifications, tracking attendance, or integrating attendee data into other workflows.

For example, you might use this node to:

• Fetch all participants of a scheduled meeting to send them follow-up emails.
• Retrieve attendee information to update an internal CRM system.
• Analyze participation trends by extracting attendee lists from multiple events.

Properties

Name	Meaning
日历 ID	The ID of the calendar containing the event. This can be obtained via APIs that fetch primary calendar info, list calendars, or search calendars.
日程 ID	The ID of the event whose attendees you want to list. This can be retrieved through event creation, event listing, or event search APIs.
需要会议室表单信息	Boolean flag indicating whether to include meeting room form information in the response.
分页标记	Pagination token used to fetch subsequent pages of attendees. Leave empty on the first request; if more results exist, the response will provide a new token to continue fetching.
每页数量	Maximum number of attendees to return per request. Minimum is 10, maximum is 100. Defaults to 20.
用户 ID 类型	Type of user ID to return for each attendee. Options are: Open ID, Union ID, or User ID. Default is Open ID.

Output

The node outputs a JSON array where each item represents an attendee of the specified calendar event. Each attendee object includes user identification fields according to the selected user ID type and may include additional details such as meeting room form information if requested.

If pagination is involved, the output may also contain tokens or metadata to facilitate fetching further pages of attendees.

No binary data output is produced by this node.

Dependencies

• Requires an API key credential for authenticating with the calendar service.
• The node depends on the calendar service's API endpoints to fetch calendar and event data.
• Proper configuration of credentials within n8n is necessary to authorize requests.

Troubleshooting

• Common issues:

  • Invalid or missing calendar ID or event ID will cause the API call to fail.
  • Incorrect user ID type selection may result in unexpected or empty user identifiers.
  • Pagination tokens must be managed correctly; using an invalid or expired token will lead to errors.
  • Requesting too many attendees per page (above 100) may be rejected by the API.

• Error messages:

  • Errors related to authentication usually indicate misconfigured or expired API credentials.
  • "未实现方法" (Unimplemented method) error indicates that the requested resource-operation combination is not supported by the node.
  • Network or API errors should be checked for connectivity and API quota limits.

• Resolutions:

  • Verify calendar and event IDs are correct and accessible.
  • Ensure API credentials are valid and have sufficient permissions.
  • Use pagination tokens as provided by previous responses without modification.
  • Adjust 每页数量 to be within allowed limits.

Links and References

• Official Calendar API documentation (for obtaining calendar and event IDs, and understanding attendee data).
• n8n documentation on managing credentials and pagination handling.
• General best practices for working with paginated API responses.