Feishu Calendar Management (feishu-calendar)

🚨 Pre-execution Notes

✅ Fixed Time Zone: Asia/Shanghai (UTC+8)
✅ Time Format: ISO 8601 / RFC 3339 (with time zone), e.g.,
```
2026-02-25T14:00:00+08:00
```
✅ Minimum Required for create: summary, start_time, end_time
✅ Highly Recommended: user_open_id: Obtain from SenderId (ou_xxx) to ensure the user can view the schedule
✅ ID Format Convention: User
```
ou_...
```
, Group
```
oc_...
```
, Meeting Room
```
omm_...
```
, Email
```
email@...
```

📋 Quick Index: Intent → Tool → Required Parameters

User Intent	Tool	action	Required Parameters	Highly Recommended	Common Optional
Create Meeting	feishu_calendar_event	create	summary, start_time, end_time	user_open_id	attendees, description, location
Query Schedules in a Time Period	feishu_calendar_event	list	start_time, end_time	-	-
Modify Schedule Time	feishu_calendar_event	patch	event_id, start_time/end_time	-	summary, description
Search Meetings by Keyword	feishu_calendar_event	search	query	-	-
Reply to Invitation	feishu_calendar_event	reply	event_id, rsvp_status	-	-
Query Recurring Schedule Instances	feishu_calendar_event	instances	event_id, start_time, end_time	-	-
Query Free/Busy Status	feishu_calendar_freebusy	list	time_min, time_max, user_ids[]	-	-
Invite Attendees	feishu_calendar_event_attendee	create	calendar_id, event_id, attendees[]	-	-
Remove Attendees	feishu_calendar_event_attendee	batch_delete	calendar_id, event_id, user_open_ids[]	-	-

🎯 Core Constraints (Knowledge Not Disclosed in Schema)

1. Why is user_open_id required?

Tool Uses User Identity: The schedule is created on the user's primary calendar, so the user can see it.

But why pass user_open_id?: Add the organizer as an attendee to ensure:

✅ The organizer receives schedule notifications
✅ The organizer can reply with RSVP status (accept/decline/tentative)
✅ The organizer appears in the attendee list
✅ Other attendees can see the organizer

If not passed:

⚠️ The user can see the schedule but will not be an attendee
⚠️ If only other attendees exist, the organizer is not in the list (does not conform to normal logic)

2. Attendee Permissions (attendee_ability)

The tool is defaulted to

attendee_ability: "can_modify_event"

, allowing attendees to edit the schedule and manage participants.

Permission Value	Ability
`none`	No permissions
`can_see_others`	Can view the attendee list
`can_invite_others`	Can invite others
`can_modify_event`	Can edit the schedule (recommended)

3. Uniform Use of open_id (ou_... format)

✅ Create Schedule:
```
user_open_id = SenderId
```
✅ Invite Attendees:
```
attendees[].id = "ou_xxx"
```
✅ Remove Attendees:
```
user_open_ids = ["ou_xxx"]
```
(optimized by the tool, directly pass open_id)

⚠️ ID Format Distinction:

```
ou_xxx
```
: User's open_id (you should use this)
```
user_xxx
```
: Internal attendee_id returned by the list interface (only for internal records)

4. Meeting Room Reservation is an Asynchronous Process

After adding a meeting room-type attendee, the meeting room enters an asynchronous reservation process:

API returns success →
```
rsvp_status: "needs_action"
```
(reserving)
Background processes asynchronously
Final status:
```
accept
```
(success) or
```
decline
```
(failure)

Query Reservation Result: Use

feishu_calendar_event_attendee.list

to check

rsvp_status

5. instances Action Only Works for Recurring Schedules

⚠️ Important: The

instances

action only works for recurring schedules, which must meet:

event_id must be the ID of a recurring schedule (the schedule has the
```
recurrence
```
field)
If called for a regular schedule, an error will be returned

How to Judge:

First use the
```
get
```
action to get schedule details
Check if the return value has a non-empty
```
recurrence
```
field
If yes, call
```
instances
```
to get the instance list

📌 Usage Scenario Examples

Scenario 1: Create a Meeting and Invite Attendees

json

{
  "action": "create",
  "summary": "Project Retrospective Meeting",
  "description": "Discuss Q1 Project Progress",
  "start_time": "2026-02-25 14:00:00",
  "end_time": "2026-02-25 15:30:00",
  "user_open_id": "ou_aaa",
  "attendees": [
    {"type": "user", "id": "ou_bbb"},
    {"type": "user", "id": "ou_ccc"},
    {"type": "resource", "id": "omm_xxx"}
  ]
}

Scenario 2: Query a User's Schedules for the Next Week

json

{
  "action": "list",
  "start_time": "2026-02-25 00:00:00",
  "end_time": "2026-03-03 23:59:00"
}

Scenario 3: View Free/Busy Time of Multiple Users

json

{
  "action": "list",
  "time_min": "2026-02-25 09:00:00",
  "time_max": "2026-02-25 18:00:00",
  "user_ids": ["ou_aaa", "ou_bbb", "ou_ccc"]
}

Note: user_ids is an array, supporting 1-10 users. Meeting room free/busy query is not currently supported.

Scenario 4: Modify Schedule Time

json

{
  "action": "patch",
  "event_id": "xxx_0",
  "start_time": "2026-02-25 15:00:00",
  "end_time": "2026-02-25 16:00:00"
}

Scenario 5: Search Schedules (by Keyword)

json

{
  "action": "search",
  "query": "Project Retrospective"
}

Scenario 6: Reply to Schedule Invitation

json

{
  "action": "reply",
  "event_id": "xxx_0",
  "rsvp_status": "accept"
}

🔍 Common Errors and Troubleshooting

Error Phenomenon	Root Cause	Solution
Organizer not in attendee list	Did not pass `user_open_id`	Highly recommended to pass `user_open_id = SenderId`
Attendees cannot see other attendees	Insufficient `attendee_ability` permissions	The tool is defaulted to `can_modify_event`
Incorrect time	Used Unix timestamp	Switch to ISO 8601 format (with time zone): `2024-01-01T00:00:00+08:00`
Meeting room shows "reserving"	Meeting room reservation is asynchronous	Wait a few seconds and query `rsvp_status` with `list`
Permission error when modifying schedule	Current user is not the organizer, and the schedule is not set with editable permissions	Ensure `attendee_ability: "can_modify_event"` is set when creating the schedule
Cannot view attendee list	Current user has no viewing permissions	Ensure you are the organizer or the schedule is set with permissions above `can_see_others`

📚 Appendix: Background Knowledge

A. Calendar Architecture Model

Feishu Calendar adopts a Three-tier Architecture:

Calendar
  └── Event
       └── Attendee

Key Understandings:

User Primary Calendar: The schedule is created on the organizer's primary calendar, so the user can see it
Attendee Mechanism: By adding attendees, the schedule is also displayed in other attendees' calendars
Permission Model: The schedule's
```
attendee_ability
```
parameter controls whether attendees can edit the schedule, invite others, or view the attendee list

B. Attendee Types

```
type: "user"
```
+
```
id: "ou_xxx"
```
— Feishu User (use open_id)
```
type: "chat"
```
+
```
id: "oc_xxx"
```
— Feishu Group
```
type: "resource"
```
+
```
id: "omm_xxx"
```
— Meeting Room

type: "third_party"

id: "email@example.com"

— External Email

C. Schedule Lifecycle

Creation: Create a schedule on the user's primary calendar (tool uses user identity)
Invite Attendees: Share the schedule with other attendees via the attendee API
Attendee Reply: Attendees can accept/decline/tentative
Modification: The organizer or authorized attendees can modify it
Deletion: After deletion, the status becomes
```
cancelled
```

D. Calendar Type Description

Type	Description	Deletable	Editable
`primary`	Primary Calendar (one per user/app)	❌ No	✅ Yes
`shared`	Shared Calendar (created and shared by users)	✅ Yes	✅ Yes
`resource`	Meeting Room Calendar	❌ No	❌ No
`google`	Bound Google Calendar	❌ No	❌ No
`exchange`	Bound Exchange Calendar	❌ No	❌ No

E. RSVP Status (rsvp_status) Description

Status	Meaning (User)	Meaning (Meeting Room)
`needs_action`	Not replied	Reserving
`accept`	Accepted	Reservation successful
`tentative`	Tentative	-
`decline`	Declined	Reservation failed
`removed`	Removed	Removed

F. Usage Limits (from Feishu OAPI Documentation)

Maximum 3000 attendees per schedule
Single Attendee Addition Limit:
- User-type attendees: 1000 people
- Meeting Rooms: 100 rooms
Primary Calendar cannot be deleted (calendar type is primary)
Meeting Room Reservation May Fail:
- Time conflict
- No reservation permission
- Meeting room configuration restrictions

feishu-calendar

NPX Install

Tags

SKILL.md Content (Chinese)

Feishu Calendar Management (feishu-calendar)

🚨 Pre-execution Notes

📋 Quick Index: Intent → Tool → Required Parameters

🎯 Core Constraints (Knowledge Not Disclosed in Schema)

1. Why is user_open_id required?

2. Attendee Permissions (attendee_ability)

3. Uniform Use of open_id (ou_... format)

4. Meeting Room Reservation is an Asynchronous Process

5. instances Action Only Works for Recurring Schedules

📌 Usage Scenario Examples

Scenario 1: Create a Meeting and Invite Attendees

Scenario 2: Query a User's Schedules for the Next Week

Scenario 3: View Free/Busy Time of Multiple Users

Scenario 4: Modify Schedule Time

Scenario 5: Search Schedules (by Keyword)

Scenario 6: Reply to Schedule Invitation

🔍 Common Errors and Troubleshooting

📚 Appendix: Background Knowledge

A. Calendar Architecture Model

B. Attendee Types

C. Schedule Lifecycle

D. Calendar Type Description

E. RSVP Status (rsvp_status) Description

F. Usage Limits (from Feishu OAPI Documentation)