Hey Product Hunt 👋 What inspired it: every team I've worked with has the same backlog of "tell us when this happens" requests: • Billing: "ping us when a card is declined, but not three times for one invoice" • Customer success: "open a ticket when a trial ends in 3 days and never activated" • Lifecycle: "send Braze an event so the rescue campaign starts" The data is already in the database. But each request becomes application code, a deploy, and a wait behind the roadmap, so most never get built. How the approach evolved: 1. It started as "watch a table, post to Slack". That broke on the first real request: "a trial that never activated" isn't a new row, it's a condition. So an event became a SQL query you define, with joins, aggregates, and even things that didn't happen. 2. The first thing every team asked was "how many messages will this send?" Nobody wants to flood #sales or open 200 duplicate tickets. So backtesting became the core: replay a rule over history before it goes live. In the demo, 211 declined charges become 92 messages, and 119 duplicates are never sent. 3. Then it was split by who knows what. Engineering writes the query once; billing, support or lifecycle decide how often it fires and where it goes, with no ticket in between. It only reads from your database, runs in shadow mode until you promote a rule, and is open source and self-hosted. Try it without signing up: https://demo.rowfire.com I'd love to hear: what's the first automation you'd build, and what's missing before you'd point it at your own database?

Rowfire

Turn database events into Slack, Zendesk & Braze actions

Turn database events into Slack, Zendesk & Braze actions