Summa icon

Summa

Consume Summa API (v.0.1.7)

Actions182

Overview

This node integrates with the Summa API to perform various operations related to telecommunications data. Specifically, for the HLR Subscription resource and the Get Access Restriction Data Profile operation, it retrieves access restriction profile information associated with a given IMSI (International Mobile Subscriber Identity). This is useful in scenarios where you need to query subscriber restrictions or profile details from the Home Location Register (HLR) system.

Practical examples include:

  • Validating subscriber access restrictions before provisioning services.
  • Auditing subscriber profiles for compliance or troubleshooting.
  • Integrating telecom subscriber data into broader workflows or dashboards.

Properties

Name Meaning
Imsi The International Mobile Subscriber Identity string used to identify the subscriber whose access restriction data profile is being requested. This property is required.

Output

The node outputs JSON data containing the access restriction data profile corresponding to the provided IMSI. The exact structure depends on the Summa API response but typically includes fields describing subscriber restrictions, allowed services, and profile parameters.

If the node supports binary data output, it would represent any non-JSON payloads returned by the API; however, based on the provided code and context, the output is primarily JSON.

Dependencies

  • Requires an active connection to the Summa API service.
  • Needs an API authentication token or key configured via n8n credentials (referred generically as "an API key credential").
  • Uses internal helper classes for HTTP requests and state management.
  • Depends on external packages from @digital-boss/n8n-designpatterns for operation resolution and execution.

Troubleshooting

  • Missing or invalid IMSI: Since IMSI is required, ensure it is provided and correctly formatted. Errors may occur if this parameter is empty or malformed.
  • Authentication errors: If the API key credential is missing, expired, or incorrect, the node will fail to authenticate with the Summa API.
  • Network issues: Connectivity problems to the Summa API endpoint can cause request failures.
  • Unexpected API responses: Changes in the Summa API or unexpected data formats might lead to parsing errors.

To resolve these:

  • Verify the IMSI input value.
  • Check and update the API authentication credentials.
  • Ensure network connectivity to the Summa API.
  • Review API documentation for any changes in response structure.

Links and References

Discussion