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 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
- Set HLR Profile
- 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
IMSI → Remove IMSI
AI-generatedOverview
This node, named "Summa," interacts with the Summa API to perform various operations on different resources. Specifically, for the IMSI resource with the Remove IMSI operation, it allows users to remove an IMSI (International Mobile Subscriber Identity) from the system managed by the Summa API. This is useful in telecom or mobile network management scenarios where IMSIs need to be deregistered or deleted, such as when decommissioning a subscriber or cleaning up stale data.
Practical examples include:
- Removing an IMSI after a subscriber has been permanently disconnected.
- Cleaning up IMSI records during SIM swaps or subscription changes.
- Managing IMSI lifecycle in automated telecom workflows.
Properties
| Name | Meaning |
|---|---|
| Imsi | The IMSI string value to be removed. This is a required field and should contain the exact IMSI identifier that needs to be deleted from the system. |
Output
The node outputs JSON data representing the result of the Remove IMSI operation. Typically, this will include confirmation of successful removal or details about any errors encountered. The exact structure depends on the Summa API response but generally includes status information and possibly metadata about the removed IMSI.
No binary data output is indicated for this operation.
Dependencies
- Requires an active connection to the Summa API via an API key credential.
- The node uses an HTTP client internally to communicate with the Summa backend service.
- Proper configuration of the Summa API credentials within n8n is necessary for authentication.
- The node depends on internal modules for state management and operation resolution but these are abstracted away from the user.
Troubleshooting
Common issues:
- Invalid or missing IMSI value: Ensure the IMSI property is correctly set and matches the expected format.
- Authentication failures: Verify that the API key credential is valid and has sufficient permissions.
- Network or connectivity problems: Check network access to the Summa API endpoint.
- API errors due to non-existent IMSI: Attempting to remove an IMSI that does not exist may return an error; verify IMSI existence before removal.
Error messages:
- Authentication errors typically indicate invalid credentials; reconfigure the API key.
- Validation errors usually point to missing or malformed IMSI input.
- HTTP errors might indicate connectivity or server-side issues; retry or check API status.
Links and References
- Summa API Documentation (replace with actual URL if available)
- n8n documentation on Creating Custom Nodes
- General info on IMSI: Wikipedia - IMSI
