Summa icon

Summa

Consume Summa API (v.0.1.7)
Join our community

Actions182

Overview

This node, named "Summa," is designed to interact with the Summa API (version indicated in the code). Specifically, for the LTE Subscription resource and the Get SCS Permissions operation, it retrieves permissions related to the Subscriber's Scalable Charging System (SCS) based on the provided IMSI (International Mobile Subscriber Identity).

Common scenarios where this node would be beneficial include:

  • Telecom operators or service providers needing to verify or audit subscriber permissions within their LTE network.
  • Automated workflows that require fetching subscriber permission details before performing further actions like billing, provisioning, or compliance checks.

Practical example:

  • A workflow that triggers when a new subscriber is added, using this node to fetch their SCS permissions to determine what services or features they are allowed to access.

Properties

Name Meaning
Imsi The International Mobile Subscriber Identity (IMSI) of the LTE subscription. This string uniquely identifies the subscriber whose SCS permissions are being requested. It is a required field.

Output

The node outputs JSON data containing the SCS permissions associated with the specified IMSI. The exact structure depends on the Summa API response but generally includes permission details relevant to the subscriber's LTE subscription.

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

Dependencies

  • Requires an active connection to the Summa API via an API key credential (referred generically as "an API key credential").
  • The node uses an HTTP client internally to communicate with the Summa backend.
  • Proper configuration of the Summa API credentials in n8n is necessary.
  • The node depends on several internal modules and design patterns from the @digital-boss/n8n-designpatterns package and custom backend implementations (HttpClient, State, operations), which handle request execution, state management, and operation resolution.

Troubleshooting

  • Missing or invalid IMSI: Since IMSI is required, ensure it is provided and correctly formatted. Invalid IMSI values may cause the API to return errors or empty results.
  • Authentication errors: If the API key credential is missing, expired, or incorrect, the node will fail to authenticate with the Summa API. Verify the credential setup in n8n.
  • API connectivity issues: Network problems or incorrect endpoint configurations can lead to request failures. Check network access and API availability.
  • Unexpected API responses: If the Summa API changes or returns unexpected data structures, the node might not parse the output correctly. Review API documentation and update the node if needed.

Links and References

Discussion