AvantGuard - CIPP icon

AvantGuard - CIPP

AvantGuard - CIPP

Actions136

Overview

This node integrates with the AvantGuard CIPP API to perform operations related to device management within lists. Specifically, the "Retrieve Exec Device Delete" operation under the "List" resource allows users to execute a delete action on a device identified by its ID, filtered by tenant information. This is useful in scenarios where automated workflows need to manage or clean up devices from lists based on dynamic criteria.

Practical examples include:

  • Automatically removing a device from a list when it is decommissioned.
  • Executing device deletion commands as part of a larger network management automation.
  • Filtering device deletions by tenant to ensure multi-tenant environments are handled correctly.

Properties

Name Meaning
Action The action to perform; for this operation, it should be set to trigger the delete logic.
Id The unique identifier of the device to be deleted.
Tenantfilter A filter string specifying which tenant's context to apply when deleting the device.

Output

The node outputs JSON data representing the response from the AvantGuard CIPP API after executing the delete action on the specified device. The structure typically includes status information about the deletion request, such as success confirmation or error details.

No binary data output is indicated.

Dependencies

  • Requires an API key credential for authenticating with the AvantGuard CIPP API.
  • Needs the base URL of the AvantGuard resource API configured in credentials.
  • Depends on the @avantguardllc/n8n-openapi-node package and the included OpenAPI specification (openapi.json) for request construction.

Troubleshooting

  • Common issues:

    • Invalid or missing device ID may cause the API to reject the request.
    • Incorrect tenant filter values can lead to authorization errors or no matching device found.
    • Network connectivity problems or incorrect API base URL configuration will prevent successful requests.
  • Error messages:

    • Authentication failures usually indicate invalid or expired API credentials.
    • "Device not found" errors suggest the provided ID does not exist under the given tenant filter.
    • Validation errors may occur if required properties (Action, Id, Tenantfilter) are missing or malformed.

To resolve these, verify that all required input properties are correctly set, confirm API credentials and endpoint URLs, and ensure the device ID and tenant filter correspond to existing resources.

Links and References

Discussion