I switched to n8n after grappling with some limitations in Zapier and Make (formerly Integromat), and it has worked out well for me. Working with IoT in Kenya presents unique challenges, from budget-friendly hardware to unreliable internet connections. Each automation tool has its specific use, but here's why n8n has become my main tool for managing over 2,500 IoT devices.
The cost factor
Running over 2,500 IoT devices is expensive, and every dollar counts when budgets are tight. Zapier's pricing can become very high with thousands of monthly operations. Make offers more generous operation limits, but n8n's self-hosting option was a major improvement for me. It allowed me to control costs tightly while scaling infrastructure as needed. Running n8n on a local server saved us about $200 a month compared to the Zapier plan we would have needed. That might sound small, but it’s significant for a startup in Nairobi. Plus, self-hosting meant I wasn't reliant on consistent internet connectivity to a third-party server, which is essential when your connection is spotty.
Customization freedom
Managing a fleet of IoT devices often requires tailored solutions. I realized this after finding Zapier's structure too rigid. While Zapier has a large library of integrations, it didn’t offer the flexibility I needed. n8n allowed me to script custom nodes into my automation workflows using JavaScript. Once, we needed a custom node to process sensor data differently based on dynamic inputs. I managed it in a weekend with n8n. Here's a small snippet of how I handled some JSON data from my devices:
