Feishu Node

Actions61

Overview

This node allows you to delete a calendar event ("日程") from a specified calendar ("日历") in Feishu (Lark). It is useful for automating the removal of scheduled events, such as when an appointment is canceled or needs to be retracted programmatically. For example, you could use this node in workflows that synchronize external booking systems with Feishu calendars, or to automatically clean up outdated or erroneous events.

Properties

Name	Type	Meaning
日历 ID	String	The ID of the calendar containing the event. Obtainable via calendar list/search APIs.
日程 ID	String	The ID of the event to delete. Obtainable via event creation/list/search APIs.
是否发送通知	Boolean	Whether to send a Bot notification to event participants upon deletion.

Output

The output will be a JSON object for each processed input item.
On success, the output typically contains confirmation of deletion (the exact structure depends on the Feishu API response).
On error, the output will include an error field with the error message. If the error is from the Feishu API (NodeApiError), it may also include additional details under the error key.

Example error output:

{
  "error": "Event not found"
}

Dependencies

Feishu API: Requires valid Feishu credentials (feishuCredentialsApi) configured in n8n.
n8n Configuration: Ensure the Feishu credential is set up and has permission to manage calendar events.

Troubleshooting

Missing Method Error:
- Message: 未实现方法: calendar.calendar:deleteEvent
- Cause: The requested resource/operation combination is not implemented in the node.
- Solution: Check if the operation name matches exactly what the node supports.
API Errors (NodeApiError):
- These are errors returned by the Feishu API, such as invalid IDs or insufficient permissions.
- The error message will be included in the output; check the error field for details.
- Solution: Verify that the provided Calendar ID and Event ID are correct and that your credentials have sufficient access.
Credential Issues:
- If credentials are missing or invalid, the node will fail to authenticate.
- Solution: Ensure the Feishu credentials are correctly configured in n8n.