AvantGuard - CIPP icon

AvantGuard - CIPP

AvantGuard - CIPP

Actions136

Overview

This node operation, "Retrieve List Deleted Items," is designed to fetch items that have been deleted from a specified list within a tenant context. It is useful in scenarios where users need to audit, review, or restore deleted entries from a list managed by an external service. For example, it can be used to track removed records in a project management tool or to synchronize deletions across systems.

Properties

Name Meaning
Tenantfilter A required string used as a query parameter to filter the deleted items by tenant scope.

Output

The node outputs JSON data representing the deleted items retrieved from the specified list filtered by the tenant. The structure of the JSON output depends on the external API's response but typically includes details about each deleted item such as identifiers, deletion timestamps, and possibly metadata related to the deletion event.

No binary data output is indicated for this operation.

Dependencies

  • Requires an API key credential for authentication with the external AvantGuard CIPP API.
  • The base URL for API requests is configured dynamically from the node credentials.
  • The node uses the @avantguardllc/n8n-openapi-node package and an OpenAPI specification (openapi.json) bundled with the node to build request properties and handle communication.

Troubleshooting

  • Missing or invalid Tenantfilter: Since the tenantfilter property is required, omitting it or providing an incorrect value may result in errors or empty responses. Ensure the tenantfilter string is correctly set.
  • Authentication errors: If the API key credential is missing or invalid, the node will fail to authenticate with the external service. Verify that the API key is correctly configured in n8n credentials.
  • API connectivity issues: Network problems or incorrect base URL configuration can cause request failures. Confirm that the resource API URL in credentials is accurate and accessible.
  • Unexpected API responses: Changes in the external API or malformed responses might cause parsing errors. Check the API documentation and update the node if necessary.

Links and References

Discussion