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 on different resources. Specifically, for the Templates resource and the Remove Template operation, it allows users to delete a template identified by its name, associated operator, and entity type. This is useful in scenarios where templates need to be managed dynamically, such as removing outdated or incorrect templates from a system that relies on templated configurations or data structures.
Practical examples include:
- Removing a specific message or configuration template used in telecom services.
- Cleaning up templates related to operators or entities no longer in use.
- Automating template lifecycle management within a larger workflow.
Properties
| Name | Meaning |
|---|---|
| Template Name | The exact name of the template to be removed. |
| Operator Name | The name of the operator associated with the template. |
| Templatizable Entity | The type of entity the template applies to (e.g., subscriber, device, etc.). |
Output
The node outputs JSON data representing the result of the remove template operation. Typically, this will include confirmation of successful deletion or details about any errors encountered. The output structure depends on the Summa API response but generally includes status information and possibly metadata about the removed template.
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.
- Proper credentials must be configured in n8n to authenticate requests.
- The node depends on internal modules for state management and operation resolution but these are bundled and do not require external installation.
Troubleshooting
Common issues:
- Incorrect or missing template name, operator name, or entity type can cause the removal to fail.
- Authentication failures if the API key credential is invalid or expired.
- Network connectivity problems preventing communication with the Summa API.
Error messages:
- Errors returned from the Summa API typically indicate whether the template was not found or if permission was denied.
- Credential-related errors suggest checking the API key validity and permissions.
Resolutions:
- Verify all required properties are correctly set and correspond exactly to existing templates.
- Ensure the API key credential is properly configured and has necessary permissions.
- Check network access and firewall settings to allow outbound requests to the Summa API endpoint.
Links and References
- Summa API Documentation (replace with actual URL)
- n8n documentation on Creating Custom Nodes
- General API authentication best practices in n8n workflows