ClockifySettings
| Setting | What it is |
|---|---|
| ConnectionRequired | The Clockify connection the step signs in with. |
| Workspace id override | Leave empty to use the workspace on the connection. Pick another workspace the same key can reach, or type its id — the List workspaces node gives you the ids. |
| Name contains | text |
| Status | "" or "INACTIVE" or "VISIBLE" or "INVISIBLE" |
| Belongs to | Which kind of record the field hangs off. Leave empty for all of them; Clockify publishes no closed list, so anything it accepts is accepted here. |
Technical details
| Key | Value |
|---|---|
connection | texta connection id from `requires.connections` (provider `clockify`) |
workspaceId | texta value from the vendor's own list |
name | text |
status | "" or "INACTIVE" or "VISIBLE" or "INVISIBLE" |
entityType | text |
Output
| Field | Type |
|---|---|
customFields | array |
customFieldCountCustom fields in this answer | number |
Sample output, and the expression for each field
- customFieldCount0
- customFields[]
Errors
When a step of this node stops a run, the run page shows a code. Look it up:
Example step
The step as a flow file holds it. Replace each value in <…>.
{
"config": {
"connection": "<connection id>",
"entityType": "",
"name": "",
"status": "",
"workspaceId": ""
},
"label": "List custom fields",
"type": "clockify.listCustomFields",
"version": 1
}