# Calendly setup for PopMCP

You end up pasting one Calendly personal access token, generated under Automations → Integrations & apps → API and webhooks and shown only once.

- Auth: API credentials
- Setup time: 4 min
- API base URL: https://api.calendly.com
- Credentials screen: https://calendly.com/integrations/api_webhooks
- Provider docs: https://developer.calendly.com/how-to-authenticate-with-personal-access-tokens

## 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

### 1. 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.

Screen: https://calendly.com/integrations/api_webhooks

### 2. 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.

Screen: https://calendly.com/integrations/api_webhooks

### 3. 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.

### 4. Enter the emailed authentication code

Calendly emails you an authentication code. Open the email, then type the code into the verification prompt to continue.

### 5. Copy the token into PopMCP

Click Copy token and paste the value into PopMCP's Personal Access Token field.

## Fields PopMCP asks for

- Personal Access Token (accessToken) [required]: 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.

## Verify

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

Cause: 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

Cause: 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

Cause: 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

Cause: 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

Cause: Those endpoints are Enterprise only regardless of token.

Fix: Skip those tools, or connect a token from an Enterprise organization.

### 429 Too Many Requests

Cause: 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.

---

Source: https://www.docs.popmcp.com/docs/integrations/calendly/