Siilo turns an automation request into a mapped process and a build-ready handoff pack, with the Power Platform licence check done before anyone starts building. Name the real Power Automate action on every step, across 130+ connectors, or import existing flows. Made for in-house Microsoft 365 automators.

Hey Product Hunt 👋 I work in Power Platform, and the same thing kept happening. Someone asks for "a flow that sorts out the invoices". Three weeks later we find out it needs a premium connector nobody budgeted for, half the branches were never discussed, and whoever is building it is reverse-engineering a Teams thread to work out what was actually agreed. The mapping was never the hard part. The handover was. So I built Siilo. You keep the request exactly as it arrived, map it on a canvas, trigger, actions, branches, approvals, who owns each step and Siilo does the bits everyone skips: 🔌 Names the real action. Every step carries its actual Power Automate connector and operation SharePoint > Get items, Approvals > Start and wait for an approval, picked from 130+ connectors and around 1,700 triggers and actions. Not "it'll do something in SharePoint". 🚦 Checks it can be built. Premium connectors, DLP groupings and run-as identity, flagged while you are still mapping. Finding out a flow needs a premium licence costs nothing on a Tuesday afternoon and quite a lot on build day. 📦 Writes the spec. An eleven-section handoff pack generated from the map: summary, triggers, step detail, decision rules, exceptions, permissions, identity and licensing, tests and acceptance criteria. PDF, Word, Markdown or JSON. ⤓ Imports what you have already built. Drop a Power Automate .zip export in and it draws the map for you conditions, approvals, error handling, every connector. The file is read in your browser; the connection that ran it and anything secret-shaped never leave your machine. Free is one project with every feature, no card. Pro is £9.99/month for unlimited projects. Two honest caveats. It is a desktop tool, the canvas wants a mouse and room to draw, so phones get a polite "open this on a laptop". And it is Power Platform-first: the mapping works for anything, but the licence check is Microsoft-specific. If you have ever been handed a half-specified automation request: what was missing? What would you want checked before a build starts? That is the bit I most want to get right.

Calling this "build-ready" pack is just nice branding for polite wall to stop non technical team sending automations in Slack DMs. Saving one dev from that back and forth pays for it.

@konstantin_tikhaev Haha, honestly that’s a pretty fair way to put it 😄 A big part of the idea behind Siilo is exactly that, giving non-technical teams a clearer way to hand over automation requests without dragging developers into endless Slack back-and-forth. If it saves even a few of those conversations, it’s doing its job. Really appreciate you seeing the value in it 🙌

Calling this "build-ready" pack is just nice branding for polite wall to stop non technical team sending automations in Slack DMs. Saving one dev from that back and forth pays for it.

Siilo

Turn automation requests into build-ready handoff packs

Turn automation requests into build-ready handoff packs