What this is
This page explains how to combine reusable templates with node-level decisions.
Why I built this
I built Rune to make automation feel visual and controllable instead of hidden behind technical setup. Teams often know what they want to automate, but they lose momentum when configuration is hard to understand or trust. Rune gives teams a guided workflow builder with clear runs and approvals so automation can be adopted safely.
Who should use this
- Operations teams designing repeatable automated routines.
- Product teams that need visual workflow editing and safe approvals.
- People who want automation without writing technical scripts.
What you can do today
- Start from known templates instead of empty builds.
- Choose node types based on task intent.
- Avoid overbuilding by reusing proven structures.
Quick start
By the end of this page, you will have a clear and repeatable first outcome in Rune Templates and Nodes.
- Pick a template close to your target workflow.
- Inspect each node and keep only required actions.
- Run and refine one node at a time.
Known limits and maturity
- Templates are starting points, not final guarantees.
- Adding too many custom nodes can reduce reliability.
- Document node intent before handing off to teammates.
- Current maturity: active.