Best Solution to Automate Workflows
I definitely need advice.
Im beginning to automate workflows in businesses (connecting APIs with an LLM on top) Im about to start developing for clients.
I had always used make .com before because it’s easy to connect APIs together.
But now I’ve gotten pretty decent at using WASP & React and I feel like that can be more flexible than something low code.
Also something lacking with make is the ability to create a dashboard if I need the user to click a button or type some input to start the workflow automation.
Can I use WASP in an away where I can run API requests in a chain at scheduled times and create multiple dashboards with it ?
Or better yet should I combo WASP with make?
WASP can be used to make the dashboards?
Or I guess WASP makes CRON jobs pretty easy and this is the way?
Also note: the goal is create these workflow automations quick and lower cost (let’s say $20k on avg per project) (right now if I’m building it out that doesn’t matter but when we hire team on it will)
Haha just want advice 🙏
4 Replies
Hi @Jacob Ferrari. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
Yes, you can definitely use Wasp for automating workflows and creating dashboards. Wasp is a powerful tool for building full-stack web apps, and it's particularly well-suited for quickly starting a web app with industry best practices source (https://wasp-lang.dev/docs#when-to-use-wasp).
Wasp supports background jobs that can help you with automating workflows. These jobs persist between server restarts, can be retried if they fail, can be delayed until a future time, and can have a recurring schedule source (https://wasp-lang.dev/docs/advanced/jobs). This feature can be used to run API requests in a chain at scheduled times.
As for creating dashboards, Wasp is built to be used alongside modern web dev stack (currently supported React and Node), which means you can leverage the power of these technologies to create interactive and dynamic dashboards.
However, Wasp is not designed to be a no-code solution or a solve-it-all tool in a single language. If you find that make.com provides certain features or ease of use that you can't achieve with Wasp, it might be worth considering a combination of the two. You could use Wasp for the parts of your project that require more flexibility and customizability, and make.com for the parts that can be easily automated with a low-code solution.
As for CRON jobs, there was a closed Github issue suggesting the addition of support for cron/scheduled jobs in Wasp source (https://github.com/wasp-lang/wasp/issues/200). However, it seems the issue was closed in favor of tracking the work in another issue. This suggests that while cron jobs might not be directly supported by Wasp at the moment, it's a feature that might be added in the future.
In conclusion, Wasp can be a powerful tool for your needs, but it might not be able to replace all the features of a low-code solution like make.com. A combination of the two might be the best approach, depending on the specific requirements of your projects.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @Jacob Ferrari, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist:
Perhaps try again in 15mins?
@Jacob Ferrari that is quite abit of questions, but I will try to answer at least some of them!
So yeah, you can certainly build dashboards, with React.
You call extenral APIs, so you should be able to call stuff you make with make.com if it exposes an external API (and very likely it does).
You can use Wasp Jobs to run your JS code at a scheduled time, whatever that JS code might be doing. And yes, that JS could be calling external APIs if you wish.
So I believe the answer is yes to all, but to your question of how fast that will be for you to produce, that is harder to say, maybe once you get your first project going it will be much eaiser to reuse it, sinc eyou will have ready code to reuse for all this stuff.
@martinsos awesome thank you! Im just trying to figure out the best tools to use for this relatively new and expanding field!
That is great, happy if I can help :)!