Summa icon

Summa

Consume Summa API (v.0.1.7)
Join our community

Actions182

Overview

This node integrates with the Summa API to perform various operations related to telecommunications subscriptions and services. Specifically, for the "SS Subscription" resource and the "Add Supplementary Service By Msisdn" operation, it allows users to add a supplementary service to a subscriber identified by their MSISDN (mobile phone number). This is useful in telecom management scenarios where operators need to enable additional services (like call forwarding, call barring, etc.) on a subscriber's line programmatically.

Practical examples include:

  • Automatically enabling a voicemail service for a new subscriber.
  • Adding call waiting or call forwarding services based on customer requests.
  • Managing supplementary services during SIM swaps or subscription updates.

Properties

Name Meaning
Msisdn The mobile phone number (MSISDN) of the subscriber to whom the supplementary service will be added. Must be provided as a string.
Template Name The name of the template defining the supplementary service configuration to apply.
Supplementary Service Type The type/category of the supplementary service to add (e.g., call forwarding, call barring).

Output

The node outputs JSON data representing the result of the API call to add the supplementary service. This typically includes confirmation details such as success status, any identifiers related to the newly added service, and possibly error messages if the operation failed.

If the node supports binary data output (not explicitly shown here), it would represent any files or attachments returned by the API, but this operation primarily deals with JSON responses.

Dependencies

  • Requires an API key credential for authenticating with the Summa API.
  • Uses an HTTP client internally to communicate with the Summa backend.
  • The node depends on the Summa API version specified in the bundled code (v.${F.version}).
  • No additional external services are required beyond the Summa API endpoint.

Troubleshooting

  • Common issues:

    • Invalid or missing MSISDN: Ensure the MSISDN is correctly formatted and provided.
    • Incorrect template name or supplementary service type: Verify that these values match those configured in the Summa system.
    • Authentication failures: Check that the API key credential is valid and has necessary permissions.
    • Network or connectivity problems: Confirm that the n8n instance can reach the Summa API endpoint.

  • Error messages:

    • Authentication errors usually indicate invalid credentials; reconfigure the API key.
    • Validation errors from the API may point to incorrect input parameters; review property values.
    • Timeout or connection errors suggest network issues; verify connectivity and retry.

Links and References

Discussion