AvantGuard - CIPP icon

AvantGuard - CIPP

AvantGuard - CIPP

Actions136

Overview

This node interacts with the AvantGuard CIPP API to retrieve calendar permission information for a specific list resource. Specifically, the "Retrieve List Calendar Permission" operation fetches permissions related to a user's calendar within a tenant's context. This is useful in scenarios where you need to audit or manage calendar access rights programmatically, such as verifying user permissions before performing calendar operations or integrating calendar permission checks into automated workflows.

Practical examples include:

  • Automatically checking if a user has the necessary calendar permissions before sending meeting invites.
  • Auditing calendar access across multiple tenants and users.
  • Integrating calendar permission data into reporting dashboards.

Properties

Name Meaning
Tenantfilter A string value used to filter or specify the tenant context for which to retrieve data.
Userid The identifier of the user whose calendar permissions are being retrieved.

Output

The node outputs JSON data representing the calendar permissions associated with the specified user and tenant. The exact structure depends on the API response but typically includes details about permission levels, roles, and possibly metadata about the calendar or list.

No binary data output is indicated by the source code.

Dependencies

  • Requires an API key credential for authenticating with the AvantGuard CIPP API.
  • The base URL for the API is configured via credentials (resourceApiUrl).
  • The node uses the @avantguardllc/n8n-openapi-node package and an OpenAPI specification (openapi.json) bundled internally to define its properties and requests.

Troubleshooting

  • Missing or invalid API credentials: Ensure that the API key credential is correctly set up and valid.
  • Incorrect tenant or user ID: Verify that the tenantfilter and userid values correspond to existing entities in the AvantGuard system.
  • Network issues or incorrect base URL: Confirm that the resourceApiUrl credential points to the correct API endpoint and that there is network connectivity.
  • Unexpected API responses: Check the API documentation or logs for changes in the API schema or permission models.

Links and References

Discussion