CIPP icon

CIPP

Interact with CIPP API

Actions18

Overview

The node interacts with the CIPP API to manage calendar permissions, specifically allowing editing of calendar permissions for users within a tenant. This is useful in scenarios where an organization needs to programmatically update or remove access rights to calendars for different users, such as automating permission changes when employees join or leave teams.

For example, you can use this node to:

  • Grant a user "Editor" permissions on a shared calendar.
  • Remove a user's access to a calendar.
  • Notify users when their calendar permissions have been updated.

Properties

Name Meaning
User ID The email address or ID of the user whose calendar permissions are being managed.
Tenant Filter The tenant ID or domain name (e.g., "n8layer.com") that filters the scope of the calendar permissions.
Permissions The level of calendar access to assign. Options include: Author, AvailabilityOnly, Contributor, Editor, LimitedDetails, Non Editing Author, Owner, Publishing Author, Publishing Editor, Reviewer.
User to Get Permissions The email address or ID of the user whose calendar permissions you want to retrieve or modify.
Folder Name The name of the calendar folder, defaulting to "Calendar".
Remove Access Boolean flag indicating whether to remove the user's access instead of updating it.
Send Notification to User Boolean flag indicating whether to send a notification to the user about the permission change.

Output

The node outputs JSON data representing the result of the calendar permission update operation. This typically includes confirmation of the updated permissions or removal status for the specified user on the given calendar folder. If the operation involves retrieving permissions, the output will contain the current permission details for the user.

No binary data output is involved.

Dependencies

  • Requires an API key credential for authenticating with the CIPP API.
  • The node expects the base URL for the CIPP API to be configured via credentials.
  • Proper tenant and user identifiers must be provided to interact with the API successfully.

Troubleshooting

  • Common Issues:

    • Invalid or missing user IDs or tenant filters may cause the API call to fail.
    • Insufficient permissions of the authenticated API user to modify calendar permissions.
    • Incorrect folder names might lead to failure in locating the calendar to update.

  • Error Messages:

    • Authentication errors indicate issues with the API key or OAuth token; verify credentials.
    • Permission denied errors suggest the authenticated user lacks rights to edit the target calendar.
    • Not found errors may mean the specified user or calendar folder does not exist; double-check inputs.

Resolving these usually involves verifying input parameters, ensuring correct API credentials, and confirming the authenticated user has adequate privileges.

Links and References

Discussion