Clockify n8n integrationAutomate Clockify with n8n.

Adds a client to the workspace and hands back its record, including the ID you reuse to attach projects to that client later in the run.

• Client Name: the name of the client being created, usually mapped from an upstream node with {{ $json.company }} rather than typed in.

Removes a client from the workspace. There is no undo on the n8n side, so a filter or an approval step in front of it is a reasonable habit.

• Client ID: the client to remove. The node does not flag it as required, but with an empty value there is nothing to target, so map it from the previous node, for example {{ $json.id }}.

Reads one client and returns its record, which is how you check a name or confirm an ID before a later operation writes anything.

• Client ID: the identifier of the client to read. Not flagged as required in the node, yet the operation needs it to know which client, so feed it from the item in hand.

Returns the clients of the workspace as one item per client, with filtering and sorting handled by the API rather than by a Code node downstream.

• Return All: on, n8n pages through every client; off, it stops at Limit.
• Archived: keeps or excludes archived clients, which matters on an old workspace.
• Name: filters clients by name.
• Sort Order: ASCENDING or DESCENDING.

Edits a client that already exists, which is the operation to reach for when a company changes name or when an old client should stop appearing in pickers.

• Name: required, and it is the value the client ends up with, so send the current name when you only mean to change something else.
• Client ID: which client gets updated.
• Address: the address of the client being updated.
• Archived: archives the client instead of deleting it.

Opens a project in the workspace so hours have somewhere to land, and returns the project record for the steps that follow.

• Project Name: required, the name of the project being created.
• Client Name or ID: attaches the project to a client, from the list or an expression.
• Billable: marks the project as billable from the start.
• Estimate: sets the estimated time.
• Color, Is Public, Note: visual and access details, plus a note about the project.

Takes a project out of the workspace. Because reporting is built on projects, this one deserves a confirmation step upstream rather than a raw connection from a list.

• Project ID: required, and it is an identifier, not the project name shown in the interface. Read it from a previous Get many projects step with {{ $json.id }}.

Fetches a single project and returns what Clockify holds on it, which is how a workflow checks a project before writing hours or tasks against it.

• Project ID: required. The dropdown elsewhere in the node shows names, this field wants the identifier, typically carried over from the trigger or from a list step.

Lists projects with the widest filter set of the node, 12 optional fields, so most of the sorting you would write by hand happens in the API call.

• Return All and Limit: full pagination, or a capped batch.
• Client Names or IDs, Contains Client, Client Status: narrow the list to the projects of given clients.
• Archived, Billable, Is Template, Name: the usual state filters.
• Sort Column (NAME, CLIENT_NAME, DURATION) and Sort Order.

Changes the settings of a live project without touching the hours already logged on it. Only the fields you add are sent, so a run can flip one flag and leave the rest alone.

• Project ID: required, the project to edit.
• Billable: switches a project from internal to billable when a contract is signed.
• Estimate, Name, Note, Color, Is Public, Client Name or ID: the rest of the editable record.

Adds a tag to the workspace so entries can be labelled by anything your projects do not already say, for instance a delivery phase or a funding line.

• Name: required, the name of the tag being created. Keep the spelling generated by the workflow stable, since tags are matched by people in the Clockify interface afterwards.

Drops a tag from the workspace. Useful when a labelling scheme is replaced and the old values keep showing up in the picker.

• Tag ID: required, the identifier of the tag, which you normally get from a Get many tags step earlier in the same workflow rather than from a hardcoded value.

Returns the tags of the workspace, which is the step that turns tag names into the IDs other operations expect.

• Return All: on for the whole list, off to stop at Limit.
• Name: filters on the tag name.
• Archived: includes or leaves out archived tags.
• Sort Column (NAME) and Sort Order (ASCENDING, DESCENDING).

Renames a tag or archives it, so a label can change wording without breaking the entries already carrying it.

• Tag ID: required, the tag to edit.
• Name: the new wording.
• Archived: hides the tag from new entries while the historical ones keep it.

Puts a task inside a project, which is the level people actually pick when they start a timer.

• Project Name or ID: required, from the list or an expression; a task cannot exist outside a project.
• Task Name: required, the name of the task to create.
• Assignee Names or IDs: who the task goes to.
• Estimate: expected time in the 2:30 format, two hours and thirty minutes.

Removes a task from its project. Both coordinates are needed, since a task ID is read inside the project it belongs to.

• Project Name or ID: required, the project holding the task.
• Task ID: required, the ID of the task to delete, not its label.

Looks up one task and returns its record, useful for reading an estimate or a status before deciding what the workflow does next.

• Project Name or ID: required, the project the task sits in.
• Task ID: required, the ID of the task to get.

Walks through the tasks of one project. The scope is the project, not the workspace, so a report across several projects loops over them.

• Project Name or ID: required, the project to read.
• Return All and Limit: every task, or a capped batch.
• Is Active: keeps only the tasks still open.
• Name: text to match in the task name.
• Sort Column (NAME) and Sort Order.

Moves a task along: new owner, new estimate, or the switch to done once the work is delivered.

• Project Name or ID and Task ID: both required to target the task.
• Status: ACTIVE or DONE.
• Assignee Names or IDs: reassigns the task.
• Estimate: revised time in the 2:30 format.
• Name: renames it.

Writes an entry into Clockify from data that started somewhere else, which is how hours tracked in another tool end up in the same timesheet as everyone else's.

• Start: required, a date and time; leaving it empty stops the node.
• End: closes the entry, otherwise it stays running.
• Project Name or ID, Task ID, Tag Names or IDs: where the hours are charged.
• Description, Billable, Custom Fields: the rest of the entry.

Erases one entry from the timesheet. Hours are what invoices are built on, so this is the operation to guard with a check on who and what, before the run reaches it.

• Time Entry ID: required, the entry to erase, normally carried by the item that triggered the workflow.

Reads a single entry. Two optional fields change the shape of what comes back, and they save a round of extra lookups.

• Time Entry ID: required.
• Hydrated: returns the project, task and tags in full instead of their IDs alone.
• Consider Duration Format: rounds the duration to minutes or seconds, following the hh:mm or hh:mm:ss format set in the workspace.

Corrects an entry after it was logged, the operation that absorbs the everyday mistakes: wrong project, missing tag, forgotten stop.

• Time Entry ID: required.
• Start and End: fix the boundaries of the entry.
• Project Name or ID, Task ID, Tag Names or IDs: recharge the hours somewhere else.
• Description, Billable, Custom Fields: the rest of the record.

Lists the people of the workspace, which is how a workflow turns a name or an email into the user ID other steps need.

• Return All and Limit: everyone, or a first batch.
• Email and Name: filter on a string contained in either.
• Status: ACTIVE, INACTIVE, PENDING or DECLINED, handy to spot invitations nobody accepted.
• Sort Column (EMAIL, NAME, HOURLYRATE) and Sort Order.

Clockify hangs everything on a workspace, so this operation returns the workspaces the API key can reach, each with its own ID. Every other operation and the Clockify Trigger ask for that ID before anything else.

• Return All: on, n8n pages through the API and returns every workspace on the account; off, it stops at the number set in Limit.
• Limit: the maximum number of workspaces returned, enough when you only need the first one to feed {{ $json.id }} into the next node.