mittwald icon

mittwald

Interact with mittwald mStudio API

Actions409

Overview

This node interacts with the mittwald mStudio API to manage domain ingress resources. Specifically, the "Ingress Delete Ingress" operation allows users to delete an existing ingress by specifying its unique identifier. This is useful in scenarios where you need to programmatically remove routing rules or access points configured in your domain setup, such as cleaning up obsolete ingress entries or automating infrastructure changes.

Practical examples include:

  • Automatically deleting ingress configurations when decommissioning services.
  • Managing ingress lifecycle as part of CI/CD pipelines.
  • Cleaning up test or temporary ingress entries after deployment tests.

Properties

Name Meaning
Ingress Id The unique identifier of the ingress to delete. This is a required string input.

Output

The node outputs JSON data representing the response from the mittwald mStudio API after attempting to delete the specified ingress. Typically, this will confirm whether the deletion was successful or provide error details if it failed.

If the API supports binary data output for this operation (not indicated here), it would represent related binary content; however, based on the static code and properties, the output is JSON only.

Dependencies

  • Requires an API key credential for authenticating with the mittwald mStudio API.
  • The node uses the base URL https://api.mittwald.de for all requests.
  • The node depends on the @devlikeapro/n8n-openapi-node package for building request properties from the OpenAPI specification.

Troubleshooting

  • Missing or invalid Ingress Id: Ensure that the "Ingress Id" property is provided and correctly references an existing ingress. Errors may occur if the ID is empty or malformed.
  • Authentication errors: Verify that the API key credential is correctly configured and has sufficient permissions to delete ingress resources.
  • Network or API errors: Check connectivity to https://api.mittwald.de and ensure the API service is operational.
  • Permission denied or forbidden errors: Confirm that the authenticated user or token has rights to delete ingress entries.

Common error messages might include HTTP 401 Unauthorized, 403 Forbidden, or 404 Not Found if the ingress ID does not exist.

Links and References

Discussion