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 telecommunications subscriptions and services. Specifically, for the HLR Subscription resource with the Add PDP operation, it allows adding a Packet Data Protocol (PDP) context to a subscriber identified by their IMSI (International Mobile Subscriber Identity). This is useful in scenarios where you need to enable or modify data connectivity settings for mobile subscribers programmatically.

Practical examples include:

  • Activating a new data session for a subscriber.
  • Managing subscriber data profiles in bulk via automation.
  • Integrating telecom backend systems with external workflows for subscriber management.

Properties

Name Meaning
Imsi The International Mobile Subscriber Identity of the subscriber to whom the PDP context will be added. This uniquely identifies the mobile subscriber.
Pdp The Packet Data Protocol context identifier or configuration string that specifies the data session parameters to add for the subscriber.

Both properties are required inputs when performing the Add PDP operation on an HLR Subscription.

Output

The node outputs JSON data representing the result of the Add PDP operation. This typically includes confirmation of the action, status codes, and any relevant response details from the Summa API indicating success or failure of adding the PDP context.

If the operation involves binary data (not indicated here), it would represent raw data returned from the API, but this node primarily deals with JSON responses.

Dependencies

  • Requires an active connection to the Summa API via an API key credential configured in n8n.
  • Uses an HTTP client internally to communicate with the Summa backend service.
  • Depends on the Summa API version specified in the node (v.1 as per the bundled code).
  • No additional environment variables are explicitly required beyond the API authentication setup.

Troubleshooting

  • Common issues:
    • Invalid or missing IMSI or PDP values will cause the API call to fail.
    • Authentication errors if the API key credential is not set up correctly.
    • Network connectivity problems between n8n and the Summa API endpoint.
  • Error messages:
    • Authentication failures usually indicate invalid credentials; verify and update the API key.
    • Validation errors from the API may specify which input parameter is incorrect or missing.
    • Timeout or network errors suggest checking internet connectivity or API availability.

Resolving these generally involves verifying input correctness, ensuring proper credential configuration, and confirming network access.

Links and References

  • Summa API official documentation (refer to your organization's internal or public API docs)
  • n8n documentation on creating and using API credentials
  • General info on IMSI and PDP contexts in mobile networks for background understanding

Discussion