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 "Sim Add" operation in the Summa node allows users to add new SIM card data into the Summa system via its API. This operation is useful for telecom operators or service providers who need to programmatically register SIM cards with detailed attributes such as IMSI strings, external identifiers, security credentials, and ISIM configurations.
Typical use cases include:
- Bulk importing SIM card information from an external database.
- Automating SIM provisioning workflows.
- Integrating SIM management into broader telecom service orchestration.
For example, a user can provide either raw JSON data representing multiple SIMs or structured form inputs specifying IMSI lists and SIM security details, which the node then sends to the Summa backend to create the SIM records.
Properties
| Name | Meaning |
|---|---|
| Operator Name | The name of the operator responsible for the SIMs being added. |
| Common Sim Security Name | The common security profile name applied to the SIMs. |
| Send Json | Boolean flag indicating whether to send raw JSON data (true) or structured form data (false). |
| Json Data | Raw JSON input containing SIM data to be sent directly when Send Json is true. |
| Imsi List | A collection of IMSI entries (when Send Json is false), each including: - IMSI String - Multiple External Identifiers (each with Id, Identifier string, Type, Trace Active flag) - Default External Identifier - Mobile Station Category |
| Sim | SIM security and configuration details (when Send Json is false), including: - ICC ID - PUK code - OPc value - Ki key - Gete UICCID - ISIM configuration list (with ICC ID, IMS template, and IMPU configuration list detailing public identities, service profiles, and transparent data templates) |
Output
The node outputs JSON data representing the response from the Summa API after attempting to add the SIM(s). This typically includes confirmation of created SIM records, any generated IDs, status messages, or error details if the operation failed.
If binary data were involved (not indicated here), it would represent files or attachments related to the SIM data, but this node focuses on JSON-based API responses.
Dependencies
- Requires an API key credential for authenticating with the Summa backend API.
- Uses an HTTP client internally to communicate with the Summa REST API.
- The node depends on the Summa API version specified in the bundled source (version referenced dynamically).
- No additional environment variables are explicitly required beyond the API credential.
Troubleshooting
Common Issues:
- Missing or invalid API credentials will cause authentication failures.
- Incorrectly formatted JSON in the
Json Dataproperty may lead to request errors. - Omitting required fields like Operator Name or Common Sim Security Name will result in validation errors.
- Providing inconsistent or incomplete IMSI or SIM details when not using raw JSON can cause backend rejections.
Error Messages:
- Authentication errors: Check that the API key credential is correctly configured and valid.
- Validation errors: Review the input properties to ensure all required fields are filled and properly formatted.
- Network or timeout errors: Verify network connectivity to the Summa API endpoint.
Links and References
- Summa API official documentation (not provided in source; consult your Summa API provider)
- n8n documentation on creating custom nodes and handling API credentials: https://docs.n8n.io/
- JSON formatting guidelines for input data: https://www.json.org/json-en.html
