Resources · n8n integration

n8n Track Time Saved nodeConfigure Track Time Saved in n8n.

Automation only gets funded when someone can put a number on it. The n8n Track Time Saved node turns each run into minutes saved, based on the path the workflow took and how many items it processed. Two parameters, version 1, nothing to install and no account to connect.

Try the Track Time Saved node on n8nSee the 2 parameters

Verified Trustpilot reviews · AI, automation & growth agency

Why automate

What does the n8n Track Time Saved node actually measure?

Track Time Saved records how many minutes a workflow execution gave back to the people who used to do that job by hand. The value is not guessed by n8n: you state it, and the node counts it once for the whole run or multiplies it by the number of items that reached it. Because it sits inside the workflow, the count follows the execution path, so a run that stopped early does not claim the same saving as a run that went all the way through.

Take a nightly export that pushes new orders into a spreadsheet. A Schedule Trigger starts the run, the rows land in Google Sheets, and Track Time Saved sits right after with Per Item selected. Five orders on a quiet night, forty on a busy one, and the number reported reflects that difference without anyone touching the workflow.

A support triage run works the other way. One execution reads the inbox, sorts the tickets, and drops a digest into Slack. The saving is the meeting that no longer happens, not a per ticket saving, so Once For All Items is the honest setting. Same node, opposite mode, and the difference is a deliberate choice rather than a default nobody reviewed.

Branching is where the node earns its place. Put an If node in front of it and give each branch its own Track Time Saved with its own Minutes Saved value. The happy path that auto approves a request claims more minutes than the branch that only flags it for a human. Nothing is averaged, because only the branch that ran contributed its number.

Prefer a different approach when the number you want is not a saving. Storing a duration, a cost or a run identifier in your own data is a job for a field, not for this node, and Track Time Saved will not read a value out of your items on its own. It also has no opinion on how long the manual task really took: the minutes come from you, so agree on them with the team that used to do the work, and write them down somewhere before they drift.

Two limits are worth knowing before it goes into production. The node does not start a workflow, so something has to run before it, and it does not store history by itself: a run counts minutes, and it is up to the following nodes to keep that number. Version 1 is the only version there is, which means a workflow you built last year shows the same two parameters as one you build today. If you want a second opinion on where this fits in a wider setup, the n8n review covers how the platform handles reporting around workflows.

Parameters

How do the two parameters work?

The Track Time Saved node has 2 parameters. For each one: the node as you configure it in n8n, what the parameter changes, and our field notes.

01

Calculation Mode

mode

What you see in n8n

Notes & use cases

Calculation Mode decides whether one execution reports a single saving or one saving per item that reached the node. Pick it from how the manual work used to be done, not from the shape of the data.

Key parameters

  • Calculation Mode: two choices, once (Once For All Items) and perItem (Per Item).
  • Once For All Items: counts minutes saved once for all input items, whatever number of items arrive.
  • Per Item: multiplies minutes saved by the number of input items, so the total moves with the volume of the run.
Use cases
a weekly report assembled in one pass is a Once For All Items job, while a loop that renames every incoming file is a Per Item job.
02

Minutes Saved

minutesSaved

What you see in n8n

Notes & use cases

Minutes Saved is the number of minutes saved by this workflow execution, and it is the only figure the node takes from you. It is a plain number field, so it accepts a fixed value or an expression.

Key parameters

  • Minutes Saved: a number, typically a small fixed value such as 3 per invoice, or an expression like {{ $json.minutes }} when an earlier node already carries the estimate, meaning n8n reads the field from the incoming item.
Use cases
a document that took six minutes to file by hand gets 6 here, and the same workflow can carry different values on different branches. Keep the figure conservative: it lands in front of whoever signs off on the next automation.
Need help

Need help automating Track Time Saved with n8n?

A person reads every message.

FAQ

Track Time Saved in n8n, answered

01Is the n8n Track Time Saved node free on Cloud and self-hosted?
Yes. Track Time Saved is a core node, shipped with n8n, so there is nothing to install and no extra cost for the node itself. It behaves the same on n8n Cloud, the hosted offer run by n8n, and on an instance you host yourself with Docker or npm under the Community Edition and its Sustainable Use license. A workflow built in one place runs identically in the other, so a team that starts on Cloud and later moves to its own server keeps the same two parameters and the same counts. The only thing that changes between those setups is who operates the instance.
02What credentials does Track Time Saved need?
None. There is no credential to create and no Authentication selector on this node, so there is nothing to set up on any account before using it. That is unusual for an n8n node and it is a real advantage: you drop it into a workflow and it runs. The values it uses come from the panel and from the items already flowing through the workflow, not from an external service. If a step further down writes the result somewhere, that destination has its own credential, but the counting itself stays local to the execution and asks nothing of you.
03What are the limits of the Track Time Saved node?
It counts, and that is all it does. It will not start a workflow on its own, so a trigger has to come first, whether that is a Schedule Trigger, a Webhook or the trigger of a tool. It does not decide how many minutes a task is worth either: that figure comes from Minutes Saved, so the quality of the reporting depends on how honestly the team fills it in. The node runs on each incoming item unless Once For All Items says otherwise, and version 1 is the maximum version in the catalog, which means the panel shows the same two parameters everywhere.
04When do you use Track Time Saved rather than a plain field?
Use it when the number has to follow the execution path. A field you set by hand carries whatever value you typed, on every run, in every branch. Track Time Saved is built around the path taken and the number of items processed, so a branch that did less work reports less, and a run with a single item does not claim the same total as a run with forty. Reach for a field instead when you simply need to move a value along with your data. The two are not rivals: one records a saving, the other stores a value.
05n8n or Make for tracking time saved?
It depends on what you need to control. Make is a hosted automation platform with no self-hosting option, billed per operation, and its visual logic suits teams that want nothing to run on their own machines. n8n can be self-hosted with Docker or npm, or used on n8n Cloud, which matters when the data passing through the workflow should stay on your side. On cost, the models differ in shape: one charges per operation, the other depends on how you host. Pick on hosting, data control, cost model and how comfortable your team is with each visual editor.
Hack'celeration Lab

Get our weekly integration tips.

No spam. Unsubscribe anytime.

Same platform

Other docs you might need on this stack.

Browse all integrations