01Extraction
Receipt capture bot
Staff forward or photograph a receipt; the workflow reads it, pulls vendor, date, total and tax, and files a clean row in the finance sheet with the image attached.
n8nOCR + LLMGoogle SheetsTelegram
AI & Automation · n8n
I build n8n workflows that run your busywork.
Every business has work that eats hours and creates nothing: filing receipts, retyping data between systems, assembling the same documents, answering the same question twenty times a week. I rebuild those tasks as automated workflows using n8n — wired to the tools you already pay for, priced fixed, and handed over so your staff can run them without me.
Best for
Owners and managers with a team drowning in admin
Built with
n8n, OpenAI / Claude, Google Workspace
Workflows shipped
5 production builds
Pricing
Fixed price per workflow, quoted after mapping
Handover
You own the workflows and the credentials
Services — what I offer
Workflow builds
01A specific repetitive process, mapped and rebuilt as an n8n workflow that runs on a trigger or a schedule.
—Process mapping before any building starts
—n8n build on your cloud or self-hosted instance
—Integration with Sheets, Drive, Telegram, email, CRMs
—Error handling, retries, and failure alerts
—Documented handover so your team can edit it
AI agent automations
02Workflows where a model does the judgement work — reading, extracting, drafting, answering — inside a pipeline you control.
—Document and receipt extraction into structured data
—Retrieval-based Q&A over your own documents
—Drafting and content generation on brand
—Prompt and output validation so results stay predictable
—Human-in-the-loop approval steps where they matter
Work — five workflows I've built
02Content
Branded post builder
A short brief goes in, an on-brand social post comes out — caption, hashtags, and a generated image sized per platform, queued for approval before it publishes.
n8nLLMImage genDrive
03Documents
Document package generator
One intake form fills a whole set of documents — contracts, cover sheets, checklists — merged from templates and delivered as a single PDF package to the right folder.
n8nDocs APIPDF mergeDrive
04AI agent
Compliance Q&A chatbot
A chatbot answering questions against the client's own standards and internal documents, citing the section it came from instead of guessing.
n8nVector storeLLMChat widget
05Field ops
Field report automation
Photos and notes submitted from site get sorted, captioned, and assembled into a formatted report that lands in the project folder before the tech is back in the truck.
n8nFormsLLMDocs
Process — how it goes
01Map
We walk through the process as it actually runs today — the clicks, the exceptions, the person who fixes things quietly. That map is the spec.
Process map + scope
02Build
I build the workflow in n8n against real data, not happy-path samples, with error handling and alerts wired in from the start.
Working workflow
03Ship
We run it live on your instance, with credentials in your accounts, and I document how each node works and what to do when something fails.
Live + documented
04Tune
Two weeks of watching the real runs, tightening prompts, and handling the edge cases that only appear in production.
Stable handover
FAQ
No. If you don't have one, I'll set it up with you as part of the build — either an n8n Cloud workspace or a self-hosted instance on your own server. Either way it lives in your account, not mine.
Cloud if you want it running today and don't want to maintain a server; it's the right default for most small teams. Self-hosted if your data can't leave your infrastructure, you need unlimited executions, or you're integrating with internal systems that aren't on the public internet.
That's most of what I build. Generating packages from templates, extracting data out of scanned or photographed documents, assembling reports from field input, and answering questions against a document set are all things I've shipped.
Fixed price per workflow, quoted after the mapping call, so you know the cost before I start building. Bigger engagements get broken into workflows and quoted the same way. Optional monthly support if you want me watching the runs after handover.
You do. The workflows run on your instance under your credentials, the JSON is yours to export, and the handover doc explains every node so your team — or another developer — can change it without me.
Contact
Tell me the task nobody wants to do.
If it happens the same way more than a few times a week, it's probably a workflow. Describe the process and I'll tell you honestly whether it's worth automating — and roughly what it would cost — before you commit to anything.
Typical response
Within one business day
Good first message
The process, how often it runs, and the tools it touches.
Also available for