Feishu Node icon

Feishu Node

Feishu Node

Actions106

Overview

This node interacts with a calendar service to retrieve a list of scheduled events. It is designed to fetch calendar events based on various filtering and pagination parameters, making it useful for synchronizing or displaying calendar data in workflows. Common scenarios include syncing events from a specific calendar, fetching upcoming events within a time range, or incrementally updating event lists using synchronization tokens.

For example, you can use this node to:

  • Retrieve all events from a particular calendar for the next week.
  • Incrementally sync new or updated events since the last check.
  • Paginate through large sets of events when the number exceeds a single request limit.

Properties

Name Meaning
日历 ID The unique identifier of the calendar. Can be obtained via querying main calendar info, listing calendars, or searching calendars.
每页数量 Maximum number of events to return per request. Valid range: 50 to 1000.
分页标记 Pagination token used to fetch subsequent pages. Leave empty for the first request. When more results are available, a new token is returned for the next page.
时间锚点 A Unix timestamp (in seconds) serving as an anchor point to fetch events occurring after this time.
增量同步标记 Token used for incremental synchronization. Leave empty for the first request. Returned at the end of pagination to be used in subsequent calls to get only changed data.
开始时间 Start of the time range filter as a Unix timestamp (seconds). Used together with End Time to specify the interval for events to retrieve.
结束时间 End of the time range filter as a Unix timestamp (seconds). Used together with Start Time to specify the interval for events to retrieve.
用户 ID 类型 Type of user ID used to identify the user. Options: Open ID, Union ID, User ID. Default is Open ID.

Output

The node outputs a JSON array where each item represents a calendar event retrieved according to the specified filters. Each event object contains details such as event time, title, description, attendees, and other metadata depending on the calendar API's response.

If the calendar service supports binary data (e.g., attachments), the node would handle it accordingly, but based on the provided code and properties, the output focuses on JSON event data.

Dependencies

  • Requires an API key credential for authenticating with the calendar service.
  • The node depends on the calendar API endpoints that provide calendar information and event listings.
  • Proper configuration of credentials and permissions to access the target calendar is necessary.

Troubleshooting

  • Common issues:

    • Invalid or missing calendar ID will cause the node to fail to retrieve events.
    • Incorrect pagination tokens may result in empty or repeated data.
    • Time range parameters must be valid Unix timestamps; otherwise, the API might reject the request.
    • Using an expired or invalid synchronization token can lead to errors or incomplete incremental updates.

  • Error messages:

    • "未实现方法: calendar.calendar:listEvents" indicates the operation is not implemented or incorrectly referenced.
    • API authentication errors suggest checking the API key or token validity.
    • Pagination errors often require resetting the page_token or sync_token.

To resolve these, verify input parameters, ensure correct credential setup, and consult the calendar API documentation for token usage.

Links and References

Discussion