Calendly
Connect Calendly to manage users, event types, scheduled events and invitees, availability, and routing forms.
You end up pasting one Calendly personal access token, generated under Automations → Integrations & apps → API and webhooks and shown only once.
- Setup time
- 4 min
- Auth
- API credentials
- API base URL
- https://api.calendly.com
- Rate limits
- Calendly throttles per token but does not publish a fixed public figure. When you exceed it the API returns HTTP 429 with a Retry-After header, so back off for that many seconds and retry.
Before you begin
- A Calendly account you can sign in to
- Access to the email inbox on that account, because Calendly sends a verification code before it issues the token
- A paid plan for the scheduling and webhook endpoints. Standard, Teams, Enterprise or legacy Professional all work
- An account that can already see the event types and scheduled events you want PopMCP to reach, because the token inherits your own user's permissions
Get your credentials
Open the API and webhooks integration
Click Automations in the left sidebar, then select the Integrations & apps tab. Find the API and webhooks tile and open it.
Integrations & apps
Connect Calendly to the tools your team already uses.
| App | Category | Status |
|---|---|---|
| Google CalendarTwo-way sync | Calendar | Connected |
| ZoomAuto-created meeting links | Video conferencing | Connected |
| API and webhooksPersonal access tokens and webhook subscriptions | Developer tools | Available |
The tile sits under Developer tools in the integrations grid. Integrations & apps used to be its own sidebar item before Calendly moved it into Automations.
Start a new personal access token
On the API and webhooks page, click Get a token now. If you already have tokens listed, click Generate new token instead.
API and webhooks
Build on the Calendly API with personal access tokens and webhook subscriptions.
| Name | Created | Last used | Status |
|---|---|---|---|
| zapier-prodCreated by you | Mar 4, 2026 | Mar 9, 2026 | Active |
First-time users see a Get a token now button where the table would be.
Name the token and create it
Under Choose a name for this token, type a name you will recognise later, such as popmcp. Click Create token.
API and webhooks
There are no scope checkboxes. The token carries your own account permissions.
Enter the emailed authentication code
Calendly emails you an authentication code. Open the email, then type the code into the verification prompt to continue.
API and webhooks
This step is new. Older walkthroughs go straight from Create token to the token value.
Copy the token into PopMCP
Click Copy token and paste the value into PopMCP's Personal Access Token field.
API and webhooks
Close this dialog and the value is gone. Calendly never redisplays it.
Connect in PopMCP
Open your workspace, choose Calendly in the marketplace, and fill in the connect dialog:
| Field | What to enter |
|---|---|
| Personal Access Tokensecret | In Calendly: click your avatar → Integrations & apps → API & webhooks → Personal access tokens → Generate new token (name it, e.g. "popmcp"). Copy the token; it's shown only once. Requires a paid plan (Standard/Teams/Enterprise or legacy Pro). Stored encrypted.Encrypted with AES-256-GCM on save and never shown again. |
PopMCP verifies the credential against Calendly immediately. On success the connection flips to Verified and its MCP tools are provisioned.
Verify it worked
PopMCP shows the connector as Connected with your Calendly name and organization URI. A test call listing event types returns your booking pages.
Troubleshooting
401 Unauthorized on every call
Why: The token was truncated on copy, or a stale token from a deleted Calendly user is being reused.
Fix: Generate a fresh token from Automations → Integrations & apps → API and webhooks and paste the whole string with no leading or trailing spaces.
You closed the token dialog before copying
Why: Calendly does not store or redisplay the token value anywhere.
Fix: Delete the token from the Personal access tokens list and generate a new one.
The verification code never arrives
Why: Calendly sends the code to the account email, which may be filtered or delayed.
Fix: Check spam and any shared-inbox rules, then click Resend code. The code is tied to the sign-in email on the Calendly account, not to your PopMCP login.
403 Forbidden on webhook or scheduling endpoints
Why: The Calendly account is on a free plan, or your user role is not an admin or owner of the organization.
Fix: Upgrade to Standard or Teams and above, or create the token from an account with organization admin rights.
403 on the activity log or invitee-deletion tools
Why: Those endpoints are Enterprise only regardless of token.
Fix: Skip those tools, or connect a token from an Enterprise organization.
429 Too Many Requests
Why: Too many calls in a short window from the same token.
Fix: Wait out the Retry-After header. PopMCP retries automatically, so space out large sync jobs.