Repository navigation
[FR] Automations: External program added as one of the Actions #1192
Replies: 2 comments
|
I've implemented a basic implementation of this in #1251 . Feedback welcome. |
This is implemented. Automations have an External Program action. How to use it
The program runs fire-and-forget, so it does not block the automation, and it combines with the other actions on the same rule. When several rules match one torrent, the last matching rule by sort order picks the program, and one program runs per torrent per cycle. Successes and rejections land in the activity log with the rule name and the torrent. Docs: https://getqui.com/features/automations#external-program On "run on added" and "run on complete" qui polls qBittorrent, it does not subscribe to qBittorrent events, so there is no event trigger. You get the same result from a rule interval plus a condition. Set the rule interval as low as 60 seconds and gate the rule on If you want a true event trigger rather than a short poll, open a separate request for it, since that is a different piece of work. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
At the moment, qBt only allows to run one script on torrent added/finished.
It would be absolutely fantastic, if one of the "Actions" in torrent "Automations" was a dropdown of existing "External Programs":
Justification:
It would allow fine-grained execution of scripts, based on tags, seeding time, categories etc. It would virtually let you to do anything you can imagine - there are many use cases mentioned in Feature Requests, Ideas that could be covered by this simple change. Once more thing that would have to be added was not only run every "X" minutes, but also:
All reactions