AvantGuard - CIPP icon

AvantGuard - CIPP

AvantGuard - CIPP

Actions136

Overview

This node operation, "Retrieve List Graph Request" under the "List" resource, is designed to perform a graph-based query on a list resource via an API. It allows users to specify various parameters that control the nature of the graph request, such as filtering criteria, pagination behavior, and which properties to retrieve. This can be useful in scenarios where you need to extract complex relational data or aggregated information from a list endpoint that supports graph queries.

Practical examples include:

  • Retrieving a filtered subset of items from a large dataset with specific properties.
  • Counting items matching certain criteria without retrieving full data (using count-only mode).
  • Fetching graph-related data structures for visualization or further processing.

Properties

Name Meaning
Countonly Whether to return only the count of matching items instead of full data.
Endpoint The API endpoint path to target for the graph request.
Graphfilter Filter expression to apply on the graph query to limit results.
Ignoreerrors Flag indicating whether to ignore errors during the request processing.
Listproperties Specifies which properties of the list items to retrieve in the response.
Nopagination Indicates whether to disable pagination and retrieve all results in one request.
(Unnamed) An unnamed required string property included in the query parameters (purpose unclear).

Output

The node outputs JSON data representing the result of the graph request against the list resource. This JSON typically contains the requested list items or counts based on the input parameters. The structure depends on the API's response format but generally includes the filtered list data with specified properties.

No binary data output is indicated by the source code or properties.

Dependencies

  • Requires an API key credential for authentication to the AvantGuard CIPP API.
  • Needs the base URL of the API resource, provided via credentials.
  • Depends on the @avantguardllc/n8n-openapi-node package for building properties and handling requests.
  • The node sends HTTP requests with headers specifying JSON content type and expects JSON responses.

Troubleshooting

  • Common issues:

    • Incorrect or missing API credentials will cause authentication failures.
    • Providing invalid filter expressions or endpoint paths may result in API errors.
    • Omitting required properties like countonly, endpoint, or graphfilter will likely cause the request to fail.
    • The unnamed required property without a display name might confuse users; ensure it is set correctly or clarify its purpose.
  • Error messages:

    • Authentication errors: Verify API key and base URL credentials.
    • Validation errors from the API: Check the correctness of query parameters, especially filters and endpoint.
    • Network errors: Confirm network connectivity and API availability.

Links and References

Discussion