Hello, I can help you connect your current amoCRM setup with n8n in a clean, scalable, and practical way so that lead management and sales processes run automatically across your stack. I already understand the key goal of this project: build a reliable foundation first, using the tools you already work with, and design it in a way that can later be expanded to other departments. What I can deliver A clear comparison between amoCRM native automation and n8n-based orchestration, including: strengths and weaknesses of each approach where native automation is enough where n8n adds real value common hidden pitfalls and maintenance risks A draft integration architecture showing how leads move between amoCRM and the rest of your stack A step-by-step n8n workflow design for: capturing new leads lead scoring conditional routing updating deal stages syncing contact data back to amoCRM automatically A proof of concept in a self-hosted n8n environment using test data, including: one working trigger conditional logic branch outbound update back into amoCRM Clean deliverables for handover: exported JSON workflow architecture diagram short walkthrough video setup notes so your team can reproduce and extend the flow independently My approach I focus on workflows that are: easy to maintain clearly named secure in credential handling reusable for future departments and automations I also pay attention to practical issues that often get missed in these integrations, such as: duplicate lead creation webhook loops stage update conflicts field mapping inconsistencies retry/error handling token/credential expiry safe testing before production deployment Relevant experience / perspective I’m familiar with CRM automation logic and with building integration flows where the CRM remains the operational center, while the automation layer handles routing, enrichment, synchronization, and task execution. From similar automation ecosystems like Make / Zapier / webhook-driven CRM flows, one important lesson is this: the best long-term setup is usually to keep business logic centralized in one orchestration layer instead of splitting logic across too many platforms. That is exactly why n8n can be a strong choice when you want more control, transparency, and future scalability. About the result The goal will be to give you not only a working POC, but also a structure your team can understand and safely build on later. If selected, I can prepare the workflow in a way that imports cleanly into your n8n self-hosted instance and is ready for testing on your side. Best regards