Integrations · Productivity

Connect Clockwise to Well

Index Clockwise meeting, focus block, and attendee so questions about calendar event and time allocation answer themselves in conversation.

What Well pulls from Clockwise

Clockwise feeds meeting, focus block, attendee into Well as a source. The connection is read-only; disconnect at any time from your workspace settings to revoke Clockwise’s access.

From ClockwiseIn Well
Meeting
Calendar event
Focus block
Time allocation
Attendee
Team member
Clockwise logo
Sync mode
MCP hybrid
Refresh
live + reconciliation reads
Direction
Clockwise → Well

What Well does with your Clockwise connection

Connect

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

Sync

Well brings meeting, focus block, and attendee in from Clockwise on live events backed by periodic reconciliation reads. The first sync backfills history in the background and the connection stays live after.

Enrich

Well resolves each Clockwise entity into calendar event, time allocation, and team member, assigns categories, and links every record to an audit trail across the rest of your connected tools.

Available

Your data from Clockwise lands in the workspace as calendar event, time allocation, and team member you can search, chart, and automate.

Questions Clockwise unlocks

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

Ask Well

Ask anything about your Clockwise connection

Summarise this month
What needs attention?
Find unmatched records

Ask about your Clockwise connection…

Connect Clockwise in three steps

  1. 01

    Authorise Clockwise via MCP

    From Well's Connections panel, search for Clockwise and click Connect. Well discovers Clockwise's MCP OAuth metadata from its .well-known endpoint, registers a client via Dynamic Client Registration, and routes you through the authorize prompt on Clockwise's side. No client credentials to paste.

    • AuthOAuth (MCP DCR)
    • DiscoveryMCP .well-known
    • MCP servermcp.getclockwise.com/mcp
  2. 02

    Map your entities

    Well's MCP client discovers meeting, focus block, and attendee from Clockwise that Clockwise's MCP server exposes and brings them into your workspace using the canonical mappings defined in Well's data-views layer. You can inspect the workspace data model from Settings > Data Model.

    • Mappingpreconfigured by Well
  3. 03

    Use the data

    Ask questions in conversation, build records tables, or let agents act on Clockwise records. Because Clockwise ships through MCP, Well treats every entity it exposes as queryable graph state alongside the rest of your connected tools.

    • First syncstarts as soon as connect completes

MCP handshake typically completes under a minute on warm connections. Resource enumeration runs immediately after; full backfill of historical Clockwise records happens in the background.

How Clockwise stays secure with Well

Well connects to Clockwise's MCP server (mcp.getclockwise.com/mcp) via the Model Context Protocol. The MCP server itself handles credential issuance through OAuth Dynamic Client Registration; Well never sees a long-lived Clockwise secret. Tokens are scoped to the meeting, focus block, and attendee Clockwise exposes and refreshed server-side. Reads only, Well cannot modify or delete Clockwise records.

OAuth (MCP DCR)Encrypted at restGDPR compliant
Read the full privacy and security policy
Scopes Well requestsmcp.getclockwise.com/mcp
  • Read Clockwise records

    Resources the Clockwise MCP server exposes, scoped by your OAuth approval.

    granted
  • Resolve meeting, focus block, and attendee across your stack

    Match identifiers in Clockwise against the same entities your other connected tools expose, so each record carries cross-tool context.

    granted
  • Modify or delete Clockwise records

    Not granted; Clockwise is read-only in Well. Write-back is opt-in per connector when a write surface exists.

    refused
  • Store Clockwise passwords or session cookies

    Authentication runs through OAuth (MCP DCR) tokens we never see.

    refused
Disconnect any time from Well settings or Clockwise’s admin panel.

Frequently asked questions about Clockwise and Well

From Well, open Connections, find Clockwise, and click Connect. Well discovers the OAuth metadata at mcp.getclockwise.com/mcp/.well-known/oauth-authorization-server, registers a client on the fly via Dynamic Client Registration, and walks you through the authorize prompt on Clockwise's side. No client_id or client_secret to paste; the handshake takes roughly a minute.

Well brings in meeting, focus block, and attendee from Clockwise and reshapes each entity into your workspace: meeting becomes calendar event; focus block becomes time allocation. Every record arrives with the source identifier preserved, so Clockwise stays the source of truth while Well lets you query the data alongside the rest of your stack.

Every Clockwise record is scanned for references to companies, contacts, and deal names in your workspace. Matches are surfaced inline on each entity's workspace page: a customer's profile shows the Clockwise tasks and threads that mention them, ranked by recency and reach.

Yes. Clockwise attendees are indexed in your workspace as team member, so questions like "show me last week's attendees from Clockwise" return them with the original Clockwise link, the workspace context, and any related records (counterparty, period, attached document) joined inline.

Well combines live Clockwise events with periodic reconciliation reads of meeting, focus block, and attendee. New rows appear within seconds when Clockwise pushes them; periodic reads catch anything a push missed. The first connect backfills history from Clockwise in the background.

Open Connections > Clockwise in Well and click Disconnect. Well calls Clockwise's token revocation endpoint and stops calling Clockwise immediately on its side; provider-side propagation to Clockwise's admin panel varies by provider. The meeting, focus block, and attendee Well already synced stay in your workspace by default; ask Support to purge them if your compliance flow requires it.

Clockwise records are stored in the region Well operates for your workspace. Specific region details and the steps to change region are available from Support. See /privacy for the current data-handling policy.

Clockwise logo

Ready to connect Clockwise?

Connect once. Every meeting, focus block, attendee from Clockwise becomes searchable, queryable, and ready for your agents and tables. Disconnect any time.