Integrations · Productivity

Connect Timeslope to Well

Connect Timeslope to make it reachable from conversation and your agents in Well. Timeslope exposes no structured records to sync today, so this is a reach connection, not a data feed.

Connect TimeslopeSee what Well does

What Well pulls from Timeslope

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

From Timeslope		In Well	Relation
Timeslope		Workspace context	Reachable from

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

What Well does with your Timeslope connection

Connect

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

Sync

Connecting Timeslope makes it reachable from your workspace; Timeslope exposes no structured records for Well to sync into the data model today.

Enrich

With no records to ingest, Timeslope adds reach without enrichment; entity resolution and categorisation run for connectors that bring structured data in.

Available

Timeslope is reachable from conversation and agents in your workspace; once it exposes structured records they land alongside the rest of your connected tools.

Questions Timeslope unlocks

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

Ask Well

Ask anything about your Timeslope connection

Summarise this month

What needs attention?

Find unmatched records

Ask about your Timeslope connection…

Connect Timeslope in three steps

01
Authorise Timeslope via MCP
From Well's Connections panel, search for Timeslope and click Connect. Well discovers Timeslope's MCP OAuth metadata from its .well-known endpoint, registers a client via Dynamic Client Registration, and routes you through the authorize prompt on Timeslope's side. No client credentials to paste.
- AuthOAuth (MCP DCR)
- DiscoveryMCP .well-known
- MCP servermcp.timeslope.com/mcp
02
Make it reachable
The connection puts Timeslope within reach of your workspace and its agents. Timeslope exposes no structured record for Well to map into an invoice, transaction, or account today, so there is no records table to set up and Well will not invent one to fill the step.
- Mappingnone (reach-only)
03
Use it from your workspace
Use the connection to let an agent reach Timeslope in the same place it reaches the rest of your stack. If Timeslope later exposes structured entities that map onto what Well captures, the data-flow section would reflect the real records.
- Availabilityreachable as soon as connect completes

This is a reach-and-availability connection, not a records feed, so nothing backfills.

How Timeslope stays secure with Well

Well connects to Timeslope's MCP server (mcp.timeslope.com/mcp) via the Model Context Protocol. The MCP server handles credential issuance through OAuth Dynamic Client Registration, so Well never holds a long-lived Timeslope secret. Because Timeslope maps no structured entity today, the token simply makes Timeslope reachable from your workspace rather than syncing records. The connection is read-only and grants Well nothing it could change in Timeslope.

OAuth (MCP DCR)Encrypted at restGDPR compliant

Read the full privacy and security policy

Scopes Well requestsmcp.timeslope.com/mcp

Read Timeslope records
Resources the Timeslope MCP server exposes, scoped by your OAuth approval.
granted
Reach Timeslope from your workspace
The grant makes Timeslope reachable from conversation and your agents. It maps no structured entity, so Well resolves no records and can change nothing in Timeslope.
granted
Modify or delete Timeslope records
Not granted; Timeslope is read-only in Well. Write-back is opt-in per connector when a write surface exists.
refused
Store Timeslope passwords or session cookies
Authentication runs through OAuth (MCP DCR) tokens we never see.
refused

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

Frequently asked questions about Timeslope and Well

How do I connect Timeslope to Well, and how long does it take?

Choose Timeslope in Well's Connections panel and authorise it over its MCP server. Well discovers the OAuth metadata from the MCP endpoint and registers a client via Dynamic Client Registration, so there are no keys to paste. The handshake completes in about a minute and puts Timeslope within reach of your workspace and its agents.

What does Well sync from Timeslope today?

No structured record, and the page is candid about that. Timeslope exposes no supported target model for Well to turn into an invoice, transaction, or account, so there is no records table to configure and nothing is pulled into your workspace. The connection is about reach, not a data feed.

If nothing is synced, what does connecting Timeslope give me?

It lets an agent working in your workspace reach Timeslope in the same place it reaches the rest of your stack, instead of treating it as a separate destination. This is a reach-and-availability connection: honest about not pulling structured records that Timeslope does not expose.

Will Timeslope ever bring records into the workspace?

Only if and when Timeslope exposes structured entities through its MCP server that map onto what Well captures. Until then Well will not invent a synced record to make the page look fuller; if that changes, the data-flow section would reflect the real entities.

What happens if I disconnect Timeslope?

Disconnecting Timeslope in Well revokes the OAuth token and ends the MCP reach immediately. Because nothing structured was being synced, there are no workspace records to retain or purge; it simply removes Timeslope from the set of tools your agents can reach through Well.