mittwald icon

mittwald

Interact with mittwald mStudio API

Actions409

Overview

This node is designed to interact with the "User" resource of the mittwald mStudio API, specifically to retrieve an OAuth access token for a user. It performs the OAuth client credentials flow by sending a request with the appropriate authorization header containing base64-encoded client credentials. This node is useful in scenarios where you need to programmatically obtain an access token to authenticate subsequent API requests on behalf of a user or service.

Practical examples include:

  • Automating authentication to the mittwald mStudio API before performing further operations.
  • Integrating with systems that require dynamic retrieval of OAuth tokens without manual intervention.
  • Building workflows that refresh or obtain new access tokens as needed.

Properties

Name Meaning
Authorization The HTTP Authorization header value containing the client credentials (client_id and client_secret) encoded in base64 and prefixed with "Basic ". This must follow RFC6749 Section 2.3.1. Example: Basic Y2xpZW50X2lkOmNsaWVudF9zZWNyZXQ=

Output

The node outputs JSON data representing the response from the OAuth token endpoint. This typically includes fields such as the access token, token type, expiration time, and possibly refresh token information depending on the OAuth server's response.

No binary data output is expected from this operation.

Dependencies

  • Requires an API key credential configured in n8n to authenticate requests to the mittwald mStudio API.
  • The node depends on the mittwald mStudio API being accessible at https://api.mittwald.de.
  • Proper client credentials (client_id and client_secret) must be provided and encoded correctly in the Authorization header.

Troubleshooting

  • Invalid Client Credentials: If the client ID or secret are incorrect or improperly encoded, the API will reject the request. Ensure the credentials are concatenated as client_id:client_secret, then base64 encoded, and prefixed with Basic .
  • Forbidden Submission of Credentials in Body: The node enforces sending credentials only via the Authorization header. Submitting them in the request body will cause errors.
  • Network Issues: Connectivity problems to https://api.mittwald.de will prevent token retrieval.
  • Expired or Revoked Credentials: Tokens may fail if the client credentials have been revoked or expired; verify their validity.
  • Error Responses: The node will surface error messages returned by the API, which often include HTTP status codes and descriptive messages. Review these to diagnose issues.

Links and References

Discussion