Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node operation, Retrieve Get User Details under the Active Directory resource, is designed to fetch detailed information about a user from an Active Directory service. It allows querying user details by specifying identifiers such as company ID and object GUID, along with additional filtering, ordering, and pagination options.

Typical use cases include:

  • Integrating Active Directory user data into workflows for identity verification.
  • Automating user profile synchronization between systems.
  • Retrieving specific user attributes for reporting or auditing purposes.

For example, you might use this node to get detailed information about a user in a particular company by providing the company's ID and the user's unique object GUID.

Properties

Name Meaning
Company Id Numeric identifier of the company to which the user belongs.
Object Guid Unique string identifier (GUID) of the user object in Active Directory.
Source Source system or domain from which to retrieve the user details.
X USER ID User ID used for authentication or identification in the request header.
Condition Optional query condition to filter or refine the search results.
Skip Number of records to skip for pagination purposes.
Limit Maximum number of records to return.
Order By Field(s) by which to order the returned user records.

Output

The node outputs JSON data containing the retrieved user details from Active Directory. The structure typically includes user attributes such as name, email, department, and other directory-specific fields depending on the queried user.

If binary data were involved (e.g., user photos), it would be included in a separate binary output field, but this operation focuses on JSON user detail data only.

Dependencies

  • Requires an API key credential or similar authentication token configured in n8n to access the Active Directory service.
  • Depends on the external Active Directory API endpoint that supports querying user details by company ID, object GUID, and other parameters.
  • Proper network connectivity and permissions to query the Active Directory service are necessary.

Troubleshooting

  • Missing or invalid credentials: Ensure the API key or authentication token is correctly set up in n8n credentials.
  • Invalid or missing required properties: Company Id, Object Guid, Source, and X USER ID are mandatory; verify these inputs are provided and valid.
  • API errors due to incorrect query parameters: Check the format and values of optional parameters like Condition, Skip, Limit, and Order By.
  • No user found: If the query returns no results, confirm that the Object Guid and Company Id correspond to an existing user.
  • Network or permission issues: Verify that the n8n instance has network access to the Active Directory API and that the authenticated user has sufficient permissions.

Links and References

Discussion