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 subscriber data. Specifically, for the Subscriber resource and the Ask For Information Using PSI operation, it allows querying subscriber information by sending either a JSON payload or a list of requested information fields based on the subscriber's IMSI (International Mobile Subscriber Identity).

Common scenarios include:

  • Retrieving detailed subscriber information from a telecom backend system.
  • Automating requests for specific subscriber data fields without manually crafting API calls.
  • Integrating subscriber data queries into larger workflows for telecom service management.

Practical example:

  • A workflow that, given an IMSI, asks the Summa API for certain subscriber details such as subscription status or profile info, either by sending a custom JSON request or specifying individual fields to retrieve.

Properties

Name Meaning
Imsi The IMSI (International Mobile Subscriber Identity) of the subscriber to query. Required.
Send Json Boolean flag indicating whether to send a raw JSON payload (true) or specify requested info fields (false). Required.
Json Data When "Send Json" is true, this JSON object contains the raw request data to send. Required in that case.
Requested Infos When "Send Json" is false, this is a collection of string values representing the specific subscriber information fields to request. Multiple fields can be specified.

Output

The node outputs JSON data containing the response from the Summa API corresponding to the requested subscriber information. The structure depends on the API response but generally includes subscriber details matching the requested fields or the JSON query sent.

If binary data were involved, it would typically represent files or media related to the subscriber, but this node focuses on JSON responses only.

Dependencies

  • Requires an active connection to the Summa API via an API key credential configured in n8n.
  • Uses internal HTTP client utilities to communicate with the Summa backend.
  • No additional external dependencies beyond the Summa API and its authentication.

Troubleshooting

  • Missing or invalid IMSI: The node requires a valid IMSI string; ensure this is correctly provided.
  • Incorrect JSON format: If "Send Json" is true, the JSON data must be well-formed and match the API schema; otherwise, the request will fail.
  • API authentication errors: Ensure the API key credential is correctly set up and has necessary permissions.
  • Empty or incorrect requested info fields: When not sending JSON, verify that requested info fields are valid and supported by the API.
  • Network or connectivity issues: Check network access to the Summa API endpoint.

Common error messages may relate to authentication failures, malformed requests, or missing required parameters. Resolving these usually involves verifying credentials, input data formats, and parameter completeness.

Links and References

Discussion