Summa icon

Summa

Consume Summa API (v.0.1.7)
Join our community

Actions182

Overview

The node named "Summa" integrates with the Summa API (version indicated in the code) to perform various operations on telecom-related resources. Specifically, for the Subscriber resource and the Delete Subscriber operation, this node allows users to delete a subscriber record from the system managed by the Summa API.

This node is beneficial in scenarios where telecom operators or service providers need to programmatically manage subscriber data, such as removing inactive or terminated subscribers from their databases. For example, an automated workflow could trigger the deletion of a subscriber after account closure or fraud detection.

Properties

Name Meaning
Subscriber Id The unique identifier of the subscriber to be deleted. This is a required string input.
Operator Name The name of the operator associated with the subscriber. This is a required string input.

Output

The node outputs JSON data representing the result of the delete operation. Typically, this would include confirmation of successful deletion or details about any errors encountered. The exact structure depends on the Summa API's response but generally includes status information.

There is no indication that the node outputs binary data.

Dependencies

  • Requires an active connection to the Summa API via an API key credential.
  • The node uses an HTTP client internally to communicate with the Summa backend.
  • Proper configuration of the API credentials within n8n is necessary for authentication.
  • No other external services are explicitly required.

Troubleshooting

  • Common Issues:

    • Invalid or missing Subscriber Id or Operator Name will likely cause the API call to fail.
    • Incorrect or expired API credentials will prevent successful communication with the Summa API.
    • Network connectivity issues can cause request failures.

  • Error Messages:

    • Authentication errors typically indicate problems with the provided API key; verify and update credentials.
    • Not found errors may occur if the Subscriber Id does not exist; confirm the ID before attempting deletion.
    • Permission denied errors suggest insufficient rights for the API user; check API permissions.

Resolving these usually involves verifying input parameters, ensuring valid credentials, and confirming network access.

Links and References

  • Summa API official documentation (not provided in source, consult your API provider)
  • n8n documentation on creating and using API credentials
  • General HTTP error codes and troubleshooting guides

Discussion