Great question. I only use n8n when it's really needed. Let's break it down step by step, asking yourslef: what stack do you need to connect and who will build and maintain it, as it requires tech skills for debugging, API work, etc? I would use n8n in situations when you have complex conditional logic your crm can't handle; you need to connect tools without native integrations; you're working with non-standard data flows. Situations when you don't have to make it too complex: workflows are straightforward and classic, even lifecycle triggers are manageable by generic crm and automations platforms like zapier or make. However, I think your industry matters too: just consulted a real estate agency that needs n8n because they're connecting MLS feeds, transaction management systems, and custom property DBs that are very complex, and standard marketing automation is not helpful in their case.