Open StefanRichterHuber opened 10 months ago
We will think about it, currently Nextcloud Flows is so slow(we tested them half year ago)
But the idea is good, we have the same situation with what we want to do, and we should find a way to solve this.
Can you please elaborate what you mean by 'slow'? Since this would be an important feature for me, I would like to understand the issue. There is already an flow app for webhooks which is currently in use by me to implement my solution. But I would like to see to use app api without external dependencies, especially to have a unified user experience, once the app is published.
Describe why it is important and where it will be useful
ExApps seem to be an excellent backend for further automations using the already established Nextcloud flows.
Describe your proposed solution
Add another API like the one for the File Actions Menu which lets the ExApp register itself as target for Nextcloud flows. Protocol and Payload could be almost identical to the one of the File Actions Menu.
Describe alternatives you've considered, if relevant
Alternatively the ExApp would have to constantly search for changed files matching the criteria of the flow, generating unnecessary load on both Nextcloud service as well as the Ex App (and its host) itself. This is a major unnecessary performance issue.
Additional context
No response