Feishu Node

Overview

This node integrates with a calendar service to create a meeting chat group associated with a specific calendar event. It is useful in scenarios where users want to automatically generate a collaborative chat space for participants of a calendar event, facilitating communication and coordination directly linked to that event.

Practical examples include:

• Automatically creating a chat group when scheduling team meetings to streamline discussions.
• Generating dedicated conversation channels for project milestones or client appointments.
• Enhancing event management workflows by linking calendar events with real-time messaging.

Properties

Name	Meaning
日历 ID	The ID of the calendar where the event is located. This can be obtained via APIs that list or search calendars.
日程 ID	The ID of the specific calendar event. This can be retrieved through event creation or listing APIs.

Output

The node outputs JSON data representing the result of the "create meeting chat" operation. This typically includes details about the newly created meeting chat group, such as its identifier and metadata confirming successful creation.

If the node supports binary data output (not evident from the provided code), it would represent any files or media related to the meeting chat, but no such indication is present here.

Dependencies

• Requires an API key credential for authenticating with the calendar and messaging service.
• Depends on the external calendar and chat platform's API endpoints to create meeting chats.
• The node uses a resource-operation factory pattern internally to call the appropriate API method based on selected resource and operation.

Troubleshooting

• Common issues:

  • Invalid or missing calendar ID or event ID will cause the operation to fail.
  • Authentication errors if the API key credential is incorrect or expired.
  • Network or API rate limiting issues may interrupt the creation process.

• Error messages:

  • "未实现方法: calendar.calendar:createEventMeetingChat" indicates the requested operation is not implemented or recognized; verify the resource and operation names.
  • API errors wrapped as NodeApiError may contain detailed error information from the external service; check the error message for specifics.

• Resolutions:

  • Ensure correct calendar and event IDs are provided.
  • Verify API credentials and permissions.
  • Handle errors gracefully using the node’s "continue on fail" option if available.

Links and References

• Refer to the calendar service API documentation for details on obtaining calendar and event IDs.
• Consult the messaging/chat platform API docs for specifics on meeting chat creation.
• n8n documentation on custom nodes and error handling for further guidance.