Feishu Node icon

Feishu Node

Feishu Node

Actions106

Overview

This node interacts with a calendar service to retrieve detailed information about a specific calendar event. It is useful when you need to fetch event details such as the event's metadata, attendees, and video conference settings from a calendar identified by its ID. Typical use cases include synchronizing calendar events with other systems, displaying event details in custom dashboards, or automating workflows based on event data.

For example, you can use this node to:

  • Get the details of a meeting scheduled in a particular calendar.
  • Retrieve attendee information for an event to send reminders or updates.
  • Access video conference settings associated with an event to integrate with communication tools.

Properties

Name Meaning
日历 ID (calendar_id) The ID of the calendar where the event is located. This ID can be obtained through APIs that query the primary calendar info, list calendars, or search calendars.
日程 ID (event_id) The ID of the event to retrieve. This can be obtained via APIs that create events, list events, or search events.
是否需要返回飞书视频会议(VC)的会前设置 (need_meeting_settings) Boolean flag indicating whether to return pre-meeting settings of the Feishu video conference associated with the event.
是否需要返回参与人信息 (need_attendee) Boolean flag indicating whether to return information about the event attendees.
返回的最大参与人数量 (max_attendee_num) The maximum number of attendees to return in the response. Defaults to 10.
用户 ID 类型 (user_id_type) The type of user ID used in the response. Options are: Open ID, Union ID, or User ID. This defines how user identities are represented in the returned data.

Output

The node outputs JSON data representing the detailed information of the requested calendar event. This includes:

  • Event metadata such as title, time, location, description, etc.
  • Optionally, video conference pre-meeting settings if requested.
  • Optionally, attendee information up to the specified maximum number, including their user IDs in the selected format.

If the event contains any binary data (e.g., attachments), it would be included in the binary output field, but this node primarily focuses on JSON event details.

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 permissions/scopes must be granted to the API key to access calendar and event information.
  • No additional external dependencies beyond the configured API credentials and network access to the calendar service.

Troubleshooting

  • Common issues:

    • Invalid or missing calendar ID or event ID will cause the node to fail fetching event data.
    • Insufficient permissions on the API key may result in authorization errors.
    • Requesting attendee information or meeting settings without proper scopes might lead to incomplete data or errors.
    • Exceeding the maximum allowed number of attendees could cause truncation of attendee lists.
  • Error messages:

    • "未实现方法: calendar.getEvent" indicates the operation is not implemented or incorrectly referenced; verify resource and operation names.
    • API errors related to authentication or permission denied should be resolved by checking the API key and its scopes.
    • Network or timeout errors require ensuring stable connectivity to the calendar service.

Links and References

Discussion