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). Specifically, for the HLR Subscription resource and the Get USSD Profile operation, it retrieves the USSD profile associated with a given IMSI (International Mobile Subscriber Identity). This can be useful in telecom environments where you need to query subscriber information related to USSD services.

Practical examples include:

  • Fetching USSD service profiles for subscribers to customize or troubleshoot their USSD interactions.
  • Integrating subscriber data retrieval into automated workflows for telecom service management.
  • Validating subscriber USSD configurations before provisioning or billing.

Properties

Name Meaning
Imsi The International Mobile Subscriber Identity (IMSI) string identifying the subscriber whose USSD profile is to be retrieved. This property is required.

Output

The node outputs JSON data representing the USSD profile details of the subscriber identified by the provided IMSI. The exact structure depends on the Summa API response but typically includes fields describing the subscriber's USSD service settings and status.

If the node supports binary data output, it would relate to any binary content returned by the API, but 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 via an API key credential configured in n8n.
  • Uses internal helper classes for HTTP requests and state management.
  • Depends on the @digital-boss/n8n-designpatterns package for resource-operation resolution and execution flow.
  • The node expects the user to have valid credentials for the Summa API set up in n8n.

Troubleshooting

  • Missing or invalid IMSI: Since IMSI is required, ensure it is provided and correctly formatted; otherwise, the API call will fail.
  • Authentication errors: If the API key credential is missing, expired, or incorrect, the node will not authenticate successfully. Verify the credential configuration.
  • API connectivity issues: Network problems or incorrect endpoint URLs may cause request failures. Check network access and API availability.
  • Unexpected API responses: If the Summa API changes or returns errors, the node might throw exceptions. Review the API documentation and update the node or credentials accordingly.

Links and References

Discussion