by Calendly
List event invitees
Returns the invitees of one scheduled event with their emails, booking-question answers, UTM tracking and no-show status.
Description
Pass the scheduled event's `uuid`, the last part of its URI. Filter by `status` or `email`; results come 20 per page in `created_at` order. Each invitee's `questions_and_answers` holds what the booking form collected and `tracking` holds its UTM parameters, ready to write to a CRM.
list-event-invitees.md
List event invitees
Returns the invitees of one scheduled event with their emails, booking-question answers, UTM tracking and no-show status.
Pass the scheduled event's uuid, the last part of its URI. Filter by
status or email; results come 20 per page in created_at order. Each
invitee's questions_and_answers holds what the booking form collected and
tracking holds its UTM parameters, ready to write to a CRM.
Set up
Use the first option your agent supports.
MCP (official, remote)
Add this server to your agent's MCP settings, then sign in when asked.
{ "mcpServers": { "calendly": { "url": "https://mcp.calendly.com" } } }
Call the MCP tool meetings-list_event_invitees.
Server URL: https://mcp.calendly.com
API (official)
- Base URL: https://api.calendly.com
- Endpoint:
GET /scheduled_events/{uuid}/invitees - Auth: send the header
Authorization: Bearer $CALENDLY_API_KEY - Get a key: https://calendly.com/integrations/api_webhooks
- Docs: https://developer.calendly.com/api-docs/overview/api/reference
Before doing anything else, make one read-only call to confirm access.
Rules
- Ask the user before anything that sends messages, costs money, or changes data.
- Never print API keys.
Built from these files in the repository
The layout and the rules come from lib/catalog/render-markdown.ts, the set-up wording from lib/catalog/render-access.ts.