Actions95
- Comment Actions
- Custom Field Actions
- Event Actions
- File Actions
- Invoice Actions
- Note Actions
- Notification Actions
- Pinned Item Actions
- Project Actions
- Project Label Actions
- State Actions
- Sub Task Actions
- Task Actions
- Activate
- Create
- Create Public Link
- Create Task Description
- Create Task Reminder
- Delete
- Delete Public Link
- Delete Task Reminder
- Delete Total Time Estimate
- Delete User Time Estimate
- Edit
- Finish
- Get Finished Tasks
- Get Many
- Get Task
- Get Task Description
- Move Task
- Set Total Time Estimate
- Set User Time Estimate
- Tasks In Task List
- Task Label Actions
- Task List Actions
- Time Tracking Actions
- User Actions
- Work Report Actions
User → Get Out Of Office
AI-generatedSummary
Retrieves the out-of-office status for a selected Freelo user. The user is chosen from a dropdown or supplied as an ID/expression.
Inputs
- User Name or ID (required) — The Freelo user to look up. Pick from the list loaded by getUsers, or enter a custom ID or expression. Declared to be sent as the
workerbody property. - Request Options — Optional node settings: batching (items per batch, interval in ms), ignore SSL certificate issues, HTTP proxy, and request timeout in ms (default 10000).
Output shape
The out-of-office data returned by the Freelo API for the selected user, as n8n items.
The source pack is signature-level only, so the exact endpoint, HTTP method and response fields could not be verified. The userId parameter is shared with the Enable and Disable Out Of Office operations.
Examples
Example 1: Check whether a teammate is out of office before assigning them a task.
Resource: User; Operation: Get Out Of Office; User Name or ID: select the teammate from the dropdown.
Example 2: Look up out-of-office status for user IDs coming from a previous node.
User Name or ID set to an expression such as {{ $json.userId }}; optionally set Request Options > Batching to throttle requests.