Actions100
- 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
- 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
Overview
This node allows you to create a basic supplementary service for an SS (Supplementary Service) Subscription via the Summa API. It is designed for telecom or network management scenarios where you need to programmatically manage supplementary services (such as call waiting, call forwarding, etc.) associated with a subscriber's SS subscription.
Common use cases:
- Activating or deactivating supplementary services for a mobile subscriber.
- Automating provisioning workflows for telecom operators.
- Integrating with OSS/BSS systems to manage subscriber features.
Example:
A telecom operator wants to enable "Call Waiting" for a specific subscriber and set its activation and provisioning states using an automated workflow.
Properties
| Name | Type | Meaning |
|---|---|---|
| Activation State | options | The current activation state of the supplementary service (e.g., NOT_ACTIVE, ACTIVE_AND_OPERATIVE). |
| Induction State | options | Indicates whether the service is induced (e.g., NOT_INDUCED, INDUCED). |
| Provisioning State | options | The provisioning status of the service (e.g., NOT_PROVISIONED, PROVISIONED). |
| Registration State | options | The registration status (e.g., REGISTERED, NOT_REGISTERED, ERASED, NOT_APPLICABLE). |
| Supplementary Service Type | string | The type of supplementary service to be managed (e.g., CallWaiting). |
| SS Subscription ID | string | Unique identifier for the SS subscription to which the service applies. |
| Operator ID | string | Identifier for the operator performing the action. |
Output
The node returns a json object containing the result of the operation from the Summa API. The exact structure depends on the API response, but typically includes:
- Status of the operation (success/failure)
- Details of the created supplementary service
- Any error messages if the operation failed
If the API supports binary data, it would represent exported files or documents related to the operation.
Dependencies
- External Service: Requires access to the Summa API endpoint.
- API Credentials: Needs valid Summa API credentials configured in n8n under the name
summaApi. - n8n Configuration: Ensure the credential is tested and available; the node uses a built-in credential test method.
Troubleshooting
Common Issues:
- Invalid Credentials: If the provided Summa API credentials are incorrect or expired, authentication will fail.
- Missing Required Fields: All properties listed above are required. Omitting any will result in validation errors.
- API Errors: If the Summa API returns an error (e.g., invalid SS Subscription ID), the node will output the error message in the response.
Error Messages & Resolutions:
"Authentication failed": Check your Summa API credentials in n8n."Missing required parameter": Ensure all required fields are filled in the node configuration."Resource not found": Verify that the SS Subscription ID and Operator ID are correct and exist in the system.
Links and References
- n8n Documentation
- (If available) Summa API documentation – consult your provider or internal documentation for detailed API specs.