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). Specifically, for the LTE Subscription resource and the Get Lte Profile operation, it retrieves LTE profile information based on a provided IMSI (International Mobile Subscriber Identity). This functionality is useful in telecommunications scenarios where you need to fetch subscriber LTE profile details programmatically, such as for network management, subscriber analytics, or integration with other telecom systems.
Practical examples include:
- Querying an LTE subscriber's profile to verify subscription status.
- Integrating LTE profile data into customer support dashboards.
- Automating subscriber data synchronization between systems.
Properties
| Name | Meaning |
|---|---|
| Imsi | The International Mobile Subscriber Identity (IMSI) string identifying the LTE subscriber whose profile is to be retrieved. This is a required input. |
Output
The node outputs JSON data representing the LTE profile associated with the given IMSI. The exact structure depends on the Summa API response but typically includes subscriber details relevant to LTE service profiles.
If the node supports binary data output, it would represent any binary content returned by the API; however, based on the static code and context, this node primarily outputs JSON data.
Dependencies
- Requires an API key credential for authenticating with the Summa API.
- Depends on the
@digital-boss/n8n-designpatternspackage for resource-operation resolution and execution patterns. - Uses internal backend modules (
HttpClient,State, and operation methods) to handle HTTP requests and state management. - The node expects the Summa API endpoint to be accessible and properly configured via credentials.
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.
- Network issues: Connectivity problems to the Summa API endpoint can cause request failures.
- API response errors: If the IMSI does not correspond to a valid LTE profile, the API might return an error or empty result.
To resolve these:
- Verify the IMSI input value.
- Check and update the API authentication credentials.
- Ensure network connectivity and API availability.
- Review API documentation for correct usage and error codes.
Links and References
- Summa API official documentation (refer to your organization's API docs).
- n8n documentation on creating and using custom nodes: https://docs.n8n.io/integrations/creating-nodes/
- General info on IMSI and LTE profiles: https://en.wikipedia.org/wiki/International_mobile_subscriber_identity
