Launching today

Flowripple

Launching today

Easily Trigger workflows from your SaaS

71 followers

Easily Trigger workflows from your SaaS

71 followers

Visit website

Automation tools

•

AI Workflow Automation

Automate your SaaS workflows with minimal code. Visual workflow builder that lets your whole team manage triggers, integrations, and automations without code deploys.

Free Options

Launch tags:Productivity•SaaS•No-Code

Launch Team / Built With

Framer — Launch websites with enterprise needs at startup speeds.

Launch websites with enterprise needs at startup speeds.

Promoted

Flowripple

Maker

📌

At my startup, we were hardcoding every lifecycle event such as user onboarding sequences, subscription renewals/cancellations, payment failure retries etc. The technical debt was piling up, we had to create complex background jobs to manage long-running delays (e.g., "Wait 3 days, then check X"). If a user didn't get an email, we were digging through massive application logs to find out where the logic branched off or if every time marketing wanted to change a delay from 24 to 48 hours, or edit a subject line, it required a PR and a full code deployment. The Solution: Decoupling via Event-Driven Orchestration which I ended up naming Flowripple I realized these flows shouldn't live in the core business logic. I moved the logic out of the app and into an orchestration service. Deleted 400+ lines of boilerplate and Separation of Concerns: The backend handles the database; the visual workflow builder handles the "if/then/wait" logic. Non-Eng Autonomy: The success team can now adjust delays or email copy in a UI without asking for a code push. Retries & Observability: We get a visual trace of every user's path through the flow, which makes debugging instant. I ended up building this into a tool called Flowripple because I couldn't find a lightweight way to do this without the overhead of massive enterprise tools.

Report

1d ago

Copus

The non-eng autonomy angle is what stands out here. Every SaaS team I have seen has this exact pain where marketing or success wants to tweak a delay or change an email subject line and it turns into a full engineering ticket. Making that a visual workflow change instead of a PR is a huge unlock. Curious how you handle versioning when a flow gets updated mid execution. Does a user who started on v1 finish on v1, or get switched to v2?

Report

8h ago

Flowripple

Maker

@handuo Right now , the execution will be switched to v2 (except for delay steps), but a proper ability to drafts and versioning will be added soon.

Report

7h ago

This resonates hard. I've dealt with the exact same pain -- hardcoding onboarding sequences and payment retry logic that should never live in the core app. The 400 lines of boilerplate you deleted is such a relatable number. The visual trace for debugging user paths is a killer feature too. When something breaks in a background job at 2am, having a clear visual of where the flow diverged saves hours. How does integration work on the SaaS side -- is it a webhook-based trigger system, or do you provide an SDK that fires events directly?

Report

10m ago