n8n in use
n8n for processes that should stay visible: who triggered them, where they stand, why a step failed. Migrations from Zapier or Make are part of it — the trigger is usually the invoice.
Proven by
There is no case study for n8n here. It runs in an application that is not publicly written up.
What that means in practice
I use n8n for processes somebody should be able to follow without me: every run has a trigger, a visible state and the step it failed at. Self-hosted, so the data stays on your own machine. The most common reason to migrate off Zapier or Make is the invoice, the second most common a step nobody there can read afterwards.
Workflows that connect systems
AI Integration in n8n (Claude, GPT)
Migration from Zapier/Make to n8n
Self-Hosted n8n Setup & Maintenance
Other technologies
Next.js
Server-Side Rendering (SSR) & Static Generation
React
React 19 with Server Components
TypeScript
Strict types from the form to the database
Tailwind CSS
Tailwind CSS v4 with CSS Layers
PostgreSQL
Schema design and migrations without downtime
Claude AI
Claude API Integration & Orchestration
Python
FastAPI & Django Backend Development
AI Agents
Autonomous AI Agents with Tool Use
Contact
Half a minute, and you know more.
Half a minute on what I work on and how. If a question is left, write to me — an answer within one working day.
Or write directly:info@damjan-savic.com