Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node operation, Retrieve Ad Group Users under the Active Directory resource, is designed to fetch users belonging to a specific Active Directory group. It queries an external API (likely a Connect Secure API) to retrieve user information based on the group's unique identifier and other optional filtering parameters.

Typical use cases include:

  • Automating user management workflows by retrieving group membership details.
  • Synchronizing Active Directory group users with other systems or databases.
  • Auditing or reporting on group memberships within an organization.

For example, you might use this node to get all users in a "Sales" AD group to update mailing lists or access permissions automatically.

Properties

Name Meaning
Company Id Numeric identifier of the company for which the AD group users are being retrieved.
Object Guid The unique object GUID of the Active Directory group whose users you want to retrieve.
X USER ID User identifier used as a header for authentication or tracking purposes in the request.
Condition Optional query condition to filter the results further based on custom criteria.
Skip Number of records to skip in the result set (for pagination).
Limit Maximum number of records to return (for pagination).
Order By Field name(s) to order the results by.

Output

The node outputs JSON data representing the list of users retrieved from the specified Active Directory group. Each item in the output typically contains user attributes as returned by the API, such as user IDs, names, email addresses, and other relevant user properties.

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

Dependencies

  • Requires an active connection to the Connect Secure API or equivalent service that exposes Active Directory group user data.
  • Needs an API key or authentication token configured in n8n credentials to authorize requests.
  • The node sends HTTP requests with query parameters and headers as per the input properties.

Troubleshooting

  • Missing or invalid Company Id/Object Guid: The API will likely return errors if these required fields are not provided or incorrect. Ensure these values are accurate.
  • Authentication errors: If the X USER ID header or API credentials are missing or invalid, the request will fail with authorization errors.
  • Pagination issues: Improper use of skip and limit may cause incomplete data retrieval or empty results.
  • Invalid query conditions: Malformed or unsupported conditions in the condition property can lead to API errors or no results.

To resolve these:

  • Double-check all required inputs.
  • Verify API credentials and user ID headers.
  • Test query conditions separately to ensure correctness.
  • Use reasonable values for pagination parameters.

Links and References

Discussion