ActionToggl TrackUpdated June 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 All 3 Toggl Track actions

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.

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 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 List Workspaces support batch operations?

Yes. Run List Workspaces inside a Loop node to process arrays. TinyCommand handles Toggl Track's rate limits automatically so you don't have to throttle manually.

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

Apps that pair well as the trigger for List Workspaces.

Questions about List Workspaces.

Other Toggl Track actions.