ActionClockifyUpdated September 2026

What Clockify projects exist?

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

List Projects in Clockify — start free All 3 Clockify actions

List Projects in Clockify — start free

Inputs

The fields this action accepts.

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

Sample request

{
  "workspaceId": "{{trigger.workspaceId}}"
}

Returns

[
  {
    "id": "proj123",
    "name": "Client Project",
    "color": "#FF5722",
    "billable": true,
    "clientId": "client123"
  }
]

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

Triggered by

Apps that pair well as the trigger for List Projects.

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 Projects.

What does the List Projects action do in Clockify?

Returns every project in a workspace with client, hourly rate, billable settings. Useful for resolving project IDs at workflow-build time and for "project utilisation" reporting workflows that aggregate by project.

What inputs does List Projects require?

Required: Workspace ID. Every input accepts a static value or a variable from any upstream node in your workflow.

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 run history shows the failed step with its input and the error message Clockify 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 Projects support batch operations?

Run List Projects 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 Clockify's rate limits.

More actions

Other Clockify actions.

Action

Create Time Entry

Posts a duration-based entry with project, task, tags, billable flag. Useful for "calendar meeting marked as billable → auto-log time in Clockify" or for batch-importing time from external sources.

Action

List Workspaces

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.

List Projects in Clockify — start free