Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node operation, Retrieve Ad Groups View, is designed to query and retrieve information about Active Directory groups via an API. It allows users to specify filtering conditions, pagination controls, and sorting preferences to customize the data retrieval. This is useful in scenarios where you need to integrate Active Directory group data into workflows, such as syncing group memberships, auditing group configurations, or managing access control lists.

Practical examples include:

  • Fetching a subset of AD groups that meet certain criteria (e.g., groups created after a specific date).
  • Paginating through large sets of groups by skipping and limiting records.
  • Ordering groups by name or creation date for reporting purposes.

Properties

Name Meaning
X USER ID User Id header value required for authentication or identification in the API request.
Condition Query condition string to filter the groups based on specified criteria.
Skip Number of records to skip, used for pagination.
Limit Maximum number of records to return, used to limit the size of the result set.
Order By Field(s) by which to order the results, e.g., group name or creation date.

Output

The node outputs JSON data representing the retrieved Active Directory groups matching the query parameters. The structure typically includes an array of group objects with their attributes as returned by the API. There is no indication of binary data output for this operation.

Dependencies

  • Requires an API key or token credential configured in n8n to authenticate requests to the Connect Secure API.
  • Depends on the external Connect Secure API service that exposes Active Directory group data.
  • No additional environment variables are explicitly required beyond standard API credential setup.

Troubleshooting

  • Common issues:

    • Missing or invalid user ID header (X USER ID) may cause authentication failures.
    • Incorrect query syntax in the "Condition" property can lead to empty results or API errors.
    • Pagination parameters (Skip and Limit) set incorrectly might result in unexpected subsets of data.
    • Improper "Order By" values could cause the API to reject the request or ignore sorting.

  • Error messages:

    • Authentication errors usually indicate missing or invalid credentials or headers.
    • API response errors related to query parameters suggest checking the format and supported fields for filtering and ordering.
    • Network or connectivity errors imply verifying API endpoint accessibility and credential validity.

Links and References

Discussion