Actions18
- Calendar Permission Actions
- Group Actions
- License Actions
- Tenant Actions
- User Actions
Overview
The node named "CIPP" provides integration with the CIPP API, allowing users to interact with various resources such as Users, Groups, Licenses, Tenants, and Calendar Permissions. Specifically, for the User resource and the List User Counts operation, this node fetches aggregated user count data filtered by a tenant identifier. This is useful in scenarios where an organization needs to monitor or report on the number of users within a specific tenant environment.
Practical examples include:
- Retrieving the total number of users associated with a particular tenant.
- Generating reports on user distribution across tenants.
- Monitoring user counts for administrative or auditing purposes.
Properties
| Name | Meaning |
|---|---|
| Tenant Filter | The tenant filter to use for the user count query. This should be the tenant ID string identifying the tenant whose user counts are to be retrieved. |
Output
The node outputs JSON data containing the user counts corresponding to the specified tenant filter. The exact structure depends on the CIPP API response but generally includes aggregated counts or statistics about users under the given tenant.
No binary data output is indicated or expected from this operation.
Dependencies
- Requires an active connection to the CIPP API.
- Needs an API authentication token configured via OAuth2 credentials (referred generically as an API key credential).
- The base URL for the API is dynamically set from the provided credentials.
- Proper permissions on the CIPP API side to access user count information.
Troubleshooting
Common issues:
- Invalid or missing tenant ID in the "Tenant Filter" property will result in no data or errors.
- Authentication failures due to incorrect or expired API tokens.
- Network connectivity problems preventing access to the CIPP API endpoint.
Error messages and resolutions:
- Unauthorized / 401 errors: Check that the API authentication token is valid and has not expired.
- 404 Not Found: Verify that the tenant ID provided exists and is correct.
- Timeouts or network errors: Ensure stable internet connection and that the API URL is reachable.
- Empty or unexpected responses: Confirm that the tenant has user data and that the API endpoint supports the requested operation.
Links and References
- CIPP API Documentation (Replace with actual URL if available)
- OAuth2 Authentication setup guides for n8n nodes
- General n8n documentation on creating and using custom nodes