Feishu Node icon

Feishu Node

Feishu Node

Actions106

Overview

This node operation allows users to delete attendees from a specific calendar event in a calendar system. It is useful when managing event participants, such as removing people who are no longer attending or were added by mistake. Typical scenarios include updating meeting invitations, managing event attendance lists, and maintaining accurate participant records.

For example, if an organizer wants to remove several attendees from a recurring meeting or a one-time event, this operation can be used to specify which attendees to delete by their IDs and optionally notify them about the removal.

Properties

Name Meaning
日历 ID (calendar_id) The ID of the calendar where the event is located. This can be obtained via APIs that fetch main calendar info, list calendars, or search calendars.
日程 ID (event_id) The ID of the event from which attendees will be removed. This ID can be retrieved through event creation, listing, or searching APIs.
参与人 ID 列表(string[]) (attendee_ids) A JSON array of attendee IDs to be deleted. Up to 500 attendees can be deleted at once (counting together with delete_ids).
参与人类型 ID 列表(delete_ids对象) (delete_ids) A JSON array of objects specifying attendee types and IDs for deletion. Refer to the official API documentation for the exact structure.
是否发送通知 (need_notification) Boolean flag indicating whether to send notifications to attendees being removed. Defaults to true.
重复日程实例时间戳 (instance_start_time_admin) Timestamp string identifying a specific instance of a recurring event to modify. Only needed when deleting attendees from a particular occurrence of a recurring event; not required for single events.
启用会议室管理员身份 (is_enable_admin) Boolean flag to enable meeting room administrator privileges during the operation. Defaults to false.
用户 ID 类型 (user_id_type) Specifies the type of user ID used in attendee identification. Options are: Open ID, Union ID, or User ID. Default is Open ID.

Output

The output of this operation is a JSON object representing the result of the deletion request. It typically includes confirmation of which attendees were successfully removed or any errors encountered during the process.

If the node supports binary data output (not indicated here), it would represent related files or attachments, but this operation focuses on JSON responses only.

Dependencies

  • Requires an API key credential for authenticating with the calendar service.
  • Depends on the calendar service's API endpoints for managing calendars, events, and attendees.
  • The node uses internal helper methods to construct execution metadata and handle API calls.
  • No additional external libraries beyond those bundled with the node are required.

Troubleshooting

  • Common issues:

    • Providing invalid or expired calendar or event IDs will cause failures.
    • Exceeding the maximum number of attendees to delete (500 combined between attendee_ids and delete_ids) may result in errors.
    • Incorrectly formatted JSON arrays for attendee_ids or delete_ids can cause parsing errors.
    • Attempting to delete attendees from a non-recurring event while providing a timestamp for an instance may be ignored or cause unexpected behavior.
    • Insufficient permissions or missing API credentials will prevent successful API calls.

  • Error messages:

    • Errors indicating "未实现方法" (unimplemented method) suggest the requested resource-operation combination is not supported.
    • API errors returned from the calendar service will be propagated; check the error message for details such as invalid IDs or permission issues.
    • Network or authentication errors should be resolved by verifying API keys and connectivity.

Links and References

Discussion