SummaInstall

Overview

This node interacts with the Summa API to manage telecommunication services. Specifically, for the "SS Subscription" resource and the "Remove All Supplementary Service By MSISDN" operation, it removes all supplementary services associated with a given MSISDN (mobile subscriber number). This is useful in scenarios where an operator or system administrator needs to clear all additional telephony services (like call forwarding, barring, etc.) linked to a subscriber's phone number.

Practical examples include:

• Resetting a subscriber’s supplementary services before provisioning new ones.
• Troubleshooting by clearing potentially conflicting supplementary service settings.
• Automating bulk removal of supplementary services during subscriber deactivation or migration.

Properties

Output

The node outputs JSON data representing the result of the removal operation. This typically includes status information such as success confirmation, error messages if any, and possibly details about which services were removed.

If the node supports binary data output, it would relate to raw API responses or logs, but based on the code and context, the primary output is structured JSON reflecting the operation outcome.

Dependencies

• Requires connection to the Summa API via an API key credential configured in n8n.
• Uses internal helper classes for HTTP requests, state management, and operation resolution.
• The node depends on the summaApi credential to authenticate requests.
• No other external dependencies are indicated.

Troubleshooting

• Common issues:

  • Invalid or missing MSISDN input can cause the API to reject the request.
  • Incorrect supplementary service type may lead to no action or errors.
  • Authentication failures due to invalid or expired API credentials.
  • Network connectivity problems preventing access to the Summa API.

• Error messages:

  • Authentication errors suggest checking the API key credential configuration.
  • Validation errors indicate missing or malformed input properties; ensure MSISDN and supplementary service type are correctly set.
  • API response errors should be reviewed in the node’s output for specific failure reasons.

Links and References

• Summa API official documentation (not provided here, but recommended to consult for detailed supplementary service types and API usage).
• n8n documentation on creating and configuring API credentials.
• General telecom supplementary services concepts for understanding service types.