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 node named "Summa" is designed to interact with the Summa API (version indicated dynamically). It supports multiple resources and operations, including the "HLR Subscription" resource with the "Set PDP Assignations" operation. This particular operation allows users to set or update PDP (Packet Data Protocol) assignations for a given IMSI (International Mobile Subscriber Identity).
Common scenarios where this node would be beneficial include telecom operators or service providers managing subscriber data and network configurations programmatically. For example, updating PDP contexts for subscribers to control their data session parameters or modifying network assignments dynamically based on subscriber profiles.
Properties
| Name | Meaning |
|---|---|
| Imsi | The International Mobile Subscriber Identity, a unique identifier for a mobile user. |
| Pdp Assignations | The PDP assignations string that defines the packet data protocol settings to apply. |
Both properties are required for the "Set PDP Assignations" operation under the "HLR Subscription" resource.
Output
The node outputs JSON data representing the result of the executed operation against the Summa API. The exact structure depends on the API response but typically includes confirmation of the updated PDP assignations or error details if the operation fails.
If the node handles binary data, it would relate to any binary payloads returned by the API, but based on the provided code and operation, the output is primarily JSON.
Dependencies
- Requires an API key credential for authenticating with the Summa API.
- Uses an HTTP client internally to send requests to the Summa backend.
- Depends on n8n's credential management to securely store and access the API authentication token.
- No additional external services beyond the Summa API are indicated.
Troubleshooting
- Authentication errors: Ensure the API key credential is correctly configured and valid.
- Invalid IMSI or PDP assignations: Verify that the IMSI is correctly formatted and that the PDP assignations string complies with expected syntax.
- Network issues: Check connectivity to the Summa API endpoint.
- API errors: Review error messages returned in the JSON output for specific causes such as permission issues or invalid parameters.
Links and References
- Summa API documentation (not provided here; consult your internal or vendor documentation)
- n8n HTTP Request node documentation for understanding underlying request mechanics: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/
