Introducing the Time Saved node

Tired of _feeling_ the impact of automation but struggling to _prove_ it?

In this video, Angel walks through the *Time Saved* node in n8n, built to help builders and leaders measure automation ROI with a shared, consistent metric.

No more painful spreadsheets, formulas, and manual logging just to answer one question:
_is this automation actually saving time?_

*What you’ll learn*
* Why proving impact (not flashy workflows) is what gets automation into production
* The difference between *execution-level* tracking and *in-workflow* tracking
* When to use *Once for all items* vs *Per item*
* How to track *variable time saved* across different workflow paths
* A practical approach to estimating time saved without overthinking it

*Demo workflow*
* Star Wars API → Google Sheets (plus Time Saved tracking)

*Useful links*
* Time Saved node docs: add link
* Insights docs: add link

*Time stamps*
00:00 – 750 hours saved/month and why impact matters
00:20 – Why most teams can’t measure automation ROI
00:55 – Introducing the Time Saved node
01:00 – Execution-level tracking setup
01:31 – Once for all items vs per item (explained)
03:05 – Variable tracking with branching logic
03:32 – Best practice: start conservative + refine over time
04:01 – Wrap-up

Want to connect?

* LinkedIn: https://www.linkedin.com/in/angelgmenendez/
* X: https://x.com/djangelic

Видео Introducing the Time Saved node канала n8n