mittwald icon

mittwald

Interact with mittwald mStudio API

Actions409

Overview

This node operation updates an existing Cronjob by modifying its properties such as activation status, description, destination URL, email notification, execution interval, timeout, and alert thresholds. It is useful for automating scheduled tasks where you need to change the behavior or parameters of a previously configured cronjob without recreating it from scratch.

Practical examples include:

  • Changing the frequency of a data synchronization task.
  • Updating the webhook URL that a cronjob triggers.
  • Adjusting alert thresholds to control when failure notifications are sent.
  • Activating or deactivating a cronjob based on operational needs.

Properties

Name Meaning
Cronjob Id The unique identifier of the Cronjob to be updated.
Active Whether the Cronjob is active (true) or inactive (false).
Description A textual description of the Cronjob's purpose or details.
Destination JSON object specifying the destination configuration, typically including a URL.
Email Email address to receive notifications related to the Cronjob.
Failed Execution Alert Threshold Numeric threshold defining after how many failed executions an alert should be sent.
Interval Cron expression string defining how often the Cronjob runs (e.g., "*/5 * * * *").
Timeout Numeric value specifying the timeout duration for the Cronjob execution in seconds.

Output

The node outputs JSON data representing the updated state of the Cronjob after the update operation. This typically includes all the properties sent in the request along with any additional metadata returned by the API.

If the node supports binary data output, it would generally relate to raw response data or logs, but this specific operation focuses on JSON updates and does not indicate 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 network access and valid credentials must be configured in n8n for successful API calls.

Troubleshooting

  • Invalid Cronjob Id: If the provided Cronjob Id does not exist or is incorrect, the API will likely return an error indicating the resource was not found. Verify the ID before updating.
  • Malformed JSON in Destination: The destination property expects a valid JSON object. Invalid JSON syntax will cause parsing errors. Ensure the JSON is well-formed.
  • Invalid Cron Expression: The interval property must be a valid cron expression. Incorrect formats may lead to scheduling errors or API rejections.
  • Authentication Errors: Missing or invalid API credentials will prevent the update operation. Confirm that the API key is correctly set up in n8n.
  • Timeouts or Network Issues: Network connectivity problems can cause request failures. Check your internet connection and API availability.

Links and References

Discussion