calendly-automation by composiohq/awesome-claude-skills
npx skills add https://github.com/composiohq/awesome-claude-skills --skill calendly-automation通过 Composio 的 Calendly 工具包,自动化 Calendly 操作,包括事件列表、受邀者管理、日程安排链接创建、可用性查询和组织管理。
工具包文档 : composio.dev/toolkits/calendly
RUBE_SEARCH_TOOLS 可用)RUBE_MANAGE_CONNECTIONS 与工具包 calendly 建立有效的 Calendly 连接RUBE_SEARCH_TOOLS 以获取当前工具模式CALENDLY_GET_CURRENT_USER 获取获取 Rube MCP : 在您的客户端配置中将 https://rube.app/mcp 添加为 MCP 服务器。无需 API 密钥 — 只需添加端点即可工作。
广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
RUBE_SEARCH_TOOLS 有响应来验证 Rube MCP 是否可用calendly 调用 RUBE_MANAGE_CONNECTIONS使用场景 : 用户希望查看其即将到来、过去或经过筛选的 Calendly 事件
工具调用顺序 :
CALENDLY_GET_CURRENT_USER - 获取已认证用户的 URI 和组织 URI [先决条件]CALENDLY_LIST_EVENTS - 列出按用户、组织或群组范围筛选的事件 [必需]CALENDLY_GET_EVENT - 通过 UUID 获取特定事件的详细信息 [可选]关键参数 :
user: 完整的 Calendly API URI(例如,https://api.calendly.com/users/{uuid})- 不能是 "me"organization: 用于组织范围查询的完整组织 URIstatus: "active" 或 "canceled"min_start_time / max_start_time: UTC 时间戳(例如,2024-01-01T00:00:00.000000Z)invitee_email: 按受邀者邮箱筛选事件(仅为筛选条件,非范围)sort: "start_time:asc" 或 "start_time:desc"count: 每页结果数(默认 20)page_token: 来自先前响应的分页令牌常见问题 :
user、organization 或 group 中的一个参数 - 省略或组合多个范围会导致失败user 参数需要完整的 API URI,不能是 "me" - 请先使用 CALENDLY_GET_CURRENT_USERinvitee_email 是筛选条件,不是范围;您仍然需要提供 user/organization/group 中的一个count + page_token;循环直到 page_token 不存在以获得完整结果使用场景 : 用户希望查看谁已预订事件或获取受邀者详细信息
工具调用顺序 :
CALENDLY_LIST_EVENTS - 查找目标事件 [先决条件]CALENDLY_LIST_EVENT_INVITEES - 列出特定事件的所有受邀者 [必需]CALENDLY_GET_EVENT_INVITEE - 获取单个受邀者的详细信息 [可选]关键参数 :
uuid: 事件 UUID(用于 LIST_EVENT_INVITEES)event_uuid + invitee_uuid: GET_EVENT_INVITEE 需要两者email: 按邮箱地址筛选受邀者status: "active" 或 "canceled"sort: "created_at:asc" 或 "created_at:desc"count: 每页结果数(默认 20)常见问题 :
CALENDLY_LIST_EVENT_INVITEES 的 uuid 参数是事件 UUID,而不是受邀者 UUIDpage_token 进行分页,直到其不存在以获得完整的受邀者列表status: "canceled" 查看它们使用场景 : 用户希望生成预订链接或检查可用时间段
工具调用顺序 :
CALENDLY_GET_CURRENT_USER - 获取用户 URI [先决条件]CALENDLY_LIST_USER_S_EVENT_TYPES - 列出可用的事件类型 [必需]CALENDLY_LIST_EVENT_TYPE_AVAILABLE_TIMES - 检查事件类型的可用时间段 [可选]CALENDLY_CREATE_SCHEDULING_LINK - 生成一次性日程安排链接 [必需]CALENDLY_LIST_USER_AVAILABILITY_SCHEDULES - 查看用户的可用性日程表 [可选]关键参数 :
owner: 事件类型 URI(例如,https://api.calendly.com/event_types/{uuid})owner_type: "EventType"(默认)max_event_count: 对于一次性链接,必须恰好为 1start_time / end_time: 用于可用性查询的 UTC 时间戳(最长 7 天范围)active: 布尔值,用于筛选活动/非活动事件类型user: 用于事件类型列表的用户 URI常见问题 :
CALENDLY_CREATE_SCHEDULING_LINK 可能返回 403CALENDLY_LIST_EVENT_TYPE_AVAILABLE_TIMES 需要 UTC 时间戳且最长 7 天范围;对于更长的搜索请拆分https://api.calendly.com/event_types/...)使用场景 : 用户希望取消已安排的 Calendly 事件
工具调用顺序 :
CALENDLY_LIST_EVENTS - 查找要取消的事件 [先决条件]CALENDLY_GET_EVENT - 在取消前确认事件详情 [先决条件]CALENDLY_LIST_EVENT_INVITEES - 检查将受影响的人员 [可选]CALENDLY_CANCEL_EVENT - 取消事件 [必需]关键参数 :
uuid: 要取消的事件 UUIDreason: 可选的取消原因(可能包含在给受邀者的通知中)常见问题 :
CALENDLY_CANCEL_EVENT 之前,请获取用户的明确确认使用场景 : 用户希望邀请成员、管理组织或处理组织邀请
工具调用顺序 :
CALENDLY_GET_CURRENT_USER - 获取用户和组织上下文 [先决条件]CALENDLY_GET_ORGANIZATION - 获取组织详情 [可选]CALENDLY_LIST_ORGANIZATION_INVITATIONS - 检查现有邀请 [可选]CALENDLY_CREATE_ORGANIZATION_INVITATION - 发送组织邀请 [必需]CALENDLY_REVOKE_USER_S_ORGANIZATION_INVITATION - 撤销待处理的邀请 [可选]CALENDLY_REMOVE_USER_FROM_ORGANIZATION - 移除成员 [可选]关键参数 :
uuid: 组织 UUIDemail: 要邀请用户的邮箱地址status: 按 "pending"、"accepted" 或 "declined" 筛选邀请常见问题 :
CALENDLY_REMOVE_USER_FROM_ORGANIZATION 移除Calendly 使用完整的 API URI 作为标识符,而不是简单的 ID:
CALENDLY_GET_CURRENT_USER 返回 resource.uri(例如,https://api.calendly.com/users/{uuid})resource.current_organization 中找到CALENDLY_LIST_USER_S_EVENT_TYPES 响应重要提示:切勿在列表/筛选端点中使用 "me" 作为用户参数。始终先解析为完整的 URI。
大多数 Calendly 列表端点使用基于令牌的分页:
count 以确定页面大小(默认 20)pagination.next_page_token 中的 page_token,直到其不存在field:direction 格式排序(例如,start_time:asc、created_at:desc)yyyy-MM-ddTHH:mm:ss.ffffffZmin_start_time / max_start_time 对事件进行日期范围筛选https://api.calendly.com/users/{uuid})"me" 传递给列表端点CALENDLY_GET_EVENT),从 URI 中提取 UUIDCALENDLY_LIST_EVENTS 要求恰好一个范围(user、organization 或 group)- 不能多也不能少| 任务 | 工具标识 | 关键参数 |
|---|---|---|
| 获取当前用户 | CALENDLY_GET_CURRENT_USER | (无) |
| 通过 UUID 获取用户 | CALENDLY_GET_USER | uuid |
| 列出事件 | CALENDLY_LIST_EVENTS | user, status, min_start_time |
| 获取事件详情 | CALENDLY_GET_EVENT | uuid |
| 取消事件 | CALENDLY_CANCEL_EVENT | uuid, reason |
| 列出受邀者 | CALENDLY_LIST_EVENT_INVITEES | uuid, status, email |
| 获取受邀者 | CALENDLY_GET_EVENT_INVITEE | event_uuid, invitee_uuid |
| 列出事件类型 | CALENDLY_LIST_USER_S_EVENT_TYPES | user, active |
| 获取事件类型 | CALENDLY_GET_EVENT_TYPE | uuid |
| 检查可用性 | CALENDLY_LIST_EVENT_TYPE_AVAILABLE_TIMES | 事件类型 URI, start_time, end_time |
| 创建日程安排链接 | CALENDLY_CREATE_SCHEDULING_LINK | owner, max_event_count |
| 列出可用性日程表 | CALENDLY_LIST_USER_AVAILABILITY_SCHEDULES | 用户 URI |
| 获取组织 | CALENDLY_GET_ORGANIZATION | uuid |
| 邀请加入组织 | CALENDLY_CREATE_ORGANIZATION_INVITATION | uuid, email |
| 列出组织邀请 | CALENDLY_LIST_ORGANIZATION_INVITATIONS | uuid, status |
| 撤销组织邀请 | CALENDLY_REVOKE_USER_S_ORGANIZATION_INVITATION | 组织 UUID, 邀请 UUID |
| 从组织中移除 | CALENDLY_REMOVE_USER_FROM_ORGANIZATION | 成员资格 UUID |
由 Composio 提供支持
每周安装
73
代码仓库
GitHub 星标
42.7K
首次出现
2026年2月6日
安全审计
安装于
opencode58
claude-code55
gemini-cli52
codex48
replit42
antigravity41
Automate Calendly operations including event listing, invitee management, scheduling link creation, availability queries, and organization administration through Composio's Calendly toolkit.
Toolkit docs : composio.dev/toolkits/calendly
RUBE_MANAGE_CONNECTIONS with toolkit calendlyRUBE_SEARCH_TOOLS first to get current tool schemasCALENDLY_GET_CURRENT_USERGet Rube MCP : Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
RUBE_SEARCH_TOOLS respondsRUBE_MANAGE_CONNECTIONS with toolkit calendlyWhen to use : User wants to see their upcoming, past, or filtered Calendly events
Tool sequence :
CALENDLY_GET_CURRENT_USER - Get authenticated user URI and organization URI [Prerequisite]CALENDLY_LIST_EVENTS - List events scoped by user, organization, or group [Required]CALENDLY_GET_EVENT - Get detailed info for a specific event by UUID [Optional]Key parameters :
user: Full Calendly API URI (e.g., https://api.calendly.com/users/{uuid}) - NOT "me"organization: Full organization URI for org-scoped queriesstatus: "active" or "canceled"min_start_time / max_start_time: UTC timestamps (e.g., 2024-01-01T00:00:00.000000Z)invitee_email: Filter events by invitee email (filter only, not a scope)Pitfalls :
user, organization, or group must be provided - omitting or combining scopes failsuser parameter requires the full API URI, not "me" - use CALENDLY_GET_CURRENT_USER firstinvitee_email is a filter, not a scope; you still need one of user/organization/groupcount + page_token; loop until page_token is absent for complete resultsWhen to use : User wants to see who is booked for events or get invitee details
Tool sequence :
CALENDLY_LIST_EVENTS - Find the target event(s) [Prerequisite]CALENDLY_LIST_EVENT_INVITEES - List all invitees for a specific event [Required]CALENDLY_GET_EVENT_INVITEE - Get detailed info for a single invitee [Optional]Key parameters :
uuid: Event UUID (for LIST_EVENT_INVITEES)event_uuid + invitee_uuid: Both required for GET_EVENT_INVITEEemail: Filter invitees by email addressstatus: "active" or "canceled"sort: "created_at:asc" or Pitfalls :
uuid parameter for CALENDLY_LIST_EVENT_INVITEES is the event UUID, not the invitee UUIDpage_token until absent for complete invitee listsstatus: "canceled" to see themWhen to use : User wants to generate a booking link or check available time slots
Tool sequence :
CALENDLY_GET_CURRENT_USER - Get user URI [Prerequisite]CALENDLY_LIST_USER_S_EVENT_TYPES - List available event types [Required]CALENDLY_LIST_EVENT_TYPE_AVAILABLE_TIMES - Check available slots for an event type [Optional]CALENDLY_CREATE_SCHEDULING_LINK - Generate a single-use scheduling link [Required]CALENDLY_LIST_USER_AVAILABILITY_SCHEDULES - View user's availability schedules [Optional]Key parameters :
owner: Event type URI (e.g., https://api.calendly.com/event_types/{uuid})owner_type: "EventType" (default)max_event_count: Must be exactly 1 for single-use linksstart_time / end_time: UTC timestamps for availability queries (max 7-day range)active: Boolean to filter active/inactive event typesuser: User URI for event type listingPitfalls :
CALENDLY_CREATE_SCHEDULING_LINK can return 403 if token lacks rights or owner URI is invalidCALENDLY_LIST_EVENT_TYPE_AVAILABLE_TIMES requires UTC timestamps and max 7-day range; split longer searcheshttps://api.calendly.com/event_types/...)When to use : User wants to cancel a scheduled Calendly event
Tool sequence :
CALENDLY_LIST_EVENTS - Find the event to cancel [Prerequisite]CALENDLY_GET_EVENT - Confirm event details before cancellation [Prerequisite]CALENDLY_LIST_EVENT_INVITEES - Check who will be affected [Optional]CALENDLY_CANCEL_EVENT - Cancel the event [Required]Key parameters :
uuid: Event UUID to cancelreason: Optional cancellation reason (may be included in notification to invitees)Pitfalls :
CALENDLY_CANCEL_EVENTWhen to use : User wants to invite members, manage organization, or handle org invitations
Tool sequence :
CALENDLY_GET_CURRENT_USER - Get user and organization context [Prerequisite]CALENDLY_GET_ORGANIZATION - Get organization details [Optional]CALENDLY_LIST_ORGANIZATION_INVITATIONS - Check existing invitations [Optional]CALENDLY_CREATE_ORGANIZATION_INVITATION - Send an org invitation [Required]CALENDLY_REVOKE_USER_S_ORGANIZATION_INVITATION - Revoke a pending invitation [Optional]CALENDLY_REMOVE_USER_FROM_ORGANIZATION - Remove a member [Optional]Key parameters :
uuid: Organization UUIDemail: Email address of user to invitestatus: Filter invitations by "pending", "accepted", or "declined"Pitfalls :
CALENDLY_REMOVE_USER_FROM_ORGANIZATIONCalendly uses full API URIs as identifiers, not simple IDs:
CALENDLY_GET_CURRENT_USER returns resource.uri (e.g., https://api.calendly.com/users/{uuid})resource.current_organizationCALENDLY_LIST_USER_S_EVENT_TYPES responseImportant: Never use "me" as a user parameter in list/filter endpoints. Always resolve to the full URI first.
Most Calendly list endpoints use token-based pagination:
count for page size (default 20)page_token from pagination.next_page_token until absentfield:direction format (e.g., start_time:asc, created_at:desc)yyyy-MM-ddTHH:mm:ss.ffffffZmin_start_time / max_start_time for date range filtering on eventshttps://api.calendly.com/users/{uuid})"me" to list endpointsCALENDLY_GET_EVENT)CALENDLY_LIST_EVENTS requires exactly one scope (user, organization, or group) - no more, no less| Task | Tool Slug | Key Params |
|---|---|---|
| Get current user | CALENDLY_GET_CURRENT_USER | (none) |
| Get user by UUID | CALENDLY_GET_USER | uuid |
| List events | CALENDLY_LIST_EVENTS | user, status, min_start_time |
Powered byComposio
Weekly Installs
73
Repository
GitHub Stars
42.7K
First Seen
Feb 6, 2026
Security Audits
Gen Agent Trust HubPassSocketPassSnykWarn
Installed on
opencode58
claude-code55
gemini-cli52
codex48
replit42
antigravity41
Azure RBAC 权限管理工具:查找最小角色、创建自定义角色与自动化分配
142,000 周安装
sort: "start_time:asc" or "start_time:desc"count: Results per page (default 20)page_token: Pagination token from previous response"created_at:desc"count: Results per page (default 20)| Get event details | CALENDLY_GET_EVENT | uuid |
| Cancel event | CALENDLY_CANCEL_EVENT | uuid, reason |
| List invitees | CALENDLY_LIST_EVENT_INVITEES | uuid, status, email |
| Get invitee | CALENDLY_GET_EVENT_INVITEE | event_uuid, invitee_uuid |
| List event types | CALENDLY_LIST_USER_S_EVENT_TYPES | user, active |
| Get event type | CALENDLY_GET_EVENT_TYPE | uuid |
| Check availability | CALENDLY_LIST_EVENT_TYPE_AVAILABLE_TIMES | event type URI, start_time, end_time |
| Create scheduling link | CALENDLY_CREATE_SCHEDULING_LINK | owner, max_event_count |
| List availability schedules | CALENDLY_LIST_USER_AVAILABILITY_SCHEDULES | user URI |
| Get organization | CALENDLY_GET_ORGANIZATION | uuid |
| Invite to org | CALENDLY_CREATE_ORGANIZATION_INVITATION | uuid, email |
| List org invitations | CALENDLY_LIST_ORGANIZATION_INVITATIONS | uuid, status |
| Revoke org invitation | CALENDLY_REVOKE_USER_S_ORGANIZATION_INVITATION | org UUID, invitation UUID |
| Remove from org | CALENDLY_REMOVE_USER_FROM_ORGANIZATION | membership UUID |