Calendly MCP integration for AI agents.
Connect AI agents to Calendly through 37 structured actions, including get current user, create event invitee, and cancel scheduled event. Review authenticat…
- ACTION CONTRACTS
- 37
- AUTHENTICATION
- OAuth 2.0 + API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Calendly integration exposes
The Calendly Agent App exposes 37 provider-backed actions for productivity work. Its current contract lets an authorized agent retrieve the authenticated calendly user for the connected credential, create one calendly invitee booking for a confirmed available start time, and cancel one calendly scheduled event by scheduled-event uri. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses OAuth 2.0 and API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Calendly account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Calendly capabilities.
Showing 12 of 37 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_current_userREADRetrieve the authenticated Calendly user for the connected credential.
create_event_inviteeWRITECreate one Calendly invitee booking for a confirmed available start time.
INPUTS: eventTypeUri / startTime / invitee / eventGuests / questionsAndAnswers
cancel_scheduled_eventHIGH IMPACTCancel one Calendly scheduled event by scheduled-event URI.
INPUTS: scheduledEventUri / reason
create_invitee_no_showWRITEMark one Calendly invitee as a no-show by invitee URI.
INPUTS: inviteeUri
create_organization_invitationWRITECreate one organization invitation for a Calendly organization.
INPUTS: organizationUri / email
create_shareWRITECreate one customized single-use share from an existing Calendly event type.
INPUTS: eventTypeUri / name / duration / durationOptions / periodType
create_single_use_scheduling_linkWRITECreate one single-use scheduling link from an existing Calendly event type without customization.
INPUTS: eventTypeUri
create_webhook_subscriptionWRITECreate one Calendly webhook subscription for an organization or one user.
INPUTS: url / scope / organizationUri / userUri / events
delete_invitee_no_showHIGH IMPACTDelete one Calendly invitee no-show by no-show URI.
INPUTS: inviteeNoShowUri
delete_organization_membershipHIGH IMPACTDelete one Calendly organization membership by membership URI.
INPUTS: organizationMembershipUri
delete_webhook_subscriptionHIGH IMPACTDelete one Calendly webhook subscription by URI.
INPUTS: webhookSubscriptionUri
get_event_inviteeREADRetrieve one Calendly invitee by invitee URI.
INPUTS: scheduledEventUri / inviteeUri
INPUT CONTRACTS
Know what the action needs before it runs.
create_event_invitee
eventTypeUriREQUIRED- The Calendly event type URI returned by the API.
startTimeREQUIRED- The scheduled start time to book in ISO 8601 format.
inviteeREQUIRED- The primary invitee profile used to create one Calendly booking.
eventGuestsOPTIONAL- The guest email addresses to add to the booking.
questionsAndAnswersOPTIONAL- The answers to custom questions to submit with the booking.
cancel_scheduled_event
scheduledEventUriREQUIRED- The Calendly scheduled event URI returned by the API.
reasonREQUIRED- The human-readable reason to cancel the scheduled event.
create_invitee_no_show
inviteeUriREQUIRED- The Calendly invitee URI returned by the API.
create_organization_invitation
organizationUriREQUIRED- The Calendly organization URI returned by the API.
emailREQUIRED- The email address to invite to the organization.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Current User
Retrieve the authenticated Calendly user for the connected credential. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_current_userControl Create Event Invitee
Create one Calendly invitee booking for a confirmed available start time. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_event_inviteeVerify with Create Event Invitee
Create one Calendly invitee booking for a confirmed available start time. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
create_event_inviteeSAFETY BOUNDARY
Operate Calendly with explicit limits
- Authorize Calendly with OAuth 2.0 and API key and grant only the provider access required by the selected actions.
- 12 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `cancel_scheduled_event`, `delete_invitee_no_show`, and `delete_organization_membership` as high-impact operations and require an explicit approval boundary.
- The sampled contract declares provider scopes including `scheduled_events:write`, `organizations:write`, `shares:write`, and `scheduling_links:write`; verify the complete action contract before execution.
- After a call, inspect the structured result and execution record before reporting that the Calendly task completed successfully.
CONNECTION MODEL
OAuth 2.0 + API key
Calendly personal access token used with the Authorization Bearer header. Create it from API & Webhooks in the Calendly Integrations page: https://calendly.com/integrations/api_webhooks
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 25
- WRITE SIGNALS
- 7
- HIGH IMPACT
- 5
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Calendly.