shivsarthak34

I'm the founding engineer at Spur, and I think we've all written the same bad code. You want to email a user when they sign up, and then check 24 hours later if they created a project. It starts simple, but eventually, you end up with a mess of cron jobs and spaghetti logic.

The breaking point for me wasn't the code complexity, but the process. Every time our marketing team wanted to change an email subject or bump a delay from 1 day to 2 days, I had to stop what I was doing, write code, and push a deployment. It felt ridiculous to deploy a new build just to change a timer.

I ended up ripping about 400 lines of boilerplate state-management code out of our backend. I moved all that logic to an orchestration layer instead (I built a tool called Flowripple for this). Now my backend just fires a 'user_signed_up' event and forgets about it. The orchestration layer handles the state, the delays, and the retries by a visual workflow builder on flowripple.

It has mostly solved the "separation of concerns" headache for us, but I'm curious how you all handle complex onboarding flows? Do you stick with Cron/Queues to keep it simple, or do you offload the state management elsewhere?

Thank you! I'd love to hear what you think of it

Landing page is at : https://flowripple.com , HN would not let me post it again because i did a Show HN 6 months back

There are just too many things for the same thing eg for email there's - mailchimp, resend, loops , ofc a simple smtp server

For now it's using my email server, but i am open to add a smtp email integration to send it via user's service , i was conflicted which one should i integrate and just solved my problem for now and thought of thinking at scale later when i actually make it public .

Sveltekit frontend with svelteflow Backend is built on a NestJs Stack

It's not a reskin , I developed it on my own. It's just that these workflow builders are built using libraries such as React Flows. As you can see in the bottom right of the sheet of the flow builder. Also my application is built on Svelte, and I'm using Svelte Flow which is a fork of React Flow itself.

Yep , it seems to be a much mature product, they are have much more integrations going on. FlowRipple is at a very nascent stage and very much figuring out it's path. I've put together this project in a month along with my full time day job, so the motive to showcase it here was to just get some eyes and opinions on it.

Maybe a vision for this product could be to be that "Sandbox Environment" with the LLM. So you just connect your backend and triggers and just create flows telling what needs to be done in natural language (one time setup) and it creates the flow.

Thank you so much

Yeah , documentation is still a WIP. i'll remove the link for now because the project will go undergo a lot of changes. And iterating over a list is currently not implemented , but I can add support for it soon. Thanks for mentioning , really appreciate it

Hahah no but I remember trying to figure how Node-RED works at least 10 years back on my RaspberryPi. I work at a company called Spur, which is a Whatsapp Marketing Software, we have a workflow automation interface there, which is used to create chatbots. On weekends I was just experimenting on some different framework libraries on which we can rebuild our workflow builder. Stumbled across SvelteFlow and tried it out, one month later here we are :)

I agree , a brief explainer/demo video does a lot of convincing. Would you mind explaining your usecase ? I'd love to know if something can be accommodated in flowripple.

Not sure which comundo

This is a very interesting take. It currently cannot be exported but It sure can be achieved. Wow i think this is something i'll prioritise to implement. Thank you so much for the insight, it can be a good differentiator too.

Isn't "new" page actually sorted by time ? Because that's the point of it ..

The vision is to be a workflow automation SaaS for other Product Backends, the trigger management and the reusability can be a differentiator for now but, this was more of a side project i did to offload some tasks i had to do on my day job. I replaced the firing of webhooks or sending of slack notifications on certain events. That being said , the app is still under development and I wanted to understand more about what people actually want, thats why i rolled out an early access program to bring out features and integrations that more people want

Which post are we talking about

I feel it's too much dials and knobs thing which can scare away the non technical team members. I personally feel n8n is a great product , but for my non technical coworkers it's hard to navigate or keep track of.

Ahah thank you i skipped that part trying not to make the video too long, Also it is easy to setup a trigger too , I've added option to either manually paste the payload that your backend will send , or actually make a live request and it will automatically detect and create a trigger for you . Mapping variables too are just one click setup, just click on the property you want to map as a variable and done , you can use them in workflows.

Also yes i'll try to accommodate all these things in future iterations of the website. thank you for the comment tho , really appreciate it

As of now we're still very early to say this is our Moat or differentiator, but i just wanted to develop a tool which takes minimal effort to integrate on the backend and is easy to be used among teams members without much technical knowledge.

Noted i'll update the website mentioning more about the features, and yes n8n.io is a similar product , i personally feel it's too technical and hands on, and havent tried Azure. About differentiators i'm still kinda on the lookout to find some, to double down on, that's why went ahead with the early access, to listen to feedback and implement what people actually want, rather than building something broad which people don't want. Thanks for the comment tho , really appreciated