Actions18
- Calendar Permission Actions
- Group Actions
- License Actions
- Tenant Actions
- User Actions
Overview
This node interacts with the CIPP API to manage calendar permissions for users within an organization. Specifically, the "List Calendar Permissions" operation retrieves the permissions set on a user's calendar, which is useful for administrators or automation workflows that need to audit or manage access rights.
Common scenarios include:
- Auditing who has access to a particular user's calendar.
- Automating permission reviews or compliance checks.
- Integrating calendar permission data into reporting dashboards.
For example, an admin could use this node to list all permissions for a user’s calendar in a specific tenant domain to ensure only authorized personnel have access.
Properties
| Name | Meaning |
|---|---|
| User ID | The email address or unique identifier of the user whose calendar permissions are being listed. This is required. |
| Tenant Filter | The tenant ID or domain name (e.g., "n8layer.com") used to filter and specify the organizational context for the query. This is required. |
Output
The node outputs JSON data representing the list of calendar permissions associated with the specified user within the given tenant. Each item in the output typically includes details such as the permission type, the grantee (user or group), and the level of access granted.
If the node supports binary data output, it would generally relate to attachments or exported permission reports, but based on the provided code and properties, the output is purely JSON structured data about calendar permissions.
Dependencies
- Requires an API key credential for authenticating with the CIPP API.
- The base URL for the API is configured dynamically from the credentials.
- The node expects the CIPP API to be accessible and properly configured for the tenant and user specified.
Troubleshooting
- Missing or invalid User ID: Ensure the User ID is correctly provided as an email or valid user identifier; otherwise, the API call will fail.
- Incorrect Tenant Filter: Providing an incorrect tenant ID or domain may result in no data returned or authorization errors.
- Authentication errors: Verify that the API key credential is valid and has sufficient permissions to access calendar permissions.
- API connectivity issues: Network problems or incorrect base URL configuration can cause request failures.
Links and References
- CIPP API Documentation (Replace with actual link if available)
- General n8n documentation on Using Credentials
- Best practices for managing calendar permissions in enterprise environments.