Summa icon

Summa

Consume Summa API (v.0.1.7)

Actions182

Overview

This node integrates with the Summa API to perform various operations related to telecom data management. Specifically, for the "CRUD PLMN" resource and the "Add PLMN To PLMN Group" operation, it allows users to add a Public Land Mobile Network (PLMN) entry into an existing PLMN group within the Summa system.

This functionality is useful in scenarios where telecom operators or administrators need to manage network configurations dynamically, such as grouping multiple PLMNs under a single logical entity for easier management or reporting.

Practical example: A telecom operator wants to organize several PLMNs representing different geographic regions into groups for streamlined policy application or monitoring. Using this node, they can programmatically add new PLMNs to these groups without manual intervention.

Properties

Name Meaning
Operator Name The name of the telecom operator associated with the PLMN being added.
Plmn Group Name The name of the PLMN group to which the PLMN will be added.
Plmn Name The identifier or name of the PLMN that is to be added to the specified PLMN group.

Output

The node outputs JSON data representing the result of the "Add PLMN To PLMN Group" operation. This typically includes confirmation details such as success status, identifiers of the updated PLMN group, and possibly metadata about the added PLMN.

If the operation involves binary data (not indicated here), it would represent relevant files or attachments returned by the API, but this node primarily deals with JSON responses.

Dependencies

  • Requires an active connection to the Summa API via an API key credential.
  • The node depends on the summaApi credential configured in n8n for authentication.
  • Uses internal helper classes for HTTP requests, state management, and operation resolution specific to the Summa API integration.

Troubleshooting

  • Common issues:

    • Invalid or missing API credentials will cause authentication failures.
    • Providing non-existent PLMN group names or PLMN names may result in errors from the API indicating that the target group or PLMN does not exist.
    • Network connectivity problems can prevent successful API calls.
  • Error messages:

    • Authentication errors: Verify that the API key credential is correctly set up and has necessary permissions.
    • Not found errors: Check that the PLMN group and PLMN names are correct and exist in the Summa system.
    • Validation errors: Ensure all required properties (Operator Name, Plmn Group Name, Plmn Name) are provided and valid.

Links and References

Discussion