Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node operation, Retrieve Ad Domain Details, is designed to query and fetch details about Active Directory domains from a Connect Secure API. It allows users to specify various parameters such as company ID, source, user identification, filtering conditions, pagination controls (skip and limit), and sorting order to tailor the query results.

Typical use cases include:

  • Integrating Active Directory domain information into workflows for auditing or reporting.
  • Automating retrieval of domain details for synchronization with other systems.
  • Filtering and paginating large sets of domain data based on custom conditions.

For example, a user might retrieve all domain details for a specific company, skipping the first 10 records and limiting the output to 50 entries, ordered by domain name.

Properties

Name Meaning
Company Id The unique identifier of the company for which Active Directory domain details are fetched.
Source The source system or context from which to retrieve the domain details.
X USER ID User identifier sent as a header to authenticate or track the request.
Condition Optional query condition to filter the domain details returned.
Skip Number of records to skip in the result set (used for pagination).
Limit Maximum number of records to return (used for pagination).
Order By Field(s) by which to order the returned domain details.

Output

The node outputs JSON data containing the retrieved Active Directory domain details according to the specified query parameters. The structure typically includes an array of domain objects with their respective attributes as provided by the Connect Secure API.

No binary data output is indicated for this operation.

Dependencies

  • Requires an active connection to the Connect Secure API.
  • Needs an API authentication token or credential configured in n8n to authorize requests.
  • The node depends on the external Connect Secure service endpoint that exposes Active Directory domain details.

Troubleshooting

  • Common issues:

    • Missing or invalid API credentials can cause authentication failures.
    • Incorrect or missing required properties like Company Id, Source, or X USER ID may lead to request errors.
    • Improperly formatted Condition strings could result in no data returned or server errors.
    • Pagination parameters (Skip and Limit) must be non-negative integers; otherwise, the API might reject the request.
  • Error messages:

    • Authentication errors usually indicate invalid or expired API tokens; reconfigure credentials.
    • Validation errors on input parameters suggest checking the property values for correctness.
    • Network or timeout errors imply connectivity issues with the Connect Secure API endpoint.

Links and References

Discussion