Every AI tool wants $20/month and your data. I got tired of that deal.
So I built AgentKit — 5 production-ready AI agents as import-ready n8n workflows that run 100% on your own machine. No cloud. No subscriptions. Your data never leaves your server.
The 5 agents
1. Telegram AI Assistant
Chat with an AI that remembers you. Conversation memory lives in Google Sheets, the brain is Ollama (free, local) or OpenAI. Just message it on Telegram.
2. Content Repurposer
Send /repurpose <topic> on Telegram — get back an X thread, LinkedIn post, Instagram caption, and YouTube title+description+tags. One input, four platforms.
3. Lead Qualifier
Webhook receives a lead — AI scores it 1-10 with reasoning — hot leads (7+) trigger an instant Telegram alert with the details. Cold ones just get logged.
4. Daily Researcher
Fires every morning at 8AM. Pulls RSS feeds, picks the top stories, AI writes a digest (English + Roman Urdu), Telegram delivers it. Wake up informed.
5. Support Bot
FAQ-only customer support. Answers strictly from your knowledge base (Google Sheets) — it cannot hallucinate because it cannot invent.
How it's built (the honest architecture)
- n8n as the orchestration layer (self-hosted, free)
- Ollama for local LLM (free) or OpenAI API if you prefer
- Telegram as the universal interface (free, everyone has it)
- Google Sheets as the zero-setup database
- Every workflow has a CONFIG node — all keys, prompts, and settings in ONE place
- Every workflow has a sticky note with setup instructions right on the canvas
No custom servers. No Docker nightmares. Import JSON — fill CONFIG — hit Active. First agent runs in ~15 minutes.
Free vs paid
The Community Edition is free on GitHub — all 5 workflows, import-ready:
https://github.com/mohsinakramchandia91-bit/AgentKit
There's a $59 commercial version (one-time, client work allowed) — link in the repo README. That's the whole business model: free value first, paid license for professionals.
Try it, break it, tell me
Tested on n8n 2.43.7. If something breaks on import, drop a comment — I'll fix it same day.
Top comments (1)
The CONFIG node pattern is a genuinely nice touch. Too many shared workflows make you hunt through every node to find where the credentials live.
One question: how are you handling Ollama model updates breaking existing prompts in the Support Bot? That knowledge-base-only behavior is exactly where a model swap would bite.
Solid project either way, and the sticky notes on the canvas are the kind of small thing that makes a big difference.