Productivity · Integration
Clockify
Add Clockify to your product for your customers, and give your AI agents governed access to it.
Clockify tracks time against projects and tasks, and the integration question is nearly always about aggregation rather than about the individual entry. One entry is trivial; what a product needs is time grouped by project, by person and by period, which is a report rather than a list. Workspaces are the tenancy boundary and a user can belong to several, so resolving which workspace a request applies to is the first step rather than an afterthought. Entries can be running rather than finished, and a running entry has no end time, which breaks any naive duration calculation. fastn scopes the key per customer and handles the workspace resolution.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own Clockify workspace so tracked time appears next to the work your product manages.
Read time grouped by project and person, which is the shape a report actually needs.
Start or log an entry from your product, so people track time where they already work.
Handle running entries correctly, rather than treating a missing end time as a zero duration.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reports how much time went to a project this month and who logged it.
An agent logs an entry within governed permissions, with the write audited per tenant.
An agent flags people with entries still running from a previous day.
Example prompt
How much time went to this project last month, broken down by person?
Set up Clockify in 4 steps
- 01Enable the Clockify connector from your fastn dashboard.
- 02Have each customer authorise their own Clockify account, so calls run under their credentials rather than a shared key.
- 03Decide which work items, assignees and due dates 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 Clockify integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Clockify integration without building it. Your customers connect their own Clockify account inside your product and work their work items, assignees and due dates there, with no per-customer code on your side.
- Handle the part that actually costs time: every team configures its own fields, statuses and workflow stages. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Clockify update is not your on-call problem.
- One integration serves your product and your agents. The same governed Clockify connection powers in-product features and gives AI agents scoped, audited access, so you keep work items in step with what happens in your product without wiring it twice.
Used by these teams
Compare with
Toggl Track
Harvest
JiraOften used alongside
Tools the same teams tend to run next to Clockify, across other categories.
Notion
Box
Docusign
AWS Simple Storage ServiceClockify integration FAQ
How do I add a Clockify integration to my product?
Enable the Clockify connector in your fastn dashboard, then let each customer authenticate their own Clockify account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Clockify client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Clockify account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Clockify account and only ever sees their own work items, assignees and due dates. 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 Clockify integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent reports how much time went to a project this month and who logged it.
Who maintains the Clockify integration?
fastn does. When Clockify 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.
Can my product create and update work in Clockify automatically?
Yes. Items can be created, updated, assigned and transitioned from your product, and changes made in Clockify can trigger your workflows in return.
Does it adapt to each team's own Clockify setup?
Yes. However a team has configured Clockify, whether that is custom fields, statuses and workflow stages or its own calendars and working hours, those are mapped per customer, so an unusual setup works without custom code from you.
What can I build with the Clockify integration?
A common starting point: let a customer connect their own Clockify workspace so tracked time appears next to the work your product manages. 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 Clockify integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Clockify does not change your per-connector cost. You can start free with 3 connected accounts.
Add Clockify to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.