Clockify
Read and write Clockify projects, clients, tasks, tags and user time entries with custom fields.
Use tracked hours for client billing, payroll and project cost reporting.
Source actions
9
Destination actions
10
Data types
9
Validation status
Implemented · fixture tested.
Implementation is checked against provider-shaped fixtures for every action, authentication failures, rate limits, pagination and duplicate safety. Provider sandbox and authorised account validation are recorded separately when credential-backed runs are completed.
What you can map
clients
- Create clientDestinationNot retried automatically
Creates a client in the configured workspace.
- List clientsSource
Workspace clients.
- Update clientDestinationDuplicate protected
Updates supplied client fields, including archiving.
current user
- Get current userSource
The API key's user, whose ID is needed for time entry reads.
custom fields
- List custom fieldsSource
Workspace custom field definitions with type and allowed values.
projects
- Create projectDestinationNot retried automatically
Creates a project in the configured workspace.
- List projectsSource
Workspace projects with client, rates and estimates.
- Update projectDestinationDuplicate protected
Updates supplied project fields, including archiving.
tags
- Create tagDestinationNot retried automatically
Creates a workspace tag.
- List tagsSource
Workspace tags.
- Update tagDestinationDuplicate protected
Renames or archives a tag.
tasks
- Create taskDestinationNot retried automatically
Creates a task in a project.
- List project tasksSource
Tasks of a project with assignees, estimates and status.
- Update taskDestinationDuplicate protected
Updates a task; Clockify requires the task name on every update.
time entries
- Create time entryDestinationNot retried automatically
Creates a time entry for the key's user.
- List user time entriesSource
Time entries of one user in the workspace, newest first.
- Update time entryDestinationDuplicate protected
Replaces a time entry; fields not sent are cleared.
users
- List workspace usersSource
Members of the configured workspace.
workspaces
- List workspacesSource
Workspaces the key's user belongs to.
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.
Provider events
Clockify workspace webhooks for time entry, project, client and task events. Nexra event triggers are not yet available; flows run on demand or on a schedule.
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.