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 Info operation, it retrieves detailed information about a single user by their ID.
Common scenarios where this node is beneficial include:
- Fetching detailed user profile data for display or processing in workflows.
- Integrating user information into CRM or support systems.
- Automating user-related tasks based on retrieved user details.
For example, you might use this node to get a user's full profile before assigning them a task or sending a notification.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the user whose information you want to retrieve. This is a required string input. |
Output
The node outputs JSON data containing the detailed information of the requested user. The structure corresponds to the user object returned by the Teamleader API's user info endpoint. It typically includes fields such as user name, email, role, status, and other profile details.
If multiple items are processed, the output will be an array of user objects.
No binary data output is produced by this operation.
Dependencies
- Requires an OAuth2 API credential configured for Teamleader with appropriate permissions to access user data.
- The node makes HTTP POST requests to the Teamleader API endpoint
https://api.focus.teamleader.euusing the/users.infooperation path. - Proper API authentication token must be provided via the configured OAuth2 credentials.
Troubleshooting
- No data returned but request was successful: This message indicates that the API call succeeded but no user data was found for the given ID. Verify that the user ID is correct and exists in Teamleader.
- No data got returned: This error means the response did not contain expected data. Check API permissions and ensure the user ID parameter is valid.
- API errors: If the node throws errors related to authorization or invalid parameters, confirm that the OAuth2 credentials are valid and have sufficient scope, and that all required parameters (like user ID) are correctly set.
- Network issues or incorrect API URLs can also cause failures; verify connectivity and configuration.
Links and References
- Teamleader API Documentation
- Teamleader User Info API endpoint documentation (referenced from above link)