mittwald icon

mittwald

Interact with mittwald mStudio API

Actions409

Overview

This node interacts with the Marketplace resource of an API, specifically performing the "Extension Change Context" operation. It allows users to change the context of a given extension contributed by a specific contributor. This is useful in scenarios where extensions need to be reassigned or their operational context switched between different scopes such as projects or customers.

Practical examples include:

  • Switching an extension's context from a project scope to a customer scope.
  • Managing extensions contributed by different contributors and updating their contexts dynamically within automation workflows.

Properties

Name Meaning
Contributor Id The unique identifier of the contributor who owns the extension.
Extension Id The unique identifier of the extension whose context is to be changed.
Context The new context for the extension. Options are: "Project" or "Customer".

Output

The node outputs JSON data representing the result of the context change operation on the specified extension. This typically includes confirmation details or updated extension information returned by the API after successfully changing the context.

No binary data output is indicated.

Dependencies

  • Requires an API key credential to authenticate requests against the mittwald mStudio API.
  • The base URL for API requests is https://api.mittwald.de.
  • The node uses standard HTTP headers for JSON content (Accept: application/json, Content-Type: application/json).

Troubleshooting

  • Missing or invalid Contributor Id or Extension Id: Ensure these IDs are correctly provided and correspond to existing entities in the system.
  • Invalid context value: Only "project" or "customer" are valid options; providing other values will cause errors.
  • Authentication errors: Verify that the API key credential is correctly configured and has sufficient permissions.
  • API connectivity issues: Check network access to https://api.mittwald.de and ensure no firewall or proxy blocks the requests.

Common error messages may relate to authorization failures, invalid parameters, or resource not found. Resolving them involves verifying credentials, input values, and resource existence.

Links and References

Discussion