ActionClockifyUpdated June 2026

How do I add a Clockify time entry?

Short answer: You can create time entry in Clockify by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Clockify Create Time Entry action to a workflow, map its 6 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Use this action All 3 Clockify actions

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Workspace ID workspaceId	string	Required	Workspace ID
Project ID projectId	string	Optional	Project ID
Description description	string	Optional	Description. e.g. "Working on feature X"
Start Time start	datetime	Required	Start Time. (date/time)
End Time end	datetime	Required	End Time. (date/time)
Billable billable	boolean	Optional	Billable

Sample request

{
  "workspaceId": "{{trigger.workspaceId}}",
  "projectId": "{{trigger.projectId}}",
  "description": "Working on feature X",
  "start": "{{trigger.start}}",
  "end": "{{trigger.end}}"
}

Returns

{
  "id": "te123",
  "billable": true,
  "description": "Working on feature X",
  "timeInterval": {
    "end": "2026-04-11T11:30:00Z",
    "start": "2026-04-11T09:00:00Z",
    "duration": "PT2H30M"
  }
}

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about Create Time Entry.

What does the Create Time Entry action do in Clockify?

Posts a duration-based entry with project, task, tags, billable flag. Useful for "calendar meeting marked as billable → auto-log time in Clockify" or for batch-importing time from external sources.

What inputs does Create Time Entry require?

Required: Workspace ID, Start Time, End Time. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if Clockify returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Create Time Entry support batch operations?

Yes. Run Create Time Entry inside a Loop node to process arrays. TinyCommand handles Clockify's rate limits automatically so you don't have to throttle manually.

More actions

Other Clockify actions.

Action

List Projects

Returns every project in a workspace with client, hourly rate, billable settings. Useful for resolving project IDs at workflow-build time and for "project utilisation" reporting workflows that aggregate by project.