Iāve been building a growing number of automations in n8n lately and Iām starting to think more seriously about long-term structure and best practices. Most of what Iām doing is real-world workflow automation: lead intake, enrichment, outbound email, voice agent triggers, scheduling, status updates, logging, etc. Itās working well, but I want to make sure Iām building the right way as things scale. Iād love to hear how more experienced n8n users approach things like: - Managing environment variables across environments - Structuring workflows vs. breaking them into sub-workflows - Inter-workflow communication patterns - Handling retries and preventing duplicate processing - Error handling strategies beyond the default error workflow - Custom execution logging (for example, pushing structured logs into a CRM or database) - Versioning and promoting workflows from dev to production - Performance considerations when automations start to grow - Monitoring client applications Basically: What are the lessons you only learn after running n8n in production for a while? If youāve built larger systems or run client-facing automations, what would you do differently if you were starting over? Appreciate any patterns, pitfalls, or āwish I knew this earlierā advice.