Summa icon

Summa

Consume Summa API (v.0.1.7)

Actions182

Overview

The node named "Summa" integrates with the Summa API (version indicated in the code) to perform various operations on multiple resources. Specifically, for the resource HLR Subscription and operation Set CSE Notification Profile, this node allows users to update or set the CSE (Charging System Entity) notification profile associated with a given IMSI (International Mobile Subscriber Identity). This is useful in telecom environments where managing subscriber profiles and notifications is essential for billing, monitoring, or service management.

Practical examples include:

  • Updating the notification profile of a subscriber identified by their IMSI to change how charging events are reported.
  • Automating telecom subscriber management workflows that require setting or modifying CSE notification profiles programmatically.

Properties

Name Meaning
Imsi The IMSI (International Mobile Subscriber Identity) of the subscriber whose profile is being set. This uniquely identifies the mobile subscriber.
Cse Notification Profile The CSE Notification Profile value to assign to the subscriber. This defines the notification settings related to charging system events.

Output

The node outputs JSON data representing the result of the Set CSE Notification Profile operation. This typically includes confirmation of success or failure, and may contain details about the updated subscriber profile or error messages if the operation failed.

No binary data output is indicated in the source code.

Dependencies

  • Requires an API key credential to authenticate with the Summa API.
  • Uses an HTTP client internally to communicate with the Summa backend services.
  • The node depends on the Summa API version specified in the bundled code.
  • Proper configuration of the API credentials within n8n is necessary for successful execution.

Troubleshooting

  • Common issues:
    • Invalid or missing IMSI value will cause the operation to fail.
    • Incorrect or unauthorized API credentials will prevent communication with the Summa API.
    • Network connectivity problems can lead to request timeouts or failures.
  • Error messages:
    • Authentication errors indicate invalid API keys or insufficient permissions; verify and update credentials.
    • Validation errors on input properties suggest missing or malformed IMSI or notification profile values; ensure required fields are correctly filled.
    • API response errors should be checked against Summa API documentation for specific error codes and remedies.

Links and References

  • Summa API official documentation (not provided in the code, but recommended to consult for detailed API usage).
  • n8n documentation on creating and using custom nodes and credentials.
  • Telecom standards references for IMSI and CSE notification profiles for deeper understanding of these concepts.

Discussion