CIPP icon

CIPP

Work with the CIPP API

Overview

This node interacts with the CIPP API to retrieve license information for a specified tenant. It is useful in scenarios where you need to programmatically access licensing details of tenants managed within the CIPP system, such as auditing licenses, monitoring usage, or integrating license data into other workflows.

For example, you might use this node to:

  • Automatically fetch and report on the licenses assigned to a tenant.
  • Trigger alerts if certain license thresholds are exceeded.
  • Integrate tenant license data into a broader IT asset management system.

Properties

Name Meaning
Tenant Name or ID Select a tenant from a list or specify its ID using an expression. This identifies which tenant's licenses to retrieve.

Output

The node outputs JSON data containing the licenses associated with the specified tenant. The structure typically includes details about each license, such as license type, status, expiration, and any relevant metadata provided by the CIPP API.

If the node supports binary data output (not indicated here), it would represent license-related files or documents; however, based on the code and properties, the output is primarily JSON-formatted license information.

Dependencies

  • Requires an API key credential for authenticating with the CIPP API.
  • The base URL for the API is configured via credentials and used as the request base URL.
  • The node depends on the CIPP API being accessible and properly configured with the necessary permissions to read tenant license data.

Troubleshooting

  • Common Issues:

    • Invalid or missing tenant ID/name can cause the API call to fail or return no data.
    • Authentication errors if the API key credential is incorrect or expired.
    • Network connectivity issues preventing access to the CIPP API endpoint.
  • Error Messages:

    • "Unauthorized" or "Authentication failed": Check that the API key credential is valid and has not expired.
    • "Tenant not found": Verify that the tenant ID or name is correct and exists in the CIPP system.
    • "Network error": Ensure that the n8n instance has network access to the CIPP API URL.

Links and References

Discussion