AvantGuard - CIPP icon

AvantGuard - CIPP

AvantGuard - CIPP

Actions136

Overview

This node interacts with the AvantGuard CIPP API to retrieve recipients of a specific list. It is designed to fetch data about who is included in a mailing or contact list, filtered by a tenant identifier. This functionality is useful in scenarios where you need to manage or analyze list membership within a multi-tenant environment, such as marketing campaigns, notifications, or user segmentation.

For example, you might use this node to:

  • Retrieve all recipients associated with a particular tenant's mailing list.
  • Integrate list recipient data into workflows for sending targeted emails or messages.
  • Audit or report on list memberships filtered by tenant.

Properties

Name Meaning
Tenantfilter A required string used to filter the list recipients by tenant. This value is sent as a query parameter named tenantfilter.

Output

The node outputs JSON data representing the list recipients retrieved from the API. The exact structure depends on the API response but typically includes details about each recipient such as identifiers, contact information, and possibly metadata related to their subscription status or tenant association.

If the API supports binary data (e.g., attachments or files), it would be included accordingly, but based on the provided code and properties, the primary output is JSON data about list recipients.

Dependencies

  • Requires an API key credential for authenticating with the AvantGuard CIPP API.
  • Needs the base URL of the resource API configured in the node credentials.
  • Depends on the external @avantguardllc/n8n-openapi-node package for building request properties and handling API interactions.
  • Uses an OpenAPI specification (openapi.json) bundled with the node to define available operations and parameters.

Troubleshooting

  • Missing or invalid tenantfilter: Since tenantfilter is required, omitting it or providing an incorrect value will likely cause the API call to fail or return no results. Ensure the tenantfilter string is correct and corresponds to an existing tenant.
  • Authentication errors: If the API key or credentials are not set up properly, the node will fail to authenticate. Verify that the API key credential is correctly configured.
  • API endpoint issues: The base URL must be correctly set in the credentials. Incorrect URLs or network issues can cause connection failures.
  • Unexpected API responses: If the API changes or returns unexpected data, the node may not parse the output correctly. Check the API documentation and update the node if necessary.

Links and References

Discussion