Feishu Node icon

Feishu Node

Feishu Node

Actions106

Overview

This node operation allows you to add attendees to an existing calendar event within a specified calendar. It is useful for scenarios where you need to update meeting participants dynamically, such as inviting additional team members to a scheduled event or modifying attendee lists for recurring meetings.

Practical examples include:

  • Adding new participants to a project status meeting after the event has been created.
  • Inviting external collaborators to an internal calendar event.
  • Managing attendees for recurring events by targeting specific instances.

Properties

Name Meaning
日历 ID (calendar_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 (event_id) The ID of the event to which attendees will be added. Obtainable through event creation, listing, or searching APIs.
参与人列表(attendees对象) (attendees) A JSON array representing the list of new attendees to add. The structure should follow the API specification for event attendees.
是否发送通知 (need_notification) Boolean flag indicating whether to send notifications to the newly added attendees. Defaults to true.
重复日程实例时间戳 (instance_start_time_admin) Timestamp identifying a specific instance of a recurring event to modify. Only required when adding attendees to one instance of a recurring event; leave empty for non-recurring events.
启用会议室管理员身份 (is_enable_admin) Boolean flag to enable meeting room administrator privileges during the operation. Defaults to false.
添加操作人为参与人 (add_operator_to_attendee) Boolean flag to add the user performing the operation as an attendee automatically. Defaults to false.
用户 ID 类型 (user_id_type) Specifies the type of user ID used in the attendees list. Options are: Open ID, Union ID, or User ID. Defaults to Open ID.

Output

The node outputs a JSON object representing the result of the add-attendees operation. This typically includes confirmation details about the updated event and the newly added attendees. The exact structure depends on the underlying API response but generally confirms success or failure and may include updated event metadata.

No binary data output is involved in this operation.

Dependencies

  • Requires an API key credential for authenticating with the calendar service.
  • The node depends on the calendar service's API endpoints for fetching calendar and event IDs and for updating event attendees.
  • Proper permissions must be granted to the API key to modify calendar events and send notifications.

Troubleshooting

  • Common issues:

    • Invalid or missing calendar ID or event ID will cause the operation to fail.
    • Incorrectly formatted attendees JSON may lead to request errors.
    • Attempting to add attendees to a non-existent recurring event instance without specifying the timestamp.
    • Insufficient permissions for the API key to modify events or send notifications.

  • Error messages:

    • "未实现方法: calendar.addEventAttendees" indicates the operation is not implemented or incorrectly referenced.
    • API errors related to authentication or authorization suggest checking the API key credentials.
    • JSON parsing errors for the attendees property indicate malformed input; ensure valid JSON format.

To resolve these, verify all IDs, ensure correct JSON formatting, confirm API key permissions, and specify the instance timestamp for recurring events when needed.

Links and References

Discussion