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 resource SS Subscription SOAP and operation Get Msisdn By Msisdn, the node retrieves information about a mobile subscriber identified by their MSISDN (Mobile Station International Subscriber Directory Number).
Typical use cases include:
- Querying subscriber details in telecom systems by providing an MSISDN.
- Integrating telecom backend services into workflows that require subscriber verification or data retrieval.
- Automating subscriber data lookups within larger automation pipelines.
For example, a user might input an MSISDN to fetch associated subscription details or validate the number's status via the Summa API.
Properties
| Name | Meaning |
|---|---|
| Msisdn | The mobile subscriber number (MSISDN) to query. This is a required string input. |
Output
The node outputs JSON data containing the response from the Summa API corresponding to the queried MSISDN. The structure of this JSON depends on the API response but generally includes subscriber details linked to the provided MSISDN.
If the API returns binary data (not explicitly shown in the code), it would typically represent raw data such as documents or files related to the subscriber, but this node primarily handles JSON responses.
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 Summa API service being available and reachable.
- The user must configure the node with valid credentials for the Summa API.
Troubleshooting
- Authentication errors: If the API key or credentials are invalid or missing, the node will fail to authenticate. Ensure the correct API key is configured.
- Invalid MSISDN input: Since the MSISDN property is required, leaving it empty or providing an incorrectly formatted number may cause the API call to fail or return no results.
- API connectivity issues: Network problems or incorrect endpoint configurations can lead to request failures.
- Unexpected API responses: Changes in the Summa API response format could cause parsing issues; verify API version compatibility.
Links and References
- Summa API Documentation (replace with actual URL if available)
- n8n documentation on Creating Custom Nodes
- General info on MSISDN: https://en.wikipedia.org/wiki/MSISDN
