Summa icon

Summa

Consume Summa API (v.0.1.7)
Join our community

Actions182

Overview

This node integrates with the Summa API to perform telecom-related operations. Specifically, for the MSISDN resource and the Link MSISDN To IMSI operation, it links a mobile subscriber's phone number (MSISDN) to their unique subscriber identity (IMSI). This is useful in scenarios such as subscriber management, SIM provisioning, or telecom service activation where associating a phone number with its subscriber identity is required.

Practical examples:

  • Telecom operators linking a new phone number to an existing subscriber profile.
  • Systems updating subscriber information after SIM swaps or number porting.
  • Automating subscriber provisioning workflows by programmatically linking MSISDNs to IMSIs.

Properties

Name Meaning
Msisdn The phone number (MSISDN) to be linked to an IMSI.
Default Msisdn Boolean flag indicating if this MSISDN should be set as the default number for the subscriber.
Imsi The International Mobile Subscriber Identity to which the MSISDN will be linked.
Hlr Template Template identifier for Home Location Register configuration related to this MSISDN-IMSI link.
Lte Template Template identifier for LTE network settings associated with this MSISDN-IMSI link.
Ims Template Template identifier for IMS (IP Multimedia Subsystem) settings related to this MSISDN-IMSI link.

Output

The node outputs JSON data representing the result of the linking operation. This typically includes confirmation details such as success status, any updated subscriber records, or error messages if the operation failed.

If binary data were involved (e.g., files or certificates), it would be summarized here, but this operation deals only with JSON responses from the API.

Dependencies

  • Requires connection to the Summa API via an API key credential configured in n8n.
  • The node uses an HTTP client internally to communicate with the Summa backend services.
  • Proper templates (HLR, LTE, IMS) must exist and be referenced correctly for the operation to succeed.

Troubleshooting

  • Common issues:
    • Invalid or missing API credentials causing authentication failures.
    • Incorrect MSISDN or IMSI values leading to API errors.
    • Nonexistent or misconfigured templates resulting in template validation errors.
  • Error messages:
    • Authentication errors: Verify that the API key credential is valid and has necessary permissions.
    • Validation errors on input fields: Check that MSISDN and IMSI formats are correct and templates exist.
    • Network or timeout errors: Ensure connectivity to the Summa API endpoint and retry.

Links and References

Discussion