<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hacker News: shivsarthak34</title><link>https://news.ycombinator.com/user?id=shivsarthak34</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Wed, 08 Apr 2026 12:37:28 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=shivsarthak34" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by shivsarthak34 in "[dead]"]]></title><description><![CDATA[
<p>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.<p>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.<p>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.<p>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?</p>
]]></description><pubDate>Sat, 24 Jan 2026 18:12:25 +0000</pubDate><link>https://news.ycombinator.com/item?id=46745978</link><dc:creator>shivsarthak34</dc:creator><comments>https://news.ycombinator.com/item?id=46745978</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=46745978</guid></item><item><title><![CDATA[New comment by shivsarthak34 in "Show HN: I built a scalable visual workflow automation platform – Flowripple"]]></title><description><![CDATA[
<p>Thank you! I'd love to hear what you think of it</p>
]]></description><pubDate>Sun, 18 Jan 2026 16:10:42 +0000</pubDate><link>https://news.ycombinator.com/item?id=46668943</link><dc:creator>shivsarthak34</dc:creator><comments>https://news.ycombinator.com/item?id=46668943</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=46668943</guid></item><item><title><![CDATA[New comment by shivsarthak34 in "Show HN: I built a scalable visual workflow automation platform – Flowripple"]]></title><description><![CDATA[
<p>Landing page is at : <a href="https://flowripple.com" rel="nofollow">https://flowripple.com</a> , HN would not let me post it again because i did a Show HN 6 months back</p>
]]></description><pubDate>Sun, 18 Jan 2026 12:57:35 +0000</pubDate><link>https://news.ycombinator.com/item?id=46667468</link><dc:creator>shivsarthak34</dc:creator><comments>https://news.ycombinator.com/item?id=46667468</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=46667468</guid></item><item><title><![CDATA[New comment by shivsarthak34 in "Show HN: I built a scalable visual workflow automation platform – Flowripple"]]></title><description><![CDATA[
<p>There are just too many things for the same thing eg for  email there's - mailchimp, resend, loops , ofc a simple smtp server</p>
]]></description><pubDate>Sun, 18 Jan 2026 12:55:20 +0000</pubDate><link>https://news.ycombinator.com/item?id=46667451</link><dc:creator>shivsarthak34</dc:creator><comments>https://news.ycombinator.com/item?id=46667451</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=46667451</guid></item><item><title><![CDATA[New comment by shivsarthak34 in "Show HN: I built a scalable visual workflow automation platform – Flowripple"]]></title><description><![CDATA[
<p>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 .</p>
]]></description><pubDate>Sun, 18 Jan 2026 12:53:08 +0000</pubDate><link>https://news.ycombinator.com/item?id=46667438</link><dc:creator>shivsarthak34</dc:creator><comments>https://news.ycombinator.com/item?id=46667438</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=46667438</guid></item><item><title><![CDATA[Show HN: I built a scalable visual workflow automation platform – Flowripple]]></title><description><![CDATA[
<p>Last year I posted about FlowRipple on Show HN (<a href="https://news.ycombinator.com/item?id=43139138">https://news.ycombinator.com/item?id=43139138</a>) when it was just a private beta. Now it's live.<p>Every SaaS ends up hardcoding workflows- payment notifications, onboarding sequences, churn alerts, all scattered across backend code. Every change requires engineering tickets and deployments. As a solo dev, I was stuck maintaining this forever.<p>FlowRipple lets anyone on the team (or me solo) update workflows visually without code changes. SDK triggers from your app (Node.js live, Python soon, or via HTTP request), webhooks, or schedules -> drag and drop builder -> Slack/email/HTTP actions with conditions/delays.<p>I got a lot of questions back then asking how it was similar to n8n or Zapier, which kind of made me question things. I even suspended work on it for about 6 months and focused on my day job. But the need for this focused tool (unlike general solutions like n8n/Zapier) just kept growing.<p>Honestly, I don't know if this will pick up or not. All I know is it solves a real problem for me and I had fun building it. Please do give it a try and let me know your thoughts , i will be building priority integrations for people on pro plan so that they can get more value out of it.</p>
<hr>
<p>Comments URL: <a href="https://news.ycombinator.com/item?id=46667375">https://news.ycombinator.com/item?id=46667375</a></p>
<p>Points: 1</p>
<p># Comments: 6</p>
]]></description><pubDate>Sun, 18 Jan 2026 12:41:51 +0000</pubDate><link>https://docs.flowripple.com/quickstart</link><dc:creator>shivsarthak34</dc:creator><comments>https://news.ycombinator.com/item?id=46667375</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=46667375</guid></item><item><title><![CDATA[New comment by shivsarthak34 in "Show HN: I Built a Visual Workflow Automation Platform – FlowRipple"]]></title><description><![CDATA[
<p>Sveltekit frontend with svelteflow 
Backend is built on a NestJs Stack</p>
]]></description><pubDate>Sun, 23 Feb 2025 08:06:25 +0000</pubDate><link>https://news.ycombinator.com/item?id=43147613</link><dc:creator>shivsarthak34</dc:creator><comments>https://news.ycombinator.com/item?id=43147613</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=43147613</guid></item><item><title><![CDATA[New comment by shivsarthak34 in "Show HN: I Built a Visual Workflow Automation Platform – FlowRipple"]]></title><description><![CDATA[
<p>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.</p>
]]></description><pubDate>Sat, 22 Feb 2025 19:36:13 +0000</pubDate><link>https://news.ycombinator.com/item?id=43142333</link><dc:creator>shivsarthak34</dc:creator><comments>https://news.ycombinator.com/item?id=43142333</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=43142333</guid></item><item><title><![CDATA[New comment by shivsarthak34 in "Show HN: I Built a Visual Workflow Automation Platform – FlowRipple"]]></title><description><![CDATA[
<p>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.</p>
]]></description><pubDate>Sat, 22 Feb 2025 18:09:20 +0000</pubDate><link>https://news.ycombinator.com/item?id=43141459</link><dc:creator>shivsarthak34</dc:creator><comments>https://news.ycombinator.com/item?id=43141459</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=43141459</guid></item><item><title><![CDATA[New comment by shivsarthak34 in "Show HN: I Built a Visual Workflow Automation Platform – FlowRipple"]]></title><description><![CDATA[
<p>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.</p>
]]></description><pubDate>Sat, 22 Feb 2025 18:04:18 +0000</pubDate><link>https://news.ycombinator.com/item?id=43141418</link><dc:creator>shivsarthak34</dc:creator><comments>https://news.ycombinator.com/item?id=43141418</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=43141418</guid></item><item><title><![CDATA[New comment by shivsarthak34 in "Show HN: I Built a Visual Workflow Automation Platform – FlowRipple"]]></title><description><![CDATA[
<p>Thank you so much</p>
]]></description><pubDate>Sat, 22 Feb 2025 17:47:09 +0000</pubDate><link>https://news.ycombinator.com/item?id=43141231</link><dc:creator>shivsarthak34</dc:creator><comments>https://news.ycombinator.com/item?id=43141231</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=43141231</guid></item><item><title><![CDATA[New comment by shivsarthak34 in "Show HN: I Built a Visual Workflow Automation Platform – FlowRipple"]]></title><description><![CDATA[
<p>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</p>
]]></description><pubDate>Sat, 22 Feb 2025 17:46:41 +0000</pubDate><link>https://news.ycombinator.com/item?id=43141230</link><dc:creator>shivsarthak34</dc:creator><comments>https://news.ycombinator.com/item?id=43141230</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=43141230</guid></item><item><title><![CDATA[New comment by shivsarthak34 in "Show HN: I Built a Visual Workflow Automation Platform – FlowRipple"]]></title><description><![CDATA[
<p>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 :)</p>
]]></description><pubDate>Sat, 22 Feb 2025 16:42:05 +0000</pubDate><link>https://news.ycombinator.com/item?id=43140511</link><dc:creator>shivsarthak34</dc:creator><comments>https://news.ycombinator.com/item?id=43140511</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=43140511</guid></item><item><title><![CDATA[New comment by shivsarthak34 in "Show HN: I Built a Visual Workflow Automation Platform – FlowRipple"]]></title><description><![CDATA[
<p>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.</p>
]]></description><pubDate>Sat, 22 Feb 2025 16:33:31 +0000</pubDate><link>https://news.ycombinator.com/item?id=43140440</link><dc:creator>shivsarthak34</dc:creator><comments>https://news.ycombinator.com/item?id=43140440</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=43140440</guid></item><item><title><![CDATA[New comment by shivsarthak34 in "Show HN: I Built a Visual Workflow Automation Platform – FlowRipple"]]></title><description><![CDATA[
<p>Not sure which comundo</p>
]]></description><pubDate>Sat, 22 Feb 2025 16:29:38 +0000</pubDate><link>https://news.ycombinator.com/item?id=43140393</link><dc:creator>shivsarthak34</dc:creator><comments>https://news.ycombinator.com/item?id=43140393</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=43140393</guid></item><item><title><![CDATA[New comment by shivsarthak34 in "Show HN: I Built a Visual Workflow Automation Platform – FlowRipple"]]></title><description><![CDATA[
<p>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.</p>
]]></description><pubDate>Sat, 22 Feb 2025 16:26:51 +0000</pubDate><link>https://news.ycombinator.com/item?id=43140366</link><dc:creator>shivsarthak34</dc:creator><comments>https://news.ycombinator.com/item?id=43140366</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=43140366</guid></item><item><title><![CDATA[New comment by shivsarthak34 in "Show HN: I Built a Visual Workflow Automation Platform – FlowRipple"]]></title><description><![CDATA[
<p>Isn't "new" page actually sorted by time ? Because that's the point of it ..</p>
]]></description><pubDate>Sat, 22 Feb 2025 16:21:11 +0000</pubDate><link>https://news.ycombinator.com/item?id=43140310</link><dc:creator>shivsarthak34</dc:creator><comments>https://news.ycombinator.com/item?id=43140310</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=43140310</guid></item><item><title><![CDATA[New comment by shivsarthak34 in "Show HN: I Built a Visual Workflow Automation Platform – FlowRipple"]]></title><description><![CDATA[
<p>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</p>
]]></description><pubDate>Sat, 22 Feb 2025 16:19:46 +0000</pubDate><link>https://news.ycombinator.com/item?id=43140295</link><dc:creator>shivsarthak34</dc:creator><comments>https://news.ycombinator.com/item?id=43140295</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=43140295</guid></item><item><title><![CDATA[New comment by shivsarthak34 in "Show HN: I Built a Visual Workflow Automation Platform – FlowRipple"]]></title><description><![CDATA[
<p>Which post are we talking about</p>
]]></description><pubDate>Sat, 22 Feb 2025 15:43:32 +0000</pubDate><link>https://news.ycombinator.com/item?id=43139958</link><dc:creator>shivsarthak34</dc:creator><comments>https://news.ycombinator.com/item?id=43139958</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=43139958</guid></item><item><title><![CDATA[New comment by shivsarthak34 in "Show HN: I Built a Visual Workflow Automation Platform – FlowRipple"]]></title><description><![CDATA[
<p>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.</p>
]]></description><pubDate>Sat, 22 Feb 2025 15:36:02 +0000</pubDate><link>https://news.ycombinator.com/item?id=43139890</link><dc:creator>shivsarthak34</dc:creator><comments>https://news.ycombinator.com/item?id=43139890</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=43139890</guid></item></channel></rss>