mittwald icon

mittwald

Interact with mittwald mStudio API

Actions409

Overview

This node operation, App Link Database, is designed to link a specific database to an app installation within the mittwald mStudio API ecosystem. It allows users to associate a database with an app installation by specifying identifiers and the purpose of the linkage. This can be useful in scenarios where apps need to interact with or manage data stored in different databases, such as syncing user data, caching information, or custom integrations.

Practical examples include:

  • Linking a primary database to an app installation for main data operations.
  • Associating a cache database to improve performance by storing frequently accessed data.
  • Connecting a custom database for specialized use cases or third-party integrations.

Properties

Name Meaning
App Installation Id The unique identifier of the app installation to which the database will be linked.
Database Id The unique identifier of the database to link with the app installation.
Database User Ids A JSON object containing user IDs related to the database, allowing fine-grained control or mapping of users.
Purpose The role of the linked database; options are:
- Primary
- Cache
- Custom

Output

The node outputs JSON data representing the result of the linking operation between the app installation and the database. This typically includes confirmation details such as success status, linked resource identifiers, and any metadata returned by the mittwald mStudio API.

There is no indication that this node outputs binary data.

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 and an OpenAPI specification (openapi.json) bundled internally for request building.

Troubleshooting

  • Missing Required Fields: Ensure that "App Installation Id", "Database Id", and "Purpose" are provided, as they are mandatory.
  • Invalid JSON in Database User Ids: The "Database User Ids" property expects valid JSON. Invalid JSON input will cause parsing errors.
  • Authentication Errors: Verify that the API key credential is correctly configured and has sufficient permissions.
  • API Endpoint Issues: Network issues or incorrect base URL configuration may lead to request failures.
  • Purpose Value Errors: Only "primary", "cache", or "custom" are accepted values for the purpose field.

Links and References

Discussion