Short answer: Drop the "Clockify → Create Time Entry" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
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 |
{"workspaceId": "{{trigger.workspaceId}}","projectId": "{{trigger.projectId}}","description": "Working on feature X","start": "{{trigger.start}}","end": "{{trigger.end}}"}
{"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.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.