mittwald icon

mittwald

Interact with mittwald mStudio API

Actions100

Overview

This node operation "App Unlink Database" is designed to disconnect or unlink a specific database from an app installation within the mittwald mStudio API environment. It is useful in scenarios where you want to remove the association between an app and a database, for example, when decommissioning a database, migrating data, or reorganizing app resources.

Practical examples include:

  • Removing a database that is no longer needed by a particular app installation.
  • Cleaning up app configurations by unlinking unused databases.
  • Preparing an app installation for reassignment to a different database.

Properties

Name Meaning
App Installation Id The unique identifier of the app installation from which the database will be unlinked.
Database Id The unique identifier of the database to unlink from the specified app installation.

Output

The node outputs JSON data representing the result of the unlink operation. This typically includes confirmation of the unlink action, such as success status or details about the updated app installation state after the database has been removed.

No binary data output is indicated.

Dependencies

  • Requires an API key credential for authentication with the mittwald mStudio API.
  • The node communicates with the mittwald API endpoint at https://api.mittwald.de.
  • Proper configuration of the API credentials in n8n is necessary for successful requests.

Troubleshooting

  • Common issues:

    • Invalid or missing App Installation Id or Database Id can cause the unlink operation to fail.
    • Authentication errors if the API key credential is not set or invalid.
    • Network connectivity problems preventing access to the mittwald API.
  • Error messages and resolutions:

    • Unauthorized / 401 error: Check that the API key credential is correctly configured and has sufficient permissions.
    • Not Found / 404 error: Verify that the provided App Installation Id and Database Id exist and are correct.
    • Bad Request / 400 error: Ensure all required parameters are provided and valid.
    • Timeouts or network errors: Confirm network connectivity and API availability.

Links and References

Discussion