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 "Summa" node integrates with the Summa API (version indicated in the code) to perform various operations on different resources related to telecommunications subscriptions and services. Specifically, for the SS Subscription resource with the Add Supplementary Service operation, this node allows users to add a supplementary service to a subscriber's subscription by specifying key identifiers and service details.
This node is beneficial in scenarios where telecom operators or service providers need to programmatically manage subscriber services, such as enabling call forwarding, call barring, or other supplementary telephony features. For example, an operator could automate adding a voicemail service or call waiting feature to a subscriber’s account based on business rules or customer requests.
Properties
| Name | Meaning |
|---|---|
| Imsi | The International Mobile Subscriber Identity (IMSI) uniquely identifying the subscriber. Required to specify which subscriber's subscription will be modified. |
| Template Name | The name of the template defining the configuration or parameters of the supplementary service to be added. This likely corresponds to predefined service profiles. |
| Supplementary Service Type | The type/category of the supplementary service to add, e.g., call forwarding, call barring, etc. |
Output
The node outputs JSON data representing the result of the Add Supplementary Service operation. This typically includes confirmation of the service addition, status codes, messages, or any returned data from the Summa API indicating success or failure.
If the node supports binary data output, it would relate to any raw response or attachments from the API, but based on the provided code and context, the primary output is structured JSON reflecting the operation outcome.
Dependencies
- Requires an API key credential for authenticating with the Summa API.
- Uses an HTTP client internally to communicate with the Summa backend services.
- The node depends on several internal modules for state management, operation resolution, and execution logic.
- Proper configuration of the Summa API credentials within n8n is necessary before use.
Troubleshooting
Common Issues:
- Missing or invalid IMSI value can cause the operation to fail because the subscriber cannot be identified.
- Incorrect or non-existent template names may lead to errors or no action taken.
- Invalid supplementary service types not supported by the API will result in error responses.
- Authentication failures due to incorrect API credentials.
Error Messages:
- Authentication errors: Check that the API key credential is correctly configured and valid.
- Validation errors: Ensure all required fields (IMSI, Template Name, Supplementary Service Type) are provided and correctly formatted.
- API errors: Review the response message for specific issues like unsupported service types or template mismatches.
Resolving these usually involves verifying input parameters, ensuring correct credential setup, and consulting the Summa API documentation for valid values.
Links and References
- Summa API official documentation (not provided here; consult your API provider)
- n8n documentation on creating and using API credentials
- Telecommunications standards for IMSI and supplementary services (for understanding service types)