ClockifyRequest time off
BetaChanges data
Submits a Clockify time off request for yourself or a colleague.
Settings
| 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. |
| Policy idRequired | Which kind of leave this is — the List time off policies node gives you the ids. |
| User id | Empty files the request for the person the API key belongs to. Filing it for a colleague needs the right role in Clockify. |
| First dayRequired | text |
| Last dayRequired | text |
| Days | How many days to take off the balance. Zero lets Clockify work it out from the dates. |
| Half a day | true/false |
| Which half | "FIRST_HALF" or "SECOND_HALF" or "NOT_DEFINED" |
| Note | text |
Technical details
| Key | Value |
|---|---|
connection | texta connection id from `requires.connections` (provider `clockify`) |
workspaceId | texta value from the vendor's own list |
policyId | text |
userId | text |
startDate | text |
endDate | text |
days | number, by default 0 |
isHalfDay | true/false, by default false |
halfDayPeriod | "FIRST_HALF" or "SECOND_HALF" or "NOT_DEFINED", by default "NOT_DEFINED"used when `isHalfDay` is true |
note | text |
Output
| Field | Type |
|---|---|
requestId | string |
requestTime off request | object |
Sample output, and the expression for each field
- request
- id"r-1"
- requestId"r-1"
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>",
"days": 0,
"endDate": "<last day>",
"halfDayPeriod": "NOT_DEFINED",
"isHalfDay": false,
"note": "",
"policyId": "<policy id>",
"startDate": "<first day>",
"userId": "",
"workspaceId": ""
},
"label": "Request time off",
"type": "clockify.createTimeOffRequest",
"version": 1
}