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 such as users, teams, tickets, deals, contacts, companies, and more. Specifically, for the User resource with the List operation, it retrieves a list of users from the Teamleader system.
Common scenarios where this node is beneficial include:
- Synchronizing user data from Teamleader into other systems or databases.
- Automating workflows that require up-to-date user lists, such as sending notifications or generating reports.
- Filtering or processing user information in bulk within an automation pipeline.
For example, you could use this node to fetch all users and then filter them based on roles or departments before passing the data to another service.
Properties
| Name | Meaning |
|---|---|
| Limit | The number of user results to return. This controls pagination size when listing users. |
Note: The "Limit" property defaults to 50 and can be adjusted to control how many users are retrieved in one request.
Output
The node outputs a JSON array where each element represents a user object returned by the Teamleader API. The structure of each user object corresponds to the Teamleader API's user data schema, typically including fields like user ID, name, email, role, and other user-specific details.
If no data is returned but the request was successful, the output will contain an object with a message indicating this situation.
No binary data output is produced by this operation.
Dependencies
- Requires an OAuth2 API credential configured in n8n to authenticate requests against the Teamleader API.
- The node makes HTTP POST requests to the Teamleader API endpoint
https://api.focus.teamleader.euusing the specified operation path (e.g.,users.list). - Proper API permissions must be granted to the OAuth2 credential to access user data.
Troubleshooting
- No data returned but request was successful: This indicates the API call succeeded but returned no user data. Verify that users exist in the Teamleader account and that any filters applied do not exclude all results.
- No data got returned error: Thrown if the API response does not contain expected data. Check API credentials and network connectivity.
- API authentication errors: Ensure the OAuth2 credential is valid and has not expired.
- Limit too high: Setting the limit property to a very high number might cause performance issues or API rate limiting. Adjust accordingly.
Links and References
- Teamleader API Documentation
- Teamleader Users API Reference (for detailed user object schema and available endpoints)