N8N! once you're routing data between clay, enrichment providers, crms, outbound platforms, and internal APIs, the extra control becomes hard to give up.
debugging is cleaner, branching is more flexible, and custom logic doesn't feel like you're fighting the platform.
that said, i don't think it's make vs n8n. i usually recommend make when a team wants to ship fast, and n8n when they're building infrastructure they'll still be maintaining a year from now.