Founder here, I’m excited to announce that we've just launched the beta version of ToolJet’s Workflow Automation tool!
For those unfamiliar, ToolJet started its journey when we open-sourced ToolJet (https://github.com/ToolJet/ToolJet) here on HackerNews back in June 2021 (https://news.ycombinator.com/item?id=27421408). When we launched ToolJet, we aimed to bridge the gap between developers and non-developers, making it easier for teams to build internal tools swiftly. Our journey began right here on HackerNews, and much of our evolution has been shaped by feedback from many of you. Today, we’re taking a step further with our new Workflow Automation tool.
How it works
1. Connect your data sources: Add any of the pre-existing ~50 data sources like PGSQL, RestAPI, Zendesk, Stripe, Amazon S3 and many more.
2. Create a workflow: Create a new workflow from your ToolJet Dashboard. A workflow is a series of steps which are executed one after the other, and each step is interacting with a datasource by fetching or putting back data.
3. Business logic: Implement your business logic by creating branches based on conditions and by running JavaScript codes.
4. Debugging: You can see the logs by expanding logs panel at the bottom of the workflow builder. It will have all information you need to debug your workflow.
Documentation: https://docs.tooljet.com/docs/workflows/overview?ref=blog.to...
Availability
Currently, the Workflow Automation beta is available for on self-hosted instances running Business and Enterprise editions.
PS: We haven't open-sourced Workflows.
Windmill is a great product too but it is totally pro-code and building workflow with it, one has to write a lot of code compared to ToolJet. Hence, ToolJet would be definitely faster here.
The issue with low codes tools is that I cannot ask gpt to do stuff for me, and I have the risk that gpt cannot help me as he don't know the tool.
IMHO, real value is when you can extend/customise ToolJet using custom code or database queries. And this is where GPT can help. We even have a inbuilt Copilot for these use cases.
While make.com is focussed just on automation but for all kinds of use cases and not focussed on solving internal tooling problems for the companies.
However, process street does look focussed on building software for internal applications but it is more towards no-code spectrum which has its advantages but makes it less customisable. ToolJet, on the other hand is more customisable and developer friendly because of our low-code approach.
(Windmill Founder here) Our workflow part is open-source so it's not 1:1 comparison
> You can deploy ToolJet on Heroku for free using the one-click-deployment button only until 28th November 2022.
Why the limitation?
For example, if you have a link going to Google somewhere you might put target="_blank" on it.
Otherwise, its use has always been frowned upon because it breaks the back button (it's a new window/tab!), disrupts context (unless that disruption makes sense, like above), and spams the taskbar/tab bar.
Of course it becomes a tangled mess later, but at least they managed to solve a problem.
