How? Is it worth it for you? What works and what doesn't? Looking for inspo

Voice agents are great, and selling them as an agency is a smart play because you can serve multiple industries, but the part I’m loving right now is using voice agents inside an actual product. My latest application - creating a SaaS app for Independent takeaway shops. Most of these owners still run everything on paper. They take phone orders, write them down, cook the food, try to keep the line moving and hope the next call doesn’t go to voicemail. My early feedback from customer testing (actually talking to shop owners) - "We miss calls but we're doing fine" - "This looks great but we're already at capacity on how many orders we can fulfil" - "We don't really miss calls" Sharing here, because sometimes it's a great reminder you can spend months building something slick, but the market decides if it matters. The only way to know is to get outside, walk into shops - or speak to people in your niche and have the uncomfortable conversations. My next steps - speak to more owners find out if this is a "real" market trend or just the results of early feedback. Loom link for anyone curious https://www.loom.com/share/acb2ca1edbb844eb88b656b41b9b722a

Spent 10 months extending different community templates with document processing. Pattern I noticed: Most templates assume humans will read documents and feed information to workflows. Personal assistant? You read and brief it. Marketing agents? You read RFPs and brief them. Support? You read attachments. RAG systems? You manually preprocess documents. Templates handle routing, logic, automation beautifully. But document reading? Still manual. The templates aren't missing features. They're missing eyes. THE UNIVERSAL EXTENSION: Add document processing to ANY template. Workflow reads documents automatically. Humans review instead of transcribe. Simple pattern: Take the step where humans read documents → Replace with automated extraction → Feed to existing template logic. TEMPLATES I'VE EXTENDED: RAG systems + document preprocessing. Marketing agents + RFP processing. Support + attachment analysis. Recruitment + resume scoring. Sales + contract validation. Compliance tracking + audit processing. Project management + spec extraction. Expense tracking + receipt OCR. Onboarding + application intelligence. SAME PATTERN EVERY TIME: Template already has great logic. Just add document reading at input stage. Extract structured data. Feed to existing template logic. Template operates with full context now. Build time: 30-90 minutes per extension. Time saved: 5-20 hours monthly per template. THE REALIZATION: Community templates are 90% complete. They're just missing document vision. The orchestration is perfect. The routing is smart. The agents are brilliant. The workflows are efficient. They just can't read PDFs. Small extensions. Massive capability jumps. MY APPROACH: 1. Identify where humans read documents in workflow 2. Add document processing at that step 3. Extract structured data matching template expectations 4. Feed to existing template logic 5. Template operates with full context now 6. Human reviews results instead of doing data entry Every template becomes 10x more useful when it can read documents independently.

Hi, Tried using 2.0.0 but had a few bugs, so rolled it back to 1.99.0, coming soon is a new version that has a lot of great features. When should I look at upgrading to get the new features. I am hosted on hostinger, what version does n8n cloud run on?

Hi everyone, I need guidance on a production-level way to transfer an entire n8n workflow including credentials and API configurations from my n8n instance (AWS cloud server) to my client’s n8n instance (also cloud hosted). I don’t want to export/import JSON files manually. I’m looking for a reliable method used by professionals to move the full workflow setup—including credentials—directly from one server to another. If anyone has experience with a proper process, your advice would be extremely valuable. Thanks in advance!