Actions65
- Custom Field Definitions Actions
- Knowledge Documents Actions
- Media Actions
- Used Tags Actions
- Webhooks Actions
- Sse Actions
- Accounts Actions
- User Management Actions
- Inbox Management Actions
- Conversations Actions
- Conversation Messages Actions
- Bot Actions
- Contacts Actions
User Management → User Controller Find One
AI-generatedOverview
This node operation retrieves detailed information about a single user from the User Management system based on a specified user ID. It supports pagination, filtering, sorting, and selecting specific fields or related entities to include in the response. This is useful for scenarios where you need to fetch comprehensive user data, including related company information, with control over the amount and type of data returned.
Use Case Examples
- Fetching a user's profile by their unique ID including their company details.
- Retrieving a user's basic contact information with specific fields like email and name.
- Getting a paginated and sorted list of user-related data with filters applied.
Properties
| Name | Meaning |
|---|---|
| Id | The unique identifier of the user to retrieve. This is a required field. |
| Page | The page number for paginated results, starting at 1. |
| Limit | The number of items to return per page. |
| Relations | Specifies related entities to include in the response, supporting nested relations using dot notation. |
| Select | Specifies which fields of the user to include in the response. |
| Sort | Defines the sorting order of the results, which can include multiple fields and order directions. |
| Filters | JSON object defining filter conditions to apply to the query. |
| Request Options | Additional request settings such as batching, SSL handling, proxy configuration, and timeout. |
Output
JSON
id- The unique identifier of the user.email- The user's email address.firstName- The user's first name.lastName- The user's last name.company- The company related to the user, including nested account information if requested.
Dependencies
- An API key credential for authenticating with the Kuantia CRM API
Troubleshooting
- Ensure the 'Id' field is provided and correctly formatted, as it is required to fetch the user.
- Check network connectivity and API credentials if requests fail or time out.
- If using relations or select fields, verify that the specified fields exist in the API schema to avoid errors.
- Adjust timeout and proxy settings in Request Options if experiencing slow or blocked requests.