GiteaInstall

Overview

The node provides an administrative operation to trigger a specific cron task on the system. This is useful for automating backend maintenance or scheduled jobs that need to be run on demand rather than waiting for their scheduled time. For example, you might use this node to manually initiate cleanup tasks, data synchronization, or report generation tasks defined in your system's cron scheduler.

Properties

Output

The node outputs JSON data representing the result of the triggered cron task execution. The exact structure depends on the underlying system's response but typically includes status information about the task run, such as success or failure messages, timestamps, and any output generated by the task.

No binary data output is indicated.

Dependencies

• Requires access to the administrative API endpoint that manages cron tasks.
• Needs appropriate API authentication credentials configured in n8n to authorize the request.
• The base URL for the API and authentication details must be set up in the node’s credentials configuration.

Troubleshooting

• Common issues:

  • Invalid or missing task name: Ensure the "Task" property matches a valid cron task identifier configured in the system.
  • Authentication errors: Verify that the API credentials are correctly configured and have sufficient permissions to trigger admin operations.
  • Network or connectivity problems: Confirm that the API endpoint is reachable from the n8n instance.

• Error messages:

  • Unauthorized or forbidden errors indicate credential or permission issues.
  • Not found errors suggest the specified task does not exist.
  • Timeout or connection errors point to network issues or unresponsive API endpoints.

Resolving these usually involves checking the task name spelling, updating credentials, and ensuring network accessibility.

Links and References

• Refer to your system’s API documentation for details on available cron tasks and their expected parameters.
• Consult n8n documentation on setting up API credentials and using HTTP request nodes for similar integrations.