Integrations · Productivity

Connect Calendly to Well

Pull your meeting schedules and contact details directly into your workspace

What Well pulls from Calendly

Calendly feeds person record into Well as a source. The connection is read-only; disconnect at any time from your workspace settings to revoke Calendly’s access.

From Calendly		In Well	Relation
Person record		Contact	Resolves to

Sync mode: MCP hybrid
Refresh: live + reconciliation reads
Direction: Calendly → Well

3 triggers from Calendly.

When a Calendly meeting is booked
Reads the scheduled event with its time, type, and invitee and stores it as a Well document so the booking is captured next to the contact.
Trigger·Document
When a Calendly invitee is resolved
Captures the invitee's name and email from the booking and links them to a company in your graph.
Trigger·Company
When a Calendly meeting is cancelled
Detects a cancelled event so the booking document stays in sync with the contact's actual activity.
Trigger·Document

What Well does with your Calendly connection

Connect

Connect Calendly over OAuth (MCP DCR): Well registers a client through Calendly's OAuth Dynamic Client Registration and you approve on Calendly's side, so the password never reaches Well; Well holds only a scoped token it can refresh.

Sync

Well brings person record in from Calendly through live reads, backed by a periodic reconciliation pass. The first sync backfills history in the background and the connection stays live after.

Enrich

Well resolves each Calendly entity into contact, assigns categories, and links every record to an audit trail across the rest of your connected tools.

Available

Your data from Calendly lands in the workspace as contact you can search, chart, and automate.

Questions Calendly unlocks

Ask in plain language. Well answers from your connected Calendly connection, resolved against the rest of your stack.

Ask Well

Ask anything about your Calendly connection

Summarise this month

What needs attention?

Find unmatched records

Ask about your Calendly connection…

1 agent skill runs on Calendly.

Well lists Calendly in the connection check every skill runs before it answers. No skill reads it for a figure yet.

Connects and checks Calendly

Check your connections

See what is connected, what is syncing, and what is missing.

Browse all skills

Connect Calendly in three steps

01
Connect your Calendly account
Authorize Well to access your Calendly account through the connection portal.
- AuthOAuth (MCP DCR)
- DiscoveryMCP .well-known
02
Map your entities
Confirm the connection to allow Well to read your scheduled events and invitee profiles.
- Mappingpreconfigured by Well
03
Use the data
Verify that your meeting history and contact details are visible within your workspace directory.
- First syncstarts as soon as connect completes

Well only reads your scheduling data and will never modify your calendar events.

How Calendly stays secure with Well

Well connects to Calendly's MCP server via the Model Context Protocol. The MCP server itself handles credential issuance through OAuth Dynamic Client Registration; Well never sees a long-lived Calendly secret. Tokens are scoped to the person record Calendly exposes and refreshed server-side. Reads only, Well cannot modify or delete Calendly records.

OAuth (MCP DCR)Encrypted at restGDPR compliant

Read the full privacy and security policy

Scopes Well requests

Read Calendly records
Resources the Calendly MCP server exposes, scoped by your OAuth approval.
granted
Resolve person record across your stack
Match identifiers in Calendly against the same entities your other connected tools expose, so each record carries cross-tool context.
granted
Modify or delete Calendly records
Not granted; Calendly is read-only in Well. Write-back is opt-in per connector when a write surface exists.
refused
Store Calendly passwords or session cookies
Authentication runs through OAuth (MCP DCR) tokens we never see.
refused