Teamleader

Overview

This node integrates with the Teamleader API to perform various operations on different resources such as users, teams, subscriptions, deals, tickets, and more. Specifically, for the Subscriptions resource with the List operation, it retrieves a list of all subscriptions from the Teamleader system.

This is useful in scenarios where you want to automate workflows involving subscription data management, such as syncing subscription lists with other systems, generating reports, or triggering actions based on subscription statuses.

Example use case:

• Automatically fetch all active subscriptions to update a CRM or billing system.
• Retrieve subscription data periodically to monitor customer engagement or subscription renewals.

Properties

The "Limit" property controls how many subscription records are fetched in one request, allowing you to manage data volume and pagination.

Output

The node outputs an array of JSON objects representing subscriptions retrieved from the Teamleader API. Each object corresponds to a subscription record with its associated fields as provided by the API.

• The output field json contains the subscription data.
• If no data is returned but the request was successful, the node outputs a message indicating this.
• Errors during the API call result in error messages unless the node is configured to continue on failure.

No binary data output is involved in this operation.

Dependencies

• Requires an OAuth2 API credential for authenticating with the Teamleader API.
• The node makes HTTP POST requests to the Teamleader API endpoint at https://api.focus.teamleader.eu.
• Proper configuration of the OAuth2 credentials within n8n is necessary for successful API calls.

Troubleshooting

• No data returned but request was successful: This indicates that the API responded without errors but did not return any subscription data. Verify that there are subscriptions available in the Teamleader account.
• No data got returned: An error thrown when the response does not contain expected data. Check API permissions and ensure the OAuth2 token is valid.
• API errors: Network issues, invalid credentials, or incorrect parameters can cause API errors. Review the error message for details and verify credentials and input parameters.
• Limit parameter issues: Setting the limit too high might cause performance issues or API rate limiting. Adjust the limit according to your needs and API constraints.

Links and References

• Teamleader API Documentation
• n8n OAuth2 Credential Setup