Human Resources · Integration
DeskTime
Add DeskTime to your product for your customers, and give your AI agents governed access to it.
DeskTime's API lives at desktime.com/api/v2/json and takes the key as an apiKey query parameter, with separate endpoints for a single employee's day and for the whole company on a given date. Data is returned per date rather than as a range, so building a week means one call per day, and the company endpoint is limited by how many employees the account holds. Time is reported as separate desktime, at-work, productive and idle figures plus offline time entries, and these do not sum in the obvious way because at-work includes approved offline periods that desktime time does not. Employee records carry a group and a role, and keys issued at team-admin level return only that group's people, which quietly narrows results without an error. fastn stores each customer's key at the right scope, handles the per-date fan-out and keeps the integration current.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own DeskTime account and choose which employee groups your product may read
Pull daily productive and idle time into a customer's own reporting view alongside your app's data
Reconcile logged project time in your product against DeskTime's recorded working time for the same day
Flag employees with recorded offline time that has not been categorised, for a manager to review
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Let an agent build a weekly working time summary for a team by fetching each date and combining the results
Have an agent identify days where at-work time and desktime time diverge sharply and explain why
Audit, per tenant, which employee records an agent read from DeskTime and at what key scope
Example prompt
What was the average productive time for our support team in DeskTime last week?
Set up DeskTime in 4 steps
- 01Enable the DeskTime connector from your fastn dashboard.
- 02Have each customer authorise their own DeskTime account, so calls run under their credentials rather than a shared key.
- 03Decide which employees, employment records and working time your product needs, map those fields, then enable the actions and triggers you want.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the DeskTime integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a DeskTime integration without building it. Your customers connect their own DeskTime account inside your product and work their employees, employment records and working time there, with no per-customer code on your side.
- Handle the part that actually costs time: HR data is sensitive and its access rules are stricter than most systems. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a DeskTime update is not your on-call problem.
- One integration serves your product and your agents. The same governed DeskTime connection powers in-product features and gives AI agents scoped, audited access, so you keep people data current without manual re-entry without wiring it twice.
Used by these teams
Compare with
Workday
BambooHR
GustoOften used alongside
Tools the same teams tend to run next to DeskTime, across other categories.
Slack
NetSuite
Notion
BoxDeskTime integration FAQ
How do I add a DeskTime integration to my product?
Enable the DeskTime connector in your fastn dashboard, then let each customer authenticate their own DeskTime account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no DeskTime client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own DeskTime account?
Yes. Every connection is scoped to the individual customer, so each authorises their own DeskTime account and only ever sees their own employees, employment records and working time. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this DeskTime integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. Let an agent build a weekly working time summary for a team by fetching each date and combining the results
Who maintains the DeskTime integration?
fastn does. When DeskTime changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
How is sensitive DeskTime employee data handled?
Access is scoped per tenant and limited to the fields you map, credentials are encrypted, and every read and write is logged. You expose only what your product actually needs rather than the whole employee record.
Can joiner, mover and leaver changes be automated?
Yes. Where DeskTime is where a hire, a role change or a departure is recorded, that change can trigger downstream provisioning or removal across the customer's other connected systems. Where DeskTime sits downstream of the HR system of record, the same event can be pushed into it so its worker list, schedules and access stay in step, which is where most of the manual effort sits.
What can I build with the DeskTime integration?
A common starting point: let a customer connect their own DeskTime account and choose which employee groups your product may read. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the DeskTime integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding DeskTime does not change your per-connector cost. You can start free with 3 connected accounts.
Add DeskTime to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.