Integrations · Productivity

Connect Timeslope to Well

Name: Timeslope entities in Well
Creator: Well

Read Timeslope clients, the people who logged the work, and the invoices that bill it into Well through its MCP server. Billed work lands against the client it belongs to, so what each client owes is queryable beside its deals.

Connect TimeslopeSee what Well does

What Well pulls from Timeslope

Timeslope feeds session, project, member 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
Session	Time entry	Indexes as
Project	Workspace context	Groups under
Member	Team member	Resolves to

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

Well brings session, project, and member in from Timeslope 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 Timeslope entity into time entry, workspace context, and team member, assigns categories, and links every record to an audit trail across the rest of your connected tools.

Available

Your data from Timeslope lands in the workspace as time entry, workspace context, and team member you can search, chart, and automate.

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 through its MCP server
Select Timeslope in Well's Connections panel to begin. Well fetches the OAuth metadata from the Timeslope MCP server at mcp.timeslope.com, registers via Dynamic Client Registration, and routes you to Timeslope to approve the read scopes, with no keys to manage.
- AuthOAuth (MCP DCR)
- DiscoveryMCP .well-known
- MCP servermcp.timeslope.com/mcp
02
Map your entities
Well reads your clients, the people who logged the work, and the invoices that bill it, mapping a client to a company, a team member to a person, and a billable record to an invoice through Well's data-views layer.
- Mappingpreconfigured by Well
03
Use the data
Then ask what a client has been billed in conversation, table invoiced work by client, or let an agent join billing to the deal it belongs to. Timeslope is an INPUT connector, so the read runs one way and your time records are never changed.
- First syncstarts as soon as connect completes

Connecting takes about a minute. Current invoices are read on connect and the earlier billing history backfills in the background.

How Timeslope stays secure with Well

Well talks to Timeslope through its MCP server at mcp.timeslope.com using the Model Context Protocol, and OAuth Dynamic Client Registration means the Timeslope credential is never held by Well. The granted token is scoped to the clients, people, and invoices Timeslope exposes and refreshes server-side. The connection reads the billing; it cannot create an invoice or change a rate 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
Resolve session, project, and member across your stack
Match identifiers in Timeslope against the same entities your other connected tools expose, so each record carries cross-tool context.
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

Choose Timeslope in Well's Connections panel to start. Well fetches the OAuth metadata from the Timeslope MCP server at mcp.timeslope.com, registers via Dynamic Client Registration, and routes you to Timeslope to approve the read scopes. There are no keys to manage, and the consent screen keeps the choice of what Well may read with you.

The clients, the people who logged the work, and the invoices that bill it. Timeslope maps to the company, people, and invoice entities, so a client resolves to a company, a team member to a person, and a billable record to an invoice against the client it belongs to. The read is one-way; Well pulls the billing in and never edits a timesheet or rate back in Timeslope.

Yes. Each Timeslope invoice arrives joined to the client it bills and the people whose time it covers, so billed work for a client sits in the same workspace as its deals and contacts. Ask what a client has been invoiced this quarter and Well answers from the joined record rather than sending you back to the Timeslope dashboard.

No, and the page is candid about the boundary. Timeslope exposes its clients, people, and invoices to Well, but not a settled-payment record, so Well reads what was billed rather than what has cleared a bank account. Billed work is structured against the client; reconciling the payment that settles it relies on whichever connector carries that side of your finances.

Well reads clients, people, and invoices through the Timeslope MCP connection and folds new billing in as it is read, with the first connect pulling existing invoice history in the background. Timeslope stays the system of record for the time and rates; Well keeps a queryable copy so billed work sits next to the rest of your workspace.

Disconnecting Timeslope in Well revokes the token and ends the reads right away, and since the connection only ever read, nothing needs reversing on Timeslope's side. The clients, people, and invoices already read stay in your workspace for reporting, so a question about billed work keeps answering after the connection is gone.