n8n-free-templates
A collection of importable n8n workflow files covering AI, vector databases, DevOps and finance chores. It is JSON you import into your own n8n, not a bot.
A collection of importable n8n workflow files covering AI, vector databases, DevOps and finance chores. It is JSON you import into your own n8n, not a bot.
a running n8n, and credentials for whichever services each workflow touches; these are JSON files you import, not software to install
Gathered from the project’s own documentation on 2026-09-13. We have not verified that this list is complete.
No receipt. Our dependency probe acts on a package.json, requirements.txt, pyproject.toml, setup.py, go.mod or go.work at the repository root, and we read no manifest of any kind in this repository. That is a gap in our tooling, not a judgement about this project.
On 2026-09-13 we read this project’s repository metadata, its file tree and its manifest files through the GitHub API, and followed the outbound link far enough to confirm the address resolves — not that what is behind it is what this page says. That is a records check, not an assessment of the software. We have not installed or run this software.
What the words mean here. Last commit is the date of the newest commit on the default branch, not the date of the repository’s last push to any branch. A licence name is GitHub’s own detection, not our reading of the licence file. A version floor is what the named manifest file declares, quoted from that file. A gap in months is printed whenever it is 12 complete months or more. A licence is not a price. It says what you may do with the source; it says nothing about whether the author sells a hosted tier, a paid image or support. Where this page states a cost, that is something we read and dated. Where it states none, we did not look. A version floor we did not find is a claim about a search: we list the project’s whole file tree and match it against the manifest families we read for a floor — package.json, pyproject.toml, go.mod, pom.xml and Dockerfile among them. A manifest family we do not read could still declare one, and a file that pins packages rather than an interpreter, such as a requirements.txt, is not a floor.
We do not republish this project’s own material — its README, code, configuration or assets. The link is where those live. What is on this page is ours: what we found and the date we looked.