TMNZ saves 400 hours per month and runs 150,000 monthly workflow executions with n8n agentic AI
TMNZ needed a self-hostable, secure workflow automation platform that non-technical staff could use without heavy training while giving engineers fine-grained control — requirements that Zapier, Make, MuleSoft, and the Microsoft suite could not meet simultaneously.
Zapier and Make could only automate isolated workflows and were heavily limited in scope; MuleSoft and the Microsoft suite were either not self-hostable or cost-prohibitive for a 60-person Fintech.
n8n is now used by more than a third of TMNZ staff, running around 150,000 executions per month and saving 400 hours per month, with AI POCs saving up to an hour per execution; TMNZ is scaling toward one million executions per month.
Show all 5 reported metrics
Frequently asked questions
What did this team achieve with this AI workflow?
n8n is now used by more than a third of TMNZ staff, running around 150,000 executions per month and saving 400 hours per month, with AI POCs saving up to an hour per execution; TMNZ is scaling toward one million execu…
What tools did this team use?
n8n, OpenAI, Azure, PostgreSQL, vector stores, Open WebUI.
What results were reported?
Monthly workflow executions: around 150,000; Monthly hours saved: 400 hours; time saved per AI POC execution: up to an hour; Staff adoption: more than a third of TMNZ staff (source-reported, not independently verified).
What failed first in this deployment?
Zapier and Make could only automate isolated workflows and were heavily limited in scope; MuleSoft and the Microsoft suite were either not self-hostable or cost-prohibitive for a 60-person Fintech.
How is this invoice processing AI workflow structured?
Staff submits automation request → LLM models execute agentic tasks → MCP servers extend agent capabilities → Results delivered via Open WebUI → Results drive continuous improvement.