Clockify
Turn requests and orders into Clockify work, and keep status in step across your tools.
27 ways to read, 10 ways to write, each write switched on by you.
Quality checks
Built and tested with example responses.
- Ready to connect: doneEvery listed action is built in.
- Built and tested with example responses: doneEach action is built from the provider’s published API and tested against example responses, errors, rate limits and paging.
Connected, approved, proven.
The things teams do most with Clockify, an example flow with a person in the loop, and what Nexra keeps as proof.
Top actions
- Create clientApproval by rule
- Create projectApproval by rule
- Detailed reportRead
Example flow
- Clockify · Detailed reportDone
- Clockify · Create clientNeeds approval
- Nexra · Record the decision and result in the evidence chainProven
Example workflow. Routine runs go through on their own. Only a change your rules flag, such as one over a limit you set, waits for the right person, who sees the exact change and the rule before it reaches Clockify.
What gets logged
- Whether it ran on its own or who approved it, and under which rule
- A fingerprint of the exact request sent to Clockify
- Clockify's reply: what it created or changed
- One entry in the evidence chain, linked to the one before
Try this in the sandbox
Run the whole flow with test data in your sandbox, then connect your own account when you are ready to go live.
For developers
Technical detail
Read and write Clockify projects, clients, tasks, tags and time entries; read groups, approvals, expenses, schedules and time off, and run summary and detailed reports.
CAKE.com API docs- Source actions
- 27
- Destination actions
- 10
- Data types
- 20
What you can map
Reads are always available. Writes are off until you switch them on for a connection, and governed writes follow your policies.
Approval requests1
- List approval requestsSource
Timesheet and expense approval requests with totals (read-only).
Clients4
- Create clientDestinationNot retried automaticallyApproval before production
Creates a client in the configured workspace.
- Get clientSource
One client.
- List clientsSource
Workspace clients.
- Update clientDestinationProvider duplicate protectionApproval before production
Updates supplied client fields, including archiving.
Created records1
- List newly created recordsSourceIncremental
Records of one kind (time entries, projects, clients and more) created in the workspace in a time range, from Clockify's experimental entity changes API.
Current user1
- Get current userSource
The API key's user, whose ID is needed for time entry reads.
Custom fields1
- List custom fieldsSource
Workspace custom field definitions with type and allowed values.
Detailed report1
- Detailed reportSource
Reports API detailed report: every time entry for all users the key can see in a period, with project, task, client and amounts.
Expense categories1
- List expense categoriesSource
Expense categories with unit prices.
Expenses2
- Get expenseSource
One expense (read-only).
- List expensesSource
Workspace expenses, optionally for one user (read-only).
Holidays1
- List holidaysSource
Workspace holidays with their assigned users and groups.
Projects4
- Create projectDestinationNot retried automaticallyApproval before production
Creates a project in the configured workspace.
- Get projectSource
One project with rates, estimates and memberships.
- List projectsSource
Workspace projects with client, rates and estimates.
- Update projectDestinationProvider duplicate protectionApproval before production
Updates supplied project fields, including archiving.
Running time entries1
- List running timersSource
Time entries currently in progress across the workspace.
Scheduling assignments1
- List scheduled assignmentsSource
Scheduling assignments (planned work per user and project) in a period.
Summary report1
- Summary reportSource
Reports API summary: tracked and billable time and amounts grouped by up to three levels (for example project, then user).
Tags4
- Create tagDestinationNot retried automaticallyApproval before production
Creates a workspace tag.
- Get tagSource
One tag.
- List tagsSource
Workspace tags.
- Update tagDestinationProvider duplicate protectionApproval before production
Renames or archives a tag.
Tasks4
- Create taskDestinationNot retried automaticallyApproval before production
Creates a task in a project.
- Get taskSource
One project task.
- List project tasksSource
Tasks of a project with assignees, estimates and status.
- Update taskDestinationProvider duplicate protectionApproval before production
Updates a task; Clockify requires the task name on every update.
Time entries4
- Create time entryDestinationNot retried automaticallyApproval before production
Creates a time entry for the key's user.
- Get time entrySource
One time entry in the workspace.
- List user time entriesSource
Time entries of one user in the workspace, newest first.
- Update time entryDestinationProvider duplicate protectionApproval before production
Replaces a time entry; fields not sent are cleared.
Time off policies1
- List time off policiesSource
Time off policies with approval and accrual settings.
User groups1
- List user groupsSource
User groups with their members and team managers.
Users1
- List workspace usersSource
Members of the configured workspace.
Workspaces2
- Get workspaceSource
The configured workspace with its plan, rates and settings.
- List workspacesSource
Workspaces the key's user belongs to.
Access and limits
- Authentication
- API key (X-Api-Key header)
- Plans and access
- All plans; tasks, billable rates and custom fields depend on the workspace plan. The API key acts as its user. Reading other users' time entries and managing projects need workspace admin or manager rights. Subdomain workspaces need a workspace-specific API key.
- Test environment
- Use a free Clockify workspace for testing.
- Rate limits
- Clockify documents 50 requests per second per workspace for add-on tokens; no separate limit is documented for API keys. HTTP 429 is retried with backoff.
- Pagination
- page and page-size (default 50); Nexra requests up to 200 per page.
- Provider events
- Clockify workspace webhooks for time entry, project, client and task events. Flows run on demand, on a schedule, or when a scheduled check finds new or changed records.
Before you build a flow
- Subdomain workspaces (https://<name>.clockify.me) are not supported; use a regional or global API origin.
- Time entry updates replace the whole entry: send every field to keep, including start.
- Rates are in cents (hourlyRate.amount 12300 = 123.00).
- page-size has no documented maximum; Nexra caps pages at 200 records.
- Clockify has no idempotency key; uncertain creates are not repeated automatically.
- Reports use the Reports API: reports.api.clockify.me for the global origin, or /report on the regional host (declared as the reports origin). Ranges are limited to one year.
- Summary reports return the first grouping level with its second-level children; deeper levels are not flattened.
- Approval requests, expenses, expense categories, scheduling assignments, holidays and time off policies are read-only; approving, submitting, withdrawing, and creating expenses or time off are not implemented.
- Expense receipts are not downloaded. Deleting projects, clients, tasks, tags, time entries or expenses is intentionally excluded.
Developer reference
- Create the CAKE.com credentials described above with the narrowest permissions your flows need.
- In Nexra, open Connect, then Connections, then New connection, choose Clockify, enter its settings and credentials, and tick only the write actions you need. Connection guide
- Test the connection, then use its actions as flow sources and destinations. Flow guide
Machine-readable detail: GET /api/public/connect/connectors/clockify and the Connections API.