mittwald icon

mittwald

Interact with mittwald mStudio API

Actions409

Overview

This node interacts with the mittwald mStudio API to list SSH keys associated with users. It is useful in scenarios where you need to retrieve and manage SSH keys for user accounts programmatically, such as auditing access credentials, automating key rotation, or integrating user key data into other systems.

For example, a system administrator could use this node to fetch all SSH keys for users in their environment to verify which keys are active or to synchronize keys with another service.

Properties

Name Meaning
Limit The maximum number of SSH key resources 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 JSON data containing a list of SSH keys for users. Each item in the output typically represents an SSH key resource with its associated metadata (such as key ID, key value, creation date, etc.). The exact structure depends on the mittwald mStudio API response but generally includes details necessary to identify and manage SSH keys.

No binary data output is indicated.

Dependencies

  • Requires an API key credential for authenticating with the mittwald mStudio API.
  • The node uses the base URL https://api.mittwald.de.
  • Proper configuration of the API authentication credential within n8n is necessary.

Troubleshooting

  • Common issues:

    • Authentication failures due to invalid or missing API credentials.
    • Pagination misconfiguration if limit, skip, and page parameters are not used correctly, potentially resulting in incomplete data retrieval.
    • Network connectivity problems affecting API calls.

  • Error messages:

    • Errors related to unauthorized access usually indicate incorrect API key setup.
    • Invalid parameter errors may occur if skip is not a multiple of limit.

  • Resolutions:

    • Verify that the API key credential is correctly configured and has sufficient permissions.
    • Ensure pagination parameters are set properly; use either skip or page but avoid conflicting values.
    • Check network connectivity and API endpoint availability.

Links and References

Discussion