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
The node named "Summa" is designed to interact with the Summa API, specifically versioned as indicated in its description. It supports multiple resources and operations related to telecommunications data management, including HLR (Home Location Register) subscriptions.
For the HLR Subscription resource and the Get HLR Regional Subscription operation, this node retrieves regional subscription information based on an IMSI (International Mobile Subscriber Identity) value provided by the user. This can be useful in scenarios where a user or system needs to query detailed subscriber location or status information from the HLR database for telecom services.
Practical examples include:
- Telecom operators verifying subscriber regional data for routing or billing.
- Systems performing fraud detection or subscriber validation.
- Customer support tools fetching subscriber details to assist users.
Properties
| Name | Meaning |
|---|---|
| Imsi | The International Mobile Subscriber Identity string used to identify the subscriber whose HLR regional subscription data is being requested. This property is required for the operation. |
Output
The node outputs JSON data containing the response from the Summa API regarding the HLR regional subscription associated with the provided IMSI. The exact structure depends on the API response but typically includes subscriber regional details such as location, subscription status, and other relevant metadata.
No binary data output is indicated in the source code or properties.
Dependencies
- Requires an API key credential for authenticating with the Summa API.
- Uses an HTTP client internally to send requests to the Summa backend service.
- The node depends on the
@digital-boss/n8n-designpatternspackage for resource-operation resolution and execution patterns. - Proper configuration of the Summa API credentials within n8n is necessary for successful operation.
Troubleshooting
- Missing or invalid IMSI: Since IMSI is required, omitting it or providing an invalid format will likely cause errors or empty responses.
- Authentication errors: If the API key credential is missing, expired, or incorrect, the node will fail to authenticate with the Summa API.
- Network issues: Connectivity problems between n8n and the Summa API endpoint may result in timeouts or request failures.
- API changes: Changes in the Summa API version or endpoints might cause unexpected errors; ensure the node and credentials are up to date.
Common error messages would relate to authentication failure, invalid parameters, or network timeouts. Resolving these involves verifying credentials, input correctness, and network connectivity.
Links and References
- Summa API Documentation (hypothetical link, replace with actual if available)
- n8n documentation on Creating Custom Nodes
- IMSI explanation: Wikipedia - IMSI