Short answer: Drop the "Toggl Track → 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 workspace_id | number | Required | The Workspace ID assigned by Toggl. Find via the corresponding list/search operation in this app. Use the exact ID, not a name or label. |
Description description | string | Optional | Description. e.g. "Working on task" |
Project ID project_id | number | Optional | The Project ID assigned by Toggl. Find via the corresponding list/search operation in this app. Use the exact ID, not a name or label. |
Start Time start | datetime | Required | Start Time. (date/time) |
Duration (seconds) duration | number | Required | Duration in seconds, e.g. 3600 for 1 hour |
Billable billable | boolean | Optional | Billable |
{"workspace_id": "{{trigger.workspace_id}}","description": "Working on task","project_id": "{{trigger.project_id}}","start": "{{trigger.start}}","duration": "{{trigger.duration}}"}
{"id": 12345,"start": "2026-04-11T09:00:00Z","duration": 3600,"description": "Working on task","workspace_id": 100}
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.