Summa icon

Summa

Consume Summa API (v.0.1.7)

Actions182

Overview

This node integrates with the Summa API to perform operations related to telecommunications data. Specifically, for the "IMSI" resource and the "Find IMSIs Of Subscriber" operation, it retrieves the list of IMSI (International Mobile Subscriber Identity) numbers associated with a given subscriber. This is useful in scenarios where you need to identify all IMSIs linked to a particular subscriber ID within a telecom operator's system.

Practical examples include:

  • Telecom operators managing subscriber profiles and needing to audit or verify all IMSIs assigned to a subscriber.
  • Fraud detection systems checking multiple IMSIs under one subscriber to detect anomalies.
  • Customer support tools fetching IMSI details to troubleshoot connectivity or subscription issues.

Properties

Name Meaning
Subscriber Id The unique identifier of the subscriber whose IMSIs are to be retrieved.
Operator Name The name of the telecom operator managing the subscriber and their IMSIs.

Both properties are required inputs for this operation.

Output

The node outputs JSON data containing the IMSIs associated with the specified subscriber. The structure typically includes an array or list of IMSI identifiers, possibly along with metadata such as status or assignment details depending on the API response.

If the node supports binary data output, it would represent any non-JSON data returned by the API, but based on the provided code and context, the output is primarily JSON-formatted IMSI information.

Dependencies

  • Requires 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 operation resolution.
  • No additional external dependencies beyond the Summa API and its authentication.

Troubleshooting

  • Common Issues:

    • Invalid or missing subscriber ID or operator name will cause the API call to fail or return no results.
    • Incorrect or expired API credentials will result in authentication errors.
    • Network connectivity problems can prevent successful communication with the Summa API.
  • Error Messages:

    • Authentication failures usually indicate invalid API keys; recheck and update credentials.
    • "Subscriber not found" or empty results suggest the subscriber ID does not exist or has no IMSIs assigned.
    • Timeout or network errors require verifying internet access and API endpoint availability.

Links and References

Discussion