Summa icon

Summa

Consume Summa API (v.0.1.7)
Join our community

Actions182

Overview

This node integrates with the Summa API to manage IMS (IP Multimedia Subsystem) subscriptions, specifically allowing users to add a Public User Identity to an IMS subscription. This operation is useful in telecommunications scenarios where managing user identities within IMS is required, such as provisioning new public identities for subscribers or updating existing ones.

Practical examples include:

  • Adding a new public identity to a subscriber's IMS profile.
  • Managing multiple public identities linked to a single private identity.
  • Configuring priority levels and service profiles associated with the public user identity.

Properties

Name Meaning
Send Json Whether to send the request payload as raw JSON (true) or use structured fields (false).
Json Data The raw JSON data to send when "Send Json" is true.
Additional Fields A collection of optional fields used when "Send Json" is false:
- Private Identity The private identity associated with the public user identity.
- Public Identity The public user identity to be added.
- Display Name A display name for the public user identity.
- Extended Priorities Multiple entries defining priority settings, each with:
-- Id Numeric identifier for the priority entry.
-- Priority Namespace Namespace categorizing the priority.
-- Priority Level The level of priority assigned.
- Barring Indication Indicates if barring is applied to this identity.
- Service Priority Level Defines the priority level of the service.
- Service Profile List Multiple service profile values associated with the identity.

Output

The node outputs JSON data representing the response from the Summa API after attempting to add the public user identity. This typically includes confirmation details, status codes, or error messages returned by the API.

If binary data were involved (not indicated here), it would represent files or media related to the operation, but this node focuses on JSON responses.

Dependencies

  • Requires an API key credential for authenticating with the Summa API.
  • The node uses an HTTP client internally to communicate with the Summa backend.
  • Proper configuration of the Summa API credentials in n8n is necessary before using this node.

Troubleshooting

  • Common Issues:
    • Invalid or missing API credentials will cause authentication failures.
    • Incorrectly formatted JSON in the "Json Data" property when "Send Json" is enabled can lead to request errors.
    • Omitting required fields like "Public Identity" when not sending raw JSON may result in validation errors.
  • Error Messages:
    • Authentication errors usually indicate invalid API keys; verify and update credentials.
    • Validation errors from the API often specify missing or malformed fields; ensure all required properties are correctly set.
    • Network or timeout errors suggest connectivity issues; check network access and API endpoint availability.

Links and References

Discussion