mittwald icon

mittwald

Interact with mittwald mStudio API

Actions409

Overview

This node interacts with the Marketplace resource to list extensions owned by a specific contributor. It is useful for users who want to retrieve and manage their own published extensions in the Marketplace, such as developers or organizations tracking their contributions. For example, a developer can use this node to fetch all their extensions, paginate through them, and display or process the data further.

Properties

Name Meaning
Contributor Id The unique identifier of the contributor whose extensions are to be listed (required).
Limit The maximum number of extensions to return in the response.
Skip The number of items to skip before starting to collect the result set; should be multiple of limit.
Page The page number to display; functions similarly to skip. If both page and skip are set, skip takes precedence.

Output

The node outputs a JSON array containing the list of extensions owned by the specified contributor. Each item in the array represents an extension with its associated metadata as returned by the Marketplace API. There is no binary data output.

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 key credential within n8n is necessary for successful requests.

Troubleshooting

  • Common issues:

    • Missing or invalid contributor ID will cause the request to fail or return empty results.
    • Incorrect API credentials or expired tokens will lead to authentication errors.
    • Pagination parameters (limit, skip, page) not set correctly may result in unexpected or empty responses.

  • Error messages:

    • Authentication errors typically indicate invalid or missing API keys; verify and update credentials.
    • Validation errors may occur if required parameters like Contributor Id are omitted; ensure all required fields are filled.
    • Rate limiting or server errors from the API should be handled by retrying after some delay.

Links and References

Discussion