Actions182
- LTE Subscription Actions
- Get Access Restriction Data For LTE
- Get Apn Info
- Get Lte Profile
- Set Lte Tele Service
- Get Lte Regional Subscription
- Get Scef Permissions
- Set APN Assignations To LTE Subscription
- Get EDRX Cycle Lengths
- Add Apn
- Get V2X Subscription Data
- Set Scef Permissions
- Set EDRX Cycle Lengths
- Set Access Restriction Data For LTE
- Set APNs To LTE Subscription
- Set APN Address Assignations To LTE Subscription
- Add LTE Subscription
- Set SCS Permissions
- Get SCS Permissions
- Get LTE ODB
- Add Custom LTE ODB
- Set LTE ODB Profile
- Get APN Assignations From LTE Subscription
- Remove APN Address Assignation From LTE Subscription
- Sim Swap Actions
- WLAN Subscription Actions
- HLR Subscription Actions
- Set HLR Profile
- Set PDP Address Assignation
- Set HLR Regional Subscription
- Remove PDP
- Remove GMLC Number
- Get HLR Teleservice
- Set MSRN Profile
- Remove PDP Assignations
- Set GMLC Numbers
- Get USSD Profile
- Set Camel Configuration
- Add Custom HLR ODB
- Add Camel Service
- Add GMLC Number
- Get GMLC Numbers
- Remove Camel Service
- Remove HLR Regional Subscription
- Set CSE Notification Profile
- Remove MSRN Profile
- Get ODB
- get HLR Profile
- Add PDP
- Get Camel Info
- Set HLR Teleservice
- Set SS Options
- Sim Swap Direct Without Remove
- Get Camel Configuration
- Clear All GMLC Number
- Set PDPs
- Apply Custom HLR ODB Settings
- Get Bearer Service
- Get Access Restriction Data Profile
- Get HLR Regional Subscription
- Remove PDP Address Assignation
- Add USSD Profile
- Set PDP Assignations
- Remove USSD Profile
- Set Access Restriction Data Profile
- Apply Subscription Settings
- Get PDP Info
- Get PDP Assignations
- Set HLR ODB Profile
- Remove CSE Notification Profile
- Get CSE Notification Profile
- Get HLR ODB
- Get MSRN Profile
- SS Subscription Actions
- Add Supplementary Service By Msisdn
- Add Call Forwarding Custom Supplementary Service
- Get All Supplementary Services By MSISDN
- Remove All Supplementary Service
- Remove All Supplementary Service By MSISDN
- Get Call Forward Information
- Get All Supplementary Services
- Remove Supplementary Service
- Add Supplementary Service
- Add Call Forwarding Custom Supplementary Service By MSISDN
- Get Call Forward Information By MSISDN
- Remove Supplementary Service By MSISDN
- SS Subscription SOAP Actions
- Get Imsi By Imsi
- Get Msisdn By Msisdn
- Create Basic Supplementary Service For SS Subscription
- Create Call Forward Supplementary Service For SS Subscription
- Create Calling Name Presentation For SS Subscription
- Create Call Line Identification Presentation For SS Subscription
- Create Call Line Identification Restriction For SS Subscription
- MSISDN Actions
- Subscriber Actions
- IMS Subscription Actions
- Send Cancel Location To Current VLR Of IMSI
- Add Transparent Data To IMPU
- Remove Transparent Data From IMPU
- Get IMS Volatile Data
- Add Service Profile To IMPU
- Add Public User Identity
- Add Private User Identity
- Remove Service Profile From IMPU
- Set GBA User Sec Settings Template To IMS Subscription
- Remove Public User Identity
- Get GBA User Sec Settings Template
- Get GBA User Sec Settings
- Delete IMS Subscription For IMSI
- IMSI Actions
- CRUD Operator Actions
- Operator Actions
- Sim Actions
- Send Protocol Actions
- Send Cancel Location MME
- Send RTR For IMPI
- Send Cancel Location To Current SGSN Of Imsi
- Send Cancel Location To Current VLR Of IMSI
- Send Cancel Location VLR
- Send Cancel Location SGSN
- Send Diameter Cancel Location SGSN
- Send Cancel Location To Current SGSN
- Send Cancel Location To All Currents Of IMSI
- Send Cancel Location To Current MME Of IMSI
- Send RTR For IMPU
- Send Cancel Location To Current VLR
- Send Cancel Location To Current MME
- CRUD PLMN Actions
- Templates Actions
Overview
This node, named "Summa," is designed to interact with the Summa API (version indicated dynamically). It supports multiple resources and operations related to telecommunications data management. Specifically, for the HLR Subscription resource and the Get MSRN Profile operation, the node retrieves the Mobile Station Roaming Number (MSRN) profile associated with a given IMSI (International Mobile Subscriber Identity).
Common scenarios where this node is beneficial include:
- Telecom operators or service providers needing to query roaming information for subscribers.
- Systems that require real-time retrieval of subscriber routing numbers for call forwarding or billing purposes.
- Integration workflows that automate subscriber data validation or enrichment based on roaming profiles.
Practical example:
- A workflow that receives an IMSI as input and uses this node to fetch the corresponding MSRN profile to determine the current roaming status or location of a mobile subscriber.
Properties
| Name | Meaning |
|---|---|
| Imsi | The International Mobile Subscriber Identity (IMSI) string used to identify the subscriber whose MSRN profile is being requested. This property is required. |
Output
The node outputs JSON data containing the MSRN profile information retrieved from the Summa API for the specified IMSI. The exact structure depends on the API response but typically includes details about the subscriber's roaming number and related metadata.
If the node supports binary data output, it would represent any associated binary content returned by the API; however, based on the provided code and context, the primary output is JSON-formatted subscriber profile data.
Dependencies
- Requires an active connection to the Summa API, authenticated via an API key credential configured in n8n.
- Uses internal helper classes for HTTP requests, state management, and operation resolution.
- No additional external services beyond the Summa API are indicated.
Troubleshooting
- Missing or invalid IMSI: Since IMSI is required, ensure it is provided and correctly formatted. Errors may occur if IMSI is empty or malformed.
- Authentication errors: If the API key credential is missing, invalid, or expired, the node will fail to authenticate with the Summa API.
- API connectivity issues: Network problems or incorrect endpoint configurations can cause request failures.
- Unexpected API responses: Changes in the Summa API or unexpected data formats might lead to parsing errors.
To resolve these issues:
- Verify the IMSI input value.
- Check and update the API authentication credentials.
- Ensure network connectivity and correct API endpoint configuration.
- Review API documentation for any changes affecting response formats.
Links and References
- Summa API Documentation (Replace with actual URL if available)
- n8n Documentation: Creating Custom Nodes
- Telecommunications standards for IMSI and MSRN concepts (e.g., 3GPP specifications)
