Feishu Node icon

Feishu Node

Feishu Node

Actions106

Overview

This node integrates with a calendar service to update existing calendar events. It allows users to modify details of a specific event within a specified calendar by providing the calendar ID, event ID, and the updated event data in JSON format. This is useful for automating calendar management tasks such as rescheduling meetings, updating event descriptions, or changing event participants.

Practical examples include:

  • Automatically updating meeting times based on external triggers.
  • Modifying event details when related project deadlines change.
  • Syncing event updates from other systems into the calendar.

Properties

Name Meaning
日历 ID The ID of the calendar where the event exists. This can be obtained via APIs that fetch primary calendar info, list calendars, or search calendars.
日程 ID The ID of the event to update. This can be retrieved from event creation responses, event listing, or event search APIs.
请求体 The request body containing the fields to update in the event. It must follow the structure defined in the calendar API documentation (e.g., https://open.feishu.cn/document/server-docs/calendar-v4/calendar-event/patch#requestBody).
用户 ID 类型 The type of user ID used in the request. Options are: Open ID, Union ID, or User ID. This defines how user identifiers are interpreted in the update operation.

Output

The node outputs an array of JSON objects representing the updated event(s). Each output item corresponds to one input item processed and contains the updated event data returned from the calendar API.

If the node supports binary data output (not indicated here), it would typically represent attachments or related media associated with the event, but this node focuses on JSON event data only.

Dependencies

  • Requires an API key credential for authenticating with the calendar service.
  • Depends on the calendar service's API endpoints for fetching and updating calendar events.
  • The node uses internal helper methods to construct execution metadata and handle errors.
  • Proper configuration of credentials and permissions to access and modify calendar events is necessary.

Troubleshooting

  • Common issues:

    • Invalid or missing calendar ID or event ID will cause the update to fail.
    • Malformed JSON in the request body may result in API errors.
    • Insufficient permissions or expired API tokens can lead to authentication errors.
    • Using incorrect user ID types might cause user-related fields not to update correctly.

  • Error messages:

    • "未实现方法: calendar.updateEvent" indicates the operation is not implemented or incorrectly referenced.
    • API error messages returned from the calendar service will be included in the node’s error output.

  • Resolutions:

    • Verify that calendar and event IDs are correct and exist.
    • Validate the JSON structure against the API documentation before sending.
    • Ensure the API key or token is valid and has required scopes.
    • Select the correct user ID type matching the identifiers used in your organization.

Links and References

Discussion