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 dynamically). It supports multiple resources and operations related to telecommunications data management. Specifically, for the HLR Subscription resource and the Get MSRN Profile operation, the node retrieves the Mobile Station Roaming Number (MSRN) profile associated with a given IMSI (International Mobile Subscriber Identity).

Common scenarios where this node is beneficial include:

  • Telecom operators or service providers needing to query roaming information for subscribers.
  • Systems that require real-time retrieval of subscriber routing numbers for call forwarding or billing purposes.
  • Integration workflows that automate subscriber data validation or enrichment based on roaming profiles.

Practical example:

  • A workflow that receives an IMSI as input and uses this node to fetch the corresponding MSRN profile to determine the current roaming status or location of a mobile subscriber.

Properties

Name Meaning
Imsi The International Mobile Subscriber Identity (IMSI) string used to identify the subscriber whose MSRN profile is being requested. This property is required.

Output

The node outputs JSON data containing the MSRN profile information retrieved from the Summa API for the specified IMSI. The exact structure depends on the API response but typically includes details about the subscriber's roaming number and related metadata.

If the node supports binary data output, it would represent any associated binary content returned by the API; however, based on the provided code and context, the primary output is JSON-formatted subscriber profile data.

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.
  • No additional external services beyond the Summa API are indicated.

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, invalid, or expired, the node will fail to authenticate with the Summa API.
  • API connectivity issues: Network problems or incorrect endpoint configurations can cause request failures.
  • Unexpected API responses: Changes in the Summa API or unexpected data formats might lead to parsing errors.

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 changes affecting response formats.

Links and References

Discussion