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 telecom data management. Specifically, for the "CRUD Operator" resource and the "Find All Operators" operation, it retrieves a list of all operators with support for pagination and sorting. This is useful in scenarios where you need to fetch operator data in bulk, such as syncing operator lists, displaying them in user interfaces, or processing them for analytics.

Practical examples:

  • Fetching a paginated list of telecom operators to populate a dropdown menu.
  • Retrieving sorted operator data for reporting purposes.
  • Integrating operator information into other workflows that require operator metadata.

Properties

Name Meaning
Pagination Search Dto A collection of parameters to control pagination and sorting:
- Page The page number to retrieve (starting from 0).
- Page Size Number of items per page.
- Order By Field name by which to order the results (e.g., operator name).
- Order Type Sorting direction, typically ascending or descending.

Output

The node outputs JSON data containing the list of operators retrieved from the Summa API according to the specified pagination and sorting parameters. The structure typically includes an array of operator objects with their details.

If the node supports binary data output, it would represent any associated files or media related to operators, but based on the provided code and context, the output is primarily JSON.

Dependencies

  • Requires an active connection to the Summa API via an API key credential.
  • The node depends on internal helper classes for HTTP requests, state management, and operation resolution.
  • No additional external services are explicitly required beyond the Summa API.
  • Proper configuration of the API credentials within n8n is necessary.

Troubleshooting

  • Common issues:

    • Invalid or missing API credentials will cause authentication failures.
    • Incorrect pagination parameters (e.g., negative page numbers) may result in errors or empty responses.
    • Network connectivity problems can prevent successful API calls.

  • Error messages:

    • Authentication errors typically indicate invalid API keys; verify and update credentials.
    • Parameter validation errors suggest incorrect input values; ensure pagination and sorting fields are valid.
    • Timeout or network errors require checking internet connectivity and API availability.

Links and References

Discussion