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 "Create Subscriber" operation in the Subscriber resource of this node allows users to create a new subscriber record by sending detailed subscriber data to the Summa API. This node is useful in telecom or mobile network management scenarios where automated provisioning or updating of subscriber information is required. For example, it can be used to onboard new mobile subscribers with their associated MSISDNs, IMSIs, roaming profiles, and service templates, or to update subscriber configurations programmatically.
Properties
| Name | Meaning |
|---|---|
| Operator Name | The name of the operator managing the subscriber. This is a required string input. |
| Send Json | A boolean flag indicating whether to send raw JSON data directly (true) or to use structured additional fields (false). |
| Json Data | When Send Json is true, this JSON input contains the full subscriber data payload to send as-is. |
| Additional Fields | When Send Json is false, this collection contains structured subscriber details including: - Subscriber: subscriberId, roamingTemplate, iot (boolean) - Msisdn Info List: multiple MSISDN entries each with alert indicator, SMS route profile, SS template, and nested IMSI relationships with PDP addresses - Imsi Subscription List: multiple IMSI subscriptions with detailed templates, roaming profiles, APN addresses, and SS settings - Isim: ISIM card info including ICC ID, IMS template, and multiple IMPU configurations with service profile templates and transparent data templates |
Output
The node outputs JSON data representing the response from the Summa API after attempting to create the subscriber. This typically includes confirmation of the created subscriber, any assigned IDs, status messages, or error details if creation failed. The output does not explicitly mention binary data, so it is assumed to be purely JSON.
Dependencies
- Requires an API key credential for authenticating with the Summa API.
- Uses the Summa API endpoint configured via credentials.
- Relies on internal helper classes for HTTP requests, state management, and operation resolution/execution.
- No other external services are explicitly required beyond the Summa API.
Troubleshooting
- Invalid or missing operator name: Since "Operator Name" is required, omitting it will cause errors. Ensure it is provided.
- Malformed JSON when
Send Jsonis true: If the JSON data is invalid or incomplete, the API call may fail. Validate JSON before sending. - Incorrectly structured additional fields: When not sending raw JSON, ensure all nested collections (MSISDN lists, IMSI relationships, etc.) follow the expected structure.
- Authentication errors: Verify that the API key credential is correctly set up and has necessary permissions.
- API endpoint issues: Network problems or incorrect API URLs can cause request failures.
- Error messages from the API: These should be inspected in the node output; common issues include duplicate subscriber IDs or invalid template names.
Links and References
- Summa API Documentation (replace with actual URL if available)
- n8n documentation on Creating Custom Nodes
- General JSON validation tools for preparing
Json Datainput
This summary is based solely on static analysis of the provided source code and property definitions without runtime execution.