Teamleader icon

Teamleader

Consume Teamleader API

Actions60

Overview

This node integrates with the Teamleader API to retrieve various types of data related to business management. Specifically, for the User resource and the Get week schedule operation, it fetches the weekly working schedule information of a specified user. This is useful in scenarios where you need to automate workflows based on a user's availability or working hours, such as scheduling meetings, assigning tasks, or managing resources efficiently.

For example, you could use this node to:

  • Automatically check a user's weekly schedule before booking appointments.
  • Integrate with calendar systems to reflect user availability.
  • Generate reports on employee working hours or shifts.

Properties

Name Meaning
ID The unique identifier of the user whose week schedule you want to retrieve. This is a required string input.

Output

The output is a JSON array containing the user's weekly schedule data as returned by the Teamleader API. The structure typically includes details about the user's working days, hours, and any special scheduling configurations enabled by the "Weekly working schedule" feature in Teamleader.

  • The json output field contains the schedule information for the specified user.
  • No binary data is output by this operation.

Dependencies

  • Requires an OAuth2 API credential configured for Teamleader with appropriate permissions to access user schedules.
  • The node makes HTTP POST requests to the Teamleader API endpoint at https://api.focus.teamleader.eu.
  • The environment must have internet access to communicate with the Teamleader API.

Troubleshooting

  • No data returned but request was successful: This message indicates that the API call succeeded but no schedule data was found for the given user ID. Verify that the user ID is correct and that the user has the Weekly working schedule feature enabled.
  • No data got returned: This error means the API response did not contain expected data. Check if the user exists and the API credentials have sufficient permissions.
  • Authentication errors: Ensure the OAuth2 credentials are valid and properly configured.
  • Invalid or missing ID: The ID property is required; ensure it is provided and correctly formatted.

Links and References

Discussion