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 integrates with the Summa API to perform various operations related to telecommunications subscriptions. Specifically, for the SS Subscription resource and the Remove Supplementary Service operation, it allows users to remove a supplementary service from a subscriber's subscription by specifying key identifiers.
Common scenarios include managing mobile network subscriber services where operators need to programmatically disable or remove additional services (like call forwarding, call barring, etc.) associated with a subscriber's profile.
Practical example: A telecom operator wants to deactivate a specific supplementary service on a subscriber's account identified by their IMSI (International Mobile Subscriber Identity) using a predefined template name and the type of supplementary service to be removed.
Properties
| Name | Meaning |
|---|---|
| Imsi | The International Mobile Subscriber Identity that uniquely identifies the subscriber. |
| Template Name | The name of the template used to define the removal operation parameters or configuration. |
| Supplementary Service Type | The type/category of the supplementary service to be removed from the subscription. |
Output
The node outputs JSON data representing the result of the remove supplementary service operation. This typically includes confirmation of success or failure, status codes, and any relevant messages returned by the Summa API.
If the operation involves binary data (not indicated here), it would represent raw response payloads or files, but this node primarily deals with JSON responses.
Dependencies
- Requires an active connection to the Summa API via an API key credential.
- The node depends on internal helper classes for HTTP requests, state management, and operation resolution/execution.
- Proper configuration of the Summa API credentials in n8n is necessary before use.
Troubleshooting
Common issues:
- Invalid or missing IMSI value will cause the operation to fail as the subscriber cannot be identified.
- Incorrect template name or supplementary service type may lead to errors or no changes applied.
- Network or authentication failures with the Summa API can prevent successful execution.
Error messages:
- Authentication errors indicate invalid or expired API credentials; reconfigure the API key.
- Validation errors usually point to missing or malformed input properties; ensure all required fields are correctly filled.
- API response errors should be checked against Summa API documentation for detailed troubleshooting.
Links and References
- Summa API Documentation (replace with actual URL)
- n8n Documentation on Creating Custom Nodes
- Telecom standards for IMSI and supplementary services (e.g., 3GPP specifications)