ActionClockifyUpdated May 2026

What Clockify workspaces can I access?

Short answer: Drop the "Clockify → List Workspaces" action anywhere in your workflow, map the inputs from upstream nodes, and publish.

Use this action All 3 Clockify actions

Sample request

{}

Returns

[
  {
    "id": "ws123",
    "name": "My Workspace",
    "memberships": [
      {
        "userId": "user123",
        "hourlyRate": {
          "amount": 5000,
          "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.

Google Sheets → Clockify

2 Google Sheets triggers

HubSpot → Clockify

18 HubSpot triggers

FAQ

Questions about List Workspaces.

What does the List Workspaces action do in Clockify?

Returns every workspace the connected user is a member of. Multi-workspace users (agencies tracking time across client workspaces) configure one Tiny Command connection per workspace they want to track.

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

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

More actions