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 in the code). Specifically, for the resource SS Subscription SOAP and operation Get Imsi By Imsi, it retrieves information related to an IMSI (International Mobile Subscriber Identity) by providing an IMSI value as input.
Common scenarios where this node would be beneficial include telecom or mobile network management workflows where subscriber identity details need to be fetched or verified based on IMSI values. For example, a user might want to validate if a given IMSI exists in the system or retrieve associated subscription data.
Properties
| Name | Meaning |
|---|---|
| Imsi | The IMSI string value used to query the Summa API for subscriber information. This is a required input. |
Output
The node outputs JSON data containing the response from the Summa API related to the IMSI queried. The exact structure depends on the API response but typically includes subscriber details linked to the provided IMSI.
If the node supports binary data output, it is not explicitly shown in the provided code snippet; thus, the primary output is JSON-formatted data representing the API response.
Dependencies
- Requires an API key credential for authenticating with the Summa API.
- Uses internal helper classes for HTTP requests (
HttpClient), state management (State), and operation resolution/execution (ResOpResolver,ResOpExecutor). - The node depends on the external package
@digital-boss/n8n-designpatternsfor operation handling patterns. - The node expects the Summa API endpoint and authentication details to be configured via credentials in n8n.
Troubleshooting
- Authentication errors: If the API key or credentials are missing or invalid, the node will fail to authenticate with the Summa API. Ensure that the API key credential is correctly set up and tested.
- Invalid IMSI input: Since the IMSI property is required, providing an empty or malformed IMSI string may cause the API call to fail or return no results.
- API connectivity issues: Network problems or incorrect API endpoint configuration can lead to request failures. Verify network access and credential configurations.
- Unexpected API responses: If the API changes or returns unexpected data structures, the node's output may not match expectations. Check the API documentation and update the node or workflow accordingly.
Links and References
- Summa API Documentation (Replace with actual URL if available)
- n8n Documentation - Creating Nodes
- IMSI Wikipedia