AvantGuard - CIPP icon

AvantGuard - CIPP

AvantGuard - CIPP

Actions136

Overview

This node interacts with the AvantGuard CIPP API to retrieve quarantine management information related to email senders. Specifically, for the "List" resource and the "Retrieve Exec Quarantine Management" operation, it fetches data about allowed senders filtered by tenant and type criteria. This is useful in scenarios where you need to programmatically manage or audit email quarantine settings, such as verifying which senders are permitted or reviewing quarantine policies for specific tenants.

Practical examples include:

  • Automating the retrieval of quarantine management details for compliance reporting.
  • Integrating quarantine status checks into broader email security workflows.
  • Filtering quarantine data by sender, tenant, or type to tailor notifications or actions.

Properties

Name Meaning
Allowsender The email sender address or identifier that is allowed; used as a query filter parameter.
Id Identifier for the specific quarantine management record or context to retrieve.
Tenantfilter Filter specifying the tenant scope to narrow down the quarantine management data.
Type Type of quarantine or category to filter the results accordingly.

Output

The node outputs JSON data representing the retrieved quarantine management information from the AvantGuard CIPP API. The structure corresponds to the API response for the given filters (allowsender, id, tenantfilter, type). It typically includes details about allowed senders, quarantine statuses, and related metadata.

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 the node credentials.
  • Depends on the @avantguardllc/n8n-openapi-node package and the bundled OpenAPI specification (openapi.json) for request building and execution.

Troubleshooting

  • Missing or invalid API credentials: Ensure the API key and base URL are correctly set in the node credentials.
  • Incorrect property values: All four properties (allowsender, id, tenantfilter, type) are required. Missing or empty values may cause the API call to fail or return no data.
  • Network or API errors: Check network connectivity and API availability. Review error messages returned by the API for guidance.
  • Unexpected response format: If the API changes, the node might not parse responses correctly. Verify compatibility with the current API version.

Links and References

Discussion