mittwald icon

mittwald

Interact with mittwald mStudio API

Actions409

Overview

This node interacts with the mittwald mStudio API to read all notifications. It allows users to retrieve notification data filtered by various criteria such as severity levels, reference IDs, aggregates, and domains. This is useful in scenarios where you want to monitor or process system or application notifications programmatically, for example, to trigger workflows based on specific alerts or to aggregate notification data for reporting.

Properties

Name Meaning
Severities Filter notifications by their severity levels. Accepts a JSON array of severities.
Reference Id Filter notifications by a specific reference identifier.
Reference Aggregate Filter notifications by an aggregate reference string.
Reference Domain Filter notifications by a domain associated with the reference.

Output

The node outputs JSON data representing the list of notifications retrieved from the mittwald mStudio API. Each notification object typically contains details such as severity, reference information, message content, timestamps, and other metadata relevant to the notification.

If binary data were involved (not indicated here), it would represent attachments or files related to notifications, but this node focuses on JSON notification data only.

Dependencies

  • Requires an API key credential for authenticating with the mittwald mStudio API.
  • The node uses the base URL https://api.mittwald.de to send requests.
  • No additional external dependencies beyond the API and n8n's HTTP request capabilities.

Troubleshooting

  • Common issues:

    • Invalid or missing API credentials will cause authentication failures.
    • Incorrect filter values (e.g., malformed JSON in Severities) may result in empty responses or errors.
    • Network connectivity problems can prevent access to the mittwald API.
  • Error messages:

    • Authentication errors usually indicate invalid or expired API keys; verify and update credentials.
    • Validation errors on query parameters suggest checking the format and correctness of input filters.
    • Timeout or connection errors require checking network settings and API availability.

Links and References

Discussion