Features by connector
Pick a connector to see exactly what Claude can read and write — and filter by plan tier to see which capabilities are included in Solo or unlock at Team+. Every tool is a slice of real work you can hand off in plain English and review before it lands in the system of record.
Every hour, captured — without opening the tracker
Cohesive360 connects Claude to Clockify through 54 tools covering live timers (start / stop / what's running), time-entry logging and correction, project / client / task / tag management, and workspace-wide summary + detailed reports. Works on every Clockify plan including free, with a single API key. Combined with your other connectors, Claude can reconstruct an untracked day from calls and case activity and file the missing entries for review — turning lost billable hours into logged ones.
Time tracking by talking
Start, stop, and log time without leaving Claude. “Start a timer for the Acme deposition prep” or “log 9–11 this morning on Figueroa” — the entry lands in Clockify exactly as if you'd clicked it.
Reports in plain English
“How much time did we put into the Smith matter this month?” becomes a grouped Clockify report — by project, client, person, or day — summarized by Claude instead of exported to a spreadsheet.
The time you forgot to track
Pair it with your other connectors: Claude can reconstruct your day from calls, documents, and tasks, then file the missing entries into Clockify — the hours that usually evaporate.
Plan tiers gate capability areas, not API access scope. For pricing, see the Pricing page.
Capabilities
2 workflow areas in Team plan+. Click any capability to expand its “what you can ask” examples and the underlying tool names. Use the sidebar to jump.
Record and browse expenses (with categories) and create draft invoices for clients. These are Clockify paid-plan features — on a free workspace the tools explain the plan requirement instead of failing cryptically.
Record and browse expenses (with categories) and create draft invoices for clients. These are Clockify paid-plan features — on a free workspace the tools explain the plan requirement instead of failing cryptically.
What you can ask Claude
- “Record a $45 filing-fee expense on the Acme project for today”
- “List this month's expenses”
- “Create a draft invoice for client Figueroa in USD”
Underlying tools (8)
list_expensesget_expensecreate_expensedelete_expenselist_expense_categorieslist_invoicesget_invoicecreate_invoicePTO policies, balances, and requests (submit for yourself or, as admin, for a teammate), timesheet approval queues, and scheduled assignments — workspace-wide or per project. Paid-plan features with graceful plan notices on free workspaces.
PTO policies, balances, and requests (submit for yourself or, as admin, for a teammate), timesheet approval queues, and scheduled assignments — workspace-wide or per project. Paid-plan features with graceful plan notices on free workspaces.
What you can ask Claude
- “What's my PTO balance?”
- “Request next Friday off under the vacation policy”
- “Any pending timesheet approvals?”
- “Show the schedule for the Acme project”
Underlying tools (6)
list_timeoff_policieslist_timeoff_requestscreate_timeoff_requestget_timeoff_balancelist_approval_requestslist_scheduled_assignmentsLimits and roadmap
What the Clockifyconnector can't do today, and why. We update this when things change.
Not in the vendor's API
Capabilities the vendor handles through admin UI or internal endpoints rather than the documented public API.
- Paid-plan features need a paid Clockify workspace. Expenses, invoices, time off, approvals, scheduling, custom fields, and invoiced-marking are all wired in the connector — but Clockify only serves them on paid plans. On a free workspace those tools return a clear plan notice instead of data; everything else works on free.
- Per-seat admin actions. Inviting workspace members, changing roles, and workspace settings stay in Clockify's UI — the connector deliberately doesn't manage your team.
On the roadmap
Technically possible but not yet prioritised. Email product@cohesive360.com if any of these would change your decision to roll out.
- Tracking time for other people. Timers and entries act as the connected user only. Reports can read the whole workspace, but writes are always your own — no impersonation.
Safeguards built into the connector
Defensive behaviours we put in the client because the underlying systems don't.
Your key, encrypted at rest
The Clockify API key is stored AES-256-GCM-encrypted in a per-user vault, bound to your account — it is never logged, never shared between users, and deleted the moment you disconnect.
Scoped to what your key can see
The connector inherits exactly your Clockify permissions — your workspaces, your entries, the projects you can access. There is no privilege escalation and no service account.
Deletes require intent
Every delete tool (entries, projects, clients, tasks, tags, expenses, webhooks) targets a single item and is documented confirm-first — Claude is instructed to check with you before removing anything. Projects and clients additionally follow Clockify's archive-before-delete rule, and there is no bulk delete anywhere.
Writes you can read back
Every write returns the created/updated entry with its ID and computed duration, so Claude verifies what actually landed in Clockify rather than assuming success.
What Clockify via Cohesive360 is not
Honest boundaries — what Claude through this connector cannot guarantee.
Cohesive360 is a facilitation channel between Claude (Anthropic) and your Clockifytenant. Claude's responses are Anthropic's output; the underlying data is the vendor's system of record. We transport requests and responses; we do not generate, review, or validate Claude's output, and we do not operate the vendor's API.
Claude can be wrong. It can misread a record, misinterpret a date, draft against the wrong matter, or summarise incorrectly. Treat every draft as a draft — review it before you accept it, particularly anything that affects a deadline, a client communication, or a matter already in motion.
The vendor can be unavailable. The API can rate-limit, return errors, or reject requests for reasons specific to your tenant configuration. When that happens, Claude will tell you — but we have no control over when or why the vendor refuses a call.