3 ms·
I feel that all workflow tools are simply lacking in terms of capabilities. Sure, the base-cases are covered but when it comes to something remotely useful it i
by _pdp_ 5y ago
I feel that all workflow tools are simply lacking in terms of capabilities. Sure, the base-cases are covered but when it comes to something remotely useful it is best to be implemented with real code. That being said, I think there is certainly a need for some low-code tools where your requirement is simply basic automation and service plumbing, as long as it is not mission critical, i.e. take value from system A and put in system B.
For example, do you really want to implement the entire Slack interactive callback workflow for displaying a simple dialog to a user? I guess not. I workflow will do a much better job at that sort of problems.
That being all said, I don't think tines does a particularly good job at this because it simply chains a number of HTTP requests. Some of these APIs require special care and HTTP simply does not cut it.