https://www.npmjs.com/package/n8n-nodes-selfhosthub Here's the n8n community post announcing the release. https://community.n8n.io/t/community-node-leonardo-ai-generate-image/100800 Next up is a json2video node.

Grateful to share some highlights from November! I dedicated the month to improving my skills in communication, design, and client acquisition. I had the privilege of working with various business owners on brand design projects and served as a personal designer for a social media manager. These experiences have been rewarding, and while I celebrate the small wins, I know there’s more ahead. I’m excited to keep growing, pushing my limits, and helping more businesses thrive!

Hi. I've been coding the SaaS application and I wanted to give an update. Studio Pro is 3 modules; Live, API and Workers. I built it with these goals: - The whole system is a standalone SaaS application built on a robust framework (Studio API) that anyone can use to spin-up their own automation service for themselves or others. That means taking into account installation, maintenance, support, payments, subscriptions, and complying with the various licenses by the apps and AI models that the system could use. It will have workflow management and a database to replace services like airtable and make.com and n8n for the supported workflows. Payments and subscriptions are TBD so stay tuned. - It will be open-sourced using the MIT license so you're free to "...use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software...". - LIVE - The Frontend Layer has to be lightweight, deployable as standalone or in an orchestrator like Kubernetes and be brand-able using templates or custom designs. The front-end is a visual interface to the API which provides the main functionality like signup, creating api keys, storing secrets for other APIs, workflow management, etc. n8n would be at this layer. - API - The API layer has to be multi-tenant (organizations), use modern methods like websockets, webhooks, API Keys and HMAC signatures, granular permissions (video:write, service-account:read), multiple user roles (super-admin, admin, member), accept and issue API calls, queue management for worker tasks, fully tested, worker cluster management, deployable standalone or in an orchestrator, etc. The Postgres database is at this layer. - WORKER - The Worker Layer has to be horizontally scalable, fast to spin-up, highly performant, state-of-the-art features and be rooted in keeping costs to a minimum if not zero$. We have brainstormed some really cool ideas like an airtable/make/n8n migration tool and AI workflow builder, ComfyUI API integration for advanced effects, and much more.

Hello. I've been doing a lot of n8n workflows for myself and others and I have run into two frustrating issues; auto-saving workflows I'm working on and auto-backups of saved workflows. I'm a software developer and site reliability engineer so, naturally, I wrote some apps to handle that. Workflow Auto-Save is a Chrome browser extension. It detects when the Save button is activated on an n8n workflow and based on a time interval you set, it clicks the Save button, automatically. See screenshot for a view of the app. Workflow Auto-Backup is a shell script that detects changes to all your saved workflows. When it detects a change, it creates a backup of the workflow with a timestamp added to the name. They're both available at https://github.com/kickin6/studio-utils. The Workflow Auto-Save Browser Extension has been submitted to the Chrome Web Store for review and hopefully, approval. Cheers

Hello Everyone, As someone who is extremely interested in automation and has zero technical experience, I want someone to help set up automation as a project or part-time job. I mainly want to set everything up on my local n8n on my Synology. After Consulting with Kawika and seeing his amazing work, I was motivated enough to ask for help, as I had tried my best to DIY, but it didn't work. If you are interested, please do let me know, thanks a lot :)