Actions60
- User Actions
- Teams Actions
- Custom Fields Actions
- Tickets Actions
- Deals Actions
- Webhooks Actions
- Contacts Actions
- Companies Actions
- Bussiness Types Actions
- Tags Actions
- Deal Phases Actions
- Invoices Actions
- Subscriptions Actions
- Products Actions
- Projects Actions
- Tasks Actions
- Files Actions
Overview
This node integrates with the Teamleader API to perform various operations on different resources. Specifically, for the User resource and the List days off operation, it retrieves information about the days off of a specified user. This can be useful in scenarios such as managing employee availability, planning projects around team members' absences, or automating HR workflows.
For example, a company could use this node to automatically fetch and display users' days off in a calendar system or trigger notifications when a user is on leave.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the user whose days off you want to list. This is a required string input. |
Output
The output is a JSON array containing objects that represent the days off for the specified user. Each object includes details about individual days off as returned by the Teamleader API. The exact structure depends on the API response but typically includes date ranges and possibly reasons or types of absence.
No binary data output is produced by this operation.
Dependencies
- Requires an OAuth2 API credential configured for Teamleader.
- The node makes POST requests to the Teamleader API endpoint
https://api.focus.teamleader.euwith the path corresponding to the selected operation (users.listDaysOff). - Proper API permissions are needed to access user days off data.
Troubleshooting
- No data returned but request was successful: This message indicates that the API call succeeded but no days off data was found for the given user ID. Verify the user ID is correct and that the user has recorded days off.
- No data got returned: This error means the API response did not contain expected data. Check API credentials, permissions, and ensure the user ID exists.
- API errors: If the API returns errors (e.g., authentication failure, invalid parameters), the node will throw an error. Ensure the OAuth2 token is valid and the input parameters are correctly set.
- Empty or missing ID: Since the user ID is required, leaving it empty will cause the operation to fail. Always provide a valid user ID.
Links and References
- Teamleader API Documentation
- Teamleader Users API Reference (for detailed info on user-related endpoints)