mittwald icon

mittwald

Interact with mittwald mStudio API

Actions100

Overview

This node operation updates an existing Cronjob by modifying its properties such as activation status, description, destination URL, email notification, execution interval, and timeout. It is useful for managing scheduled tasks programmatically within workflows, allowing users to adjust when and how their cronjobs run without manual intervention.

Practical examples include:

  • Changing the frequency of a data synchronization task.
  • Updating the webhook URL that a cronjob triggers.
  • Enabling or disabling a cronjob based on workflow conditions.
  • Adjusting timeout settings to prevent long-running jobs.

Properties

Name Meaning
Cronjob Id The unique identifier of the Cronjob to be updated.
Active Whether the Cronjob is enabled (true) or disabled (false).
Description A textual description of the Cronjob's purpose or details.
Destination JSON object specifying the target URL or endpoint where the Cronjob sends requests.
Email Email address to notify regarding the Cronjob's execution or status.
Interval Cron expression defining how often the Cronjob runs (e.g., "*/5 * * * *" for every 5 minutes).
Timeout Maximum allowed execution time in seconds before the Cronjob times out (0 means no timeout).

Output

The node outputs JSON data representing the updated Cronjob object as returned by the API. This typically includes all current properties of the Cronjob after the update, such as its ID, active status, description, destination details, email, interval, and timeout settings.

No binary data output is involved.

Dependencies

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

Troubleshooting

  • Invalid Cronjob Id: If the provided Cronjob Id does not exist, the API will likely return an error indicating the resource was not found. Verify the ID is correct.
  • Malformed JSON in Destination: The Destination property expects valid JSON. Invalid JSON syntax will cause request failures. Use proper JSON formatting.
  • Invalid Cron Expression: The Interval must be a valid cron expression. Incorrect formats may lead to errors or unexpected scheduling behavior.
  • Authentication Errors: Missing or invalid API credentials will result in authorization failures. Ensure the API key is correctly set up.
  • Timeout Misconfiguration: Setting an excessively low timeout might cause premature job termination; setting it to zero disables timeout.

Links and References

Discussion