AvantGuard - CIPP icon

AvantGuard - CIPP

AvantGuard - CIPP

Actions136

Overview

This node interacts with the AvantGuard CIPP API to retrieve specific list information based on execution, clearance, immediate, and ID parameters. It is designed to fetch detailed data for a given identifier within a tenant filter context. This node is useful in scenarios where you need to programmatically access or audit list entries filtered by tenant and identified by a unique ID, such as compliance checks, security audits, or data synchronization tasks.

Properties

Name Meaning
Id The unique identifier of the list entry to retrieve.
Tenantfilter A string used to filter the data by tenant, ensuring the query is scoped appropriately.

Output

The node outputs JSON data representing the retrieved list entry corresponding to the provided Id and Tenantfilter. The structure of the JSON output matches the response schema defined by the AvantGuard CIPP API for this endpoint. The output contains detailed information about the requested list item.

No binary data output is indicated.

Dependencies

  • Requires an API key credential for authenticating with the AvantGuard CIPP API.
  • The base URL for the API is configured via credentials and appended with /api.
  • The node uses HTTP headers to accept and send JSON content (Accept: application/json, Content-Type: application/json).
  • The node depends on the @avantguardllc/n8n-openapi-node package and an OpenAPI specification file (openapi.json) bundled with the node.

Troubleshooting

  • Missing or invalid API credentials: Ensure that the API key credential is correctly set up and has the necessary permissions.
  • Incorrect Id or Tenantfilter: Providing invalid or non-existent identifiers will result in empty or error responses. Verify these values before running the node.
  • Network or connectivity issues: Confirm that the base URL configured in credentials is reachable from the n8n instance.
  • Unexpected API errors: Check the API documentation for error codes returned and ensure the request conforms to expected formats.

Links and References

Discussion