Summa icon

Summa

Consume Summa API (v.0.1.7)

Actions182

Overview

This node, named "Summa," is designed to interact with the Summa API (version indicated in the code). Specifically, for the resource LTE Subscription and operation Get Scef Permissions, it retrieves permissions related to the SCEF (Service Capability Exposure Function) for a given LTE subscription identified by an IMSI (International Mobile Subscriber Identity).

Common scenarios where this node would be beneficial include:

  • Telecom operators or service providers needing to verify or audit SCEF permissions assigned to a subscriber.
  • Automated workflows that manage or monitor LTE subscriptions and their associated capabilities.
  • Integration of LTE subscription data into broader OSS/BSS systems or network management tools.

Practical example:

  • A workflow that triggers when a new LTE subscription is created and uses this node to fetch and log the current SCEF permissions for compliance checks.

Properties

Name Meaning
Imsi The International Mobile Subscriber Identity (IMSI) string identifying the LTE subscription for which to retrieve SCEF permissions. This property is required.

Output

The node outputs JSON data representing the SCEF permissions associated with the specified LTE subscription IMSI. The exact structure depends on the Summa API response but typically includes permission details such as allowed services, access rights, or exposure capabilities.

If the node supports binary data output, it is not evident from the provided code snippet; thus, the output is primarily JSON-based.

Dependencies

  • Requires an active connection to the Summa API, authenticated via an API key credential configured in n8n.
  • Uses internal helper classes for HTTP requests, state management, and operation resolution.
  • The node depends on the summaApi credential to authenticate requests to the Summa backend.

Troubleshooting

  • Missing or invalid IMSI: Since IMSI is required, ensure it is provided and correctly formatted. Errors may occur if IMSI is empty or malformed.
  • Authentication errors: If the API key credential is missing, expired, or incorrect, the node will fail to connect to the Summa API.
  • API connectivity issues: Network problems or incorrect endpoint configurations can cause request failures.
  • Unexpected API responses: If the Summa API changes or returns unexpected data, the node might throw errors or produce incomplete output.

To resolve these issues:

  • Verify the IMSI input value.
  • Check and update the API authentication credentials.
  • Ensure network connectivity and correct API endpoint configuration.
  • Review API documentation for any recent changes.

Links and References

Discussion