How to Connect Calendly to OpenClaw

Log in to your Calendly account and navigate to app.calendly.com/integrations/api_webhooks. This is Calendly's developer integrations page — it is accessible from the main navigation under Integrations > API and Webhooks. Scroll to the 'Personal Access Tokens' section and click 'Generate New Token'. Give the token a descriptive name like 'OpenClaw Integration' — this helps you identify it later if you need to revoke it. Calendly will display the token value once. Copy it immediately and store it somewhere secure — you cannot view it again after closing the dialog. The token grants access to all Calendly resources associated with your account: events, event types, availability, users, and webhooks. Treat it like a password. Calendly Personal Access Tokens do not expire automatically, but you can revoke them at any time from the same page. Also note your Calendly user URI. You can find it by making a test API call to the /users/me endpoint (shown in the next step). The URI looks like `https://api.calendly.com/users/XXXXXXXXXXXXXXXXXXX` and is required as a filter parameter for most list endpoints.

1# Test your token and get your user URI (run in terminal)
2curl -H "Authorization: Bearer YOUR_CALENDLY_API_KEY" \
3     -H "Content-Type: application/json" \
4     https://api.calendly.com/users/me
5
6# Expected response includes:
7# {
8#   "resource": {
9#     "uri": "https://api.calendly.com/users/XXXXXXXXXXXXXXXXXXX",
10#     "name": "Your Name",
11#     "email": "you@example.com",
12#     ...
13#   }
14# }
15
16# Copy the "uri" value — you will need it for scoped API calls

Open your OpenClaw configuration file at `~/.openclaw/config.yaml` and add the Calendly integration block under the `integrations` key. This is a direct API integration, so it uses the `integrations` section rather than the `skills` section. The `api_key` field is your Calendly Personal Access Token. The `user_uri` field is the URI you retrieved in Step 1 — it is required to scope list endpoints to your own account. Without it, requests to list events or event types will return authorization errors. The `base_url` should always be `https://api.calendly.com` — do not change this. The `webhook_signing_key` field is optional and covered in Step 3; leave it empty for now. After saving the config file, reload OpenClaw with `openclaw reload` or restart the process. OpenClaw will validate that the API key can authenticate against the Calendly /users/me endpoint. Check the OpenClaw log for a confirmation message.

1# ~/.openclaw/config.yaml
2integrations:
3  calendly:
4    api_key: "YOUR_CALENDLY_PERSONAL_ACCESS_TOKEN"
5    user_uri: "https://api.calendly.com/users/XXXXXXXXXXXXXXXXXXX"
6    base_url: "https://api.calendly.com"
7    webhook_signing_key: ""     # Added in Step 3 if using webhooks
8    poll_interval: 300           # Seconds between event checks when not using webhooks (default: 300)
9    lookback_days: 1             # How many past days to include in event queries (default: 0)

With the config in place, verify the integration is working by querying your upcoming Calendly events. The Calendly API's `/scheduled_events` endpoint lists all events matching filters you provide. The `user` parameter scopes results to your account. The date format for `min_start_time` and `max_start_time` is ISO 8601: `2026-03-30T00:00:00.000000Z`. The API returns events in pages of up to 100 — if you have many events, use the `next_page_token` from the response to paginate. You can also query event types to see all the different meeting types you have configured in Calendly. Event types are the templates your invitees see when booking — knowing their URIs is useful for filtering events by meeting category. Run the test commands below and confirm you see your real Calendly data returned in the JSON responses. If you see a 403, double-check that the `user` parameter matches your user URI exactly.

1# List your upcoming scheduled events (next 7 days)
2curl -H "Authorization: Bearer YOUR_CALENDLY_API_KEY" \
3     "https://api.calendly.com/scheduled_events?user=https://api.calendly.com/users/YOUR_USER_ID&min_start_time=2026-03-30T00:00:00.000000Z&max_start_time=2026-04-06T00:00:00.000000Z&sort=start_time:asc"
4
5# List your event types (meeting templates)
6curl -H "Authorization: Bearer YOUR_CALENDLY_API_KEY" \
7     "https://api.calendly.com/event_types?user=https://api.calendly.com/users/YOUR_USER_ID"
8
9# Get details on a specific scheduled event
10curl -H "Authorization: Bearer YOUR_CALENDLY_API_KEY" \
11     "https://api.calendly.com/scheduled_events/EVENT_UUID/invitees"

Polling the API every few minutes works for scheduled summaries, but if you need OpenClaw to react immediately when a meeting is booked or cancelled, configure Calendly webhooks. Calendly will POST a payload to your OpenClaw webhook URL within seconds of each scheduling event. Webhooks require OpenClaw to be running in server mode with an accessible HTTP endpoint. If OpenClaw is running locally behind a router, you will need to expose it via a public URL — tools like ngrok, Cloudflare Tunnel, or a VPS deployment give you a stable public address. Create the webhook subscription via the Calendly API. The `url` parameter is your OpenClaw webhook endpoint. The `events` array specifies which Calendly events trigger the webhook — `invitee.created` fires on new bookings, `invitee.canceled` fires on cancellations. Calendly will provide a signing key in the response — add this to your OpenClaw config as `webhook_signing_key` to verify that payloads are genuinely from Calendly. For complex webhook workflows, RapidDev's team can help design multi-step automation flows that combine Calendly webhook data with other integrations in your OpenClaw stack.

1# Create a Calendly webhook subscription
2curl -X POST \
3     -H "Authorization: Bearer YOUR_CALENDLY_API_KEY" \
4     -H "Content-Type: application/json" \
5     -d '{
6       "url": "https://your-openclaw-endpoint.example.com/webhooks/calendly",
7       "events": ["invitee.created", "invitee.canceled"],
8       "organization": "https://api.calendly.com/organizations/YOUR_ORG_UUID",
9       "user": "https://api.calendly.com/users/YOUR_USER_UUID",
10       "scope": "user"
11     }' \
12     https://api.calendly.com/webhook_subscriptions
13
14# List existing webhook subscriptions
15curl -H "Authorization: Bearer YOUR_CALENDLY_API_KEY" \
16     "https://api.calendly.com/webhook_subscriptions?organization=https://api.calendly.com/organizations/YOUR_ORG_UUID&scope=user"
17
18# Example Calendly webhook payload (invitee.created):
19# {
20#   "event": "invitee.created",
21#   "payload": {
22#     "event_type": { "name": "30 Minute Meeting", ... },
23#     "invitee": { "name": "Jane Doe", "email": "jane@example.com", ... },
24#     "scheduled_event": { "start_time": "2026-04-01T14:00:00Z", ... }
25#   }
26# }

With event data flowing into OpenClaw via webhooks or polling, configure an automation workflow that reacts to new bookings. The pattern is: receive the Calendly event payload, extract invitee details (name, email, event type, scheduled time), then trigger downstream actions. A simple starting workflow posts a Slack message or sends an email when a new booking arrives. A more complex workflow might look up the invitee email in your CRM, add meeting notes to Notion, and send the invitee a personalized pre-meeting questionnaire — all triggered by a single Calendly booking. The OpenClaw workflow config uses the Calendly integration as the trigger source, specifying which event types activate the workflow. The `payload` fields from the Calendly webhook are available as template variables in the actions block. Test the workflow by creating a real test booking through your Calendly link with a test email address. Verify the automation fires correctly before routing real invitees through it.

1# ~/.openclaw/config.yaml — booking notification workflow
2workflows:
3  calendly-booking-notify:
4    trigger:
5      integration: calendly
6      event: invitee.created
7    actions:
8      - type: log
9        message: "New Calendly booking: {{payload.invitee.name}} ({{payload.invitee.email}}) for {{payload.event_type.name}} at {{payload.scheduled_event.start_time}}"
10
11  calendly-cancellation-alert:
12    trigger:
13      integration: calendly
14      event: invitee.canceled
15    actions:
16      - type: log
17        message: "Cancelled: {{payload.invitee.name}} cancelled {{payload.event_type.name}} scheduled for {{payload.scheduled_event.start_time}}"