Summa icon

Summa

Consume Summa API (v.0.1.7)

Actions182

Overview

This node integrates with the Summa API to perform telecom-related operations. Specifically, the Sim Swap Deferred Explicit operation allows users to initiate a SIM swap process where one ICCID (Integrated Circuit Card Identifier) is replaced by another, along with updating associated IMSI (International Mobile Subscriber Identity) mappings. This deferred explicit swap is useful in scenarios where telecom operators need to manage subscriber identity transitions between SIM cards while controlling the timing and details of the swap explicitly.

Practical examples include:

  • Migrating a subscriber from an old SIM card to a new one while preserving service continuity.
  • Managing bulk IMSI updates during SIM replacements in a controlled manner.
  • Telecom operators automating SIM swap workflows with precise control over involved identifiers.

Properties

Name Meaning
From Icc Id The ICCID of the SIM card currently assigned to the subscriber (source SIM).
To Icc Id The ICCID of the SIM card to which the subscriber will be moved (target SIM).
Imsi Swaps A collection of IMSI pairs specifying old IMSIs to be replaced by new IMSIs during the swap. Each entry has:
- Old Imsi: The IMSI currently associated with the subscriber.
- New Imsi: The IMSI to replace the old one.
Operator Name The name of the telecom operator managing the SIM swap operation.

Output

The node outputs JSON data representing the result of the SIM swap operation as returned by the Summa API. This typically includes confirmation of the swap request, status information, and any relevant metadata about the processed IMSI swaps and ICCIDs.

If the operation involves binary data (e.g., certificates or files), it would be included in the binary output field; however, based on the provided code and properties, this node primarily deals with JSON responses.

Dependencies

  • Requires an API key credential for authenticating with the Summa API.
  • Depends on the @digital-boss/n8n-designpatterns package for resource-operation resolution and execution patterns.
  • Uses internal HTTP client and state management modules to handle requests and maintain operation context.
  • The node expects proper configuration of the Summa API credentials within n8n.

Troubleshooting

  • Missing or invalid API credentials: Ensure that the API key credential for the Summa API is correctly configured and tested.
  • Invalid ICCID or IMSI values: Verify that the ICCID and IMSI strings conform to expected formats and exist in the operator's system.
  • Empty or malformed IMSI swaps collection: The imsiSwaps property must contain valid old-new IMSI pairs; otherwise, the API may reject the request.
  • Operator name mismatch: The operator name must match the expected value recognized by the Summa API.
  • Network or API errors: Check connectivity and API endpoint availability; review error messages for HTTP status codes and response bodies for clues.

Links and References

  • Summa API Documentation (Replace with actual URL if available)
  • Telecom standards for ICCID and IMSI formatting
  • n8n documentation on creating custom nodes and using credentials

Discussion