Summa icon

Summa

Consume Summa API (v.0.1.7)
Join our community

Actions182

Overview

This node, named "Summa," is designed to interact with the Summa API (version indicated in the code). It supports multiple resources and operations related to telecommunications data management. Specifically, for the resource Send Protocol and operation Send Cancel Location SGSN, the node sends a cancellation request to a Serving GPRS Support Node (SGSN) based on provided subscriber information.

Typical use cases include:

  • Telecom operators needing to cancel or update subscriber location information in their network.
  • Automating network management tasks such as deregistering a subscriber from a specific SGSN.
  • Integrating with backend systems that manage mobile subscriber sessions and locations.

Example scenario: A telecom operator wants to cancel the location of a subscriber identified by IMSI on a particular SGSN node due to service changes or subscriber deactivation.

Properties

Name Meaning
Imsi The International Mobile Subscriber Identity (IMSI) identifying the subscriber.
Serving Node The identifier of the SGSN node where the subscriber is currently registered.
Cancellation Type The type of cancellation to perform; this could be different modes or reasons for cancel.

Output

The node outputs JSON data representing the response from the Summa API after attempting to send the cancel location request. This typically includes status information about the success or failure of the cancellation operation.

If the node supports binary data output, it would represent any raw data returned by the API, but based on the provided code and context, the primary output is structured JSON.

Dependencies

  • Requires an API key credential for authenticating with the Summa API.
  • Uses an HTTP client internally to communicate with the Summa backend services.
  • The node depends on the summaApi credential configured in n8n for authentication.
  • No other external dependencies are explicitly required.

Troubleshooting

  • Common issues:

    • Missing or invalid API credentials will cause authentication failures.
    • Incorrect IMSI or Serving Node values may result in errors or no action taken.
    • Network connectivity problems can prevent successful API calls.

  • Error messages:

    • Authentication errors typically indicate invalid or missing API keys; verify credentials.
    • Validation errors may occur if required properties like IMSI or Serving Node are empty or malformed.
    • API response errors should be checked for detailed messages from the Summa backend.

Resolving these usually involves verifying input parameters, ensuring valid credentials, and checking network access.

Links and References

Discussion