SummaInstall

Overview

This node integrates with the Summa API to add a new MSISDN (Mobile Station International Subscriber Directory Number) using a predefined Supplementary Services (SS) template. It is designed for telecom operators or service providers who need to programmatically manage subscriber numbers and their associated service templates.

Typical use cases include:

• Automating the provisioning of new mobile numbers with specific service configurations.
• Applying consistent SS templates across multiple MSISDNs to ensure uniform service behavior.
• Integrating with backend systems to streamline subscriber management workflows.

For example, a telecom operator can use this node to add a new MSISDN linked to an IMSI, specifying alert indicators and various service templates (HLR, LTE, IMS, SMS routing, SS), ensuring the number is configured correctly upon creation.

Properties

All properties are required for the operation "Add MSISDN With SS Template" under the resource "MSISDN".

Output

The node outputs JSON data representing the result of the Add MSISDN operation. This typically includes confirmation details such as the created MSISDN record, status messages, or any relevant metadata returned by the Summa API.

If the operation involves binary data (not indicated here), it would represent related files or attachments, but in this case, output is purely JSON-based.

Dependencies

• Requires an active connection to the Summa API via an API key credential.
• The node depends on the summaApi credential for authentication.
• Network access to the Summa API endpoint must be configured and available.
• No additional external services are explicitly required beyond the Summa API.

Troubleshooting

• Authentication errors: Ensure the API key credential is valid and has necessary permissions.
• Missing or invalid parameters: All input properties are required; missing or malformed values will cause errors.
• Network issues: Verify connectivity to the Summa API endpoint.
• Template mismatches: Using incorrect or non-existent templates (HLR, LTE, IMS, SS) may result in API errors; confirm template names are correct.
• Alert indicator misuse: The alert indicator must be a boolean; passing other types may cause validation failures.

Common error messages might include authentication failures, validation errors for missing fields, or API response errors indicating template problems. Resolving these usually involves checking credentials, input correctness, and API documentation for valid template names.

Links and References

• Summa API Documentation (replace with actual URL)
• Telecom standards for MSISDN and IMSI management
• n8n documentation on creating custom nodes and managing credentials