mittwald icon

mittwald

Interact with mittwald mStudio API

Actions100

Overview

This node operation creates a backup schedule for a specified project in the Backup resource. It allows users to automate backups by defining when and how long backups should be retained. This is useful for ensuring regular data protection without manual intervention, especially in environments where project data changes frequently and needs consistent safeguarding.

Practical examples:

  • Scheduling daily backups of a project at 4:05 AM with a retention period of 7 days.
  • Creating weekly backup schedules with descriptive labels to organize multiple backup plans.

Properties

Name Meaning
Project Id The unique identifier of the project for which the backup schedule will be created.
Description Optional text describing the backup schedule for easier identification.
Schedule The execution timing of the backup in crontab notation (e.g., "5 4 * * *" for daily 4:05 AM).
Ttl Time-to-live for the backup schedule, specifying how long backups are retained (e.g., "7d" for 7 days).

Output

The node outputs JSON data representing the newly created backup schedule object as returned by the API. This typically includes details such as the schedule ID, project ID, description, cron schedule, TTL, creation timestamps, and status. There is no binary 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 credential within n8n is necessary for successful requests.

Troubleshooting

  • Invalid Project Id: If the provided project ID does not exist or is incorrect, the API may return an error indicating the project was not found. Verify the project ID before running the node.
  • Malformed Cron Expression: An invalid schedule string can cause scheduling errors. Ensure the cron expression follows standard crontab syntax.
  • TTL Format Errors: The TTL must be a valid time string (e.g., "7d", "24h"). Incorrect formats may lead to rejection by the API.
  • Authentication Failures: Missing or invalid API credentials will prevent the node from connecting to the API. Confirm that the API key is correctly set up in n8n.
  • Network Issues: Connectivity problems with the mittwald API endpoint can cause request failures. Check network access and proxy settings if applicable.

Links and References

Discussion