Teamleader icon

Teamleader

Consume Teamleader API

Actions60

Overview

This node integrates with the Teamleader API to retrieve data related to various resources. Specifically, for the Custom Fields resource with the List operation, it fetches a list of all custom field definitions configured in the Teamleader account.

This functionality is useful when you want to dynamically access or manage custom fields used across your CRM or project management workflows. For example, you might use this node to:

  • Retrieve all available custom fields to map them into another system.
  • Display or process custom field metadata before creating or updating records.
  • Automate reporting or synchronization tasks involving custom field data.

Properties

Name Meaning
Limit The number of results to return. This controls how many custom field definitions are fetched in one request. Default is 50.

Output

The node outputs an array of JSON objects representing the custom field definitions retrieved from the Teamleader API. Each object corresponds to a single custom field definition and contains its metadata as provided by the API.

The output is structured as follows:

  • json: An array where each element is a custom field definition object with properties such as ID, name, type, and other relevant metadata describing the custom field.

No binary data is output by this node.

Dependencies

  • Requires an OAuth2 API credential configured for Teamleader to authenticate requests.
  • Makes HTTP POST requests to the Teamleader API endpoint at https://api.focus.teamleader.eu.
  • The node uses the /customFieldDefinitions.list API method to fetch the list of custom fields.

Troubleshooting

  • No data returned but request was successful: This message indicates that the API call succeeded but no custom fields were found. Verify that custom fields exist in your Teamleader account.
  • No data got returned: This error occurs if the API response does not contain expected data. Check your API credentials and permissions.
  • Authentication errors: Ensure the OAuth2 credentials are valid and have the necessary scopes to access custom field definitions.
  • Limit parameter issues: Setting the limit too high may cause performance issues or API rate limiting. Adjust the limit according to your needs.

Links and References

Discussion