ActionToggl TrackUpdated September 2026

How do I list every workspace the connected Toggl user can access?

Short answer: You can list workspaces in Toggl Track by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Toggl Track List Workspaces action to a workflow, map its 0 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

List Workspaces in Toggl Track — start free
Sample request
{}
Returns
[
{
"id": 100,
"name": "My Workspace",
"premium": true,
"default_currency": "USD"
}
]

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

Triggered by

Apps that pair well as the trigger for List Workspaces.

Any of these apps can fire this action as part of a workflow.

FAQ

Questions about List Workspaces.

What does the List Workspaces action do in Toggl Track?
Lists all Toggl Track workspaces the connected user belongs to. Required first step for any flow that needs a workspace_id.
What inputs does List Workspaces require?
List Workspaces has no required inputs. Sensible defaults are applied if you leave fields blank.
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 Toggl Track returns an error?
The run history shows the failed step with its input and the error message Toggl Track returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.
Does List Workspaces support batch operations?
Run List Workspaces inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Toggl Track's rate limits.
More actions

Other Toggl Track actions.

List Workspaces in Toggl Track — start free