Nodey is a mobile companion for n8n. Monitor your workflows in real time, diagnose failed executions with AI, build workflows from a prompt, and trigger automations with NFC tags or geofenced locations — all from your phone.
Hey Product Hunt — I’m Hesham, the maker of Nodey 👋
I built Nodey because I kept running into a simple problem: n8n is incredibly powerful, but when something breaks, checking on it from your phone is still awkward. If you’re away from your laptop, on-call, traveling, or just trying to keep an eye on automations during the day, there isn’t a great native mobile command center for n8n.
Nodey is my attempt to fix that.
It lets you monitor n8n executions, inspect recent errors, use AI to understand and debug workflows, back up workflows into an encrypted on-device vault, and trigger automations using mobile-native actions like NFC tags, geofences, widgets, and push notifications.
The homepage includes an interactive app mockup, not just screenshots — you can actually click around and get a feel for how the app works before installing it.
A few things I’d especially love feedback on:
1. Does the positioning make sense if you already use n8n?
2. Which feature feels most useful: monitoring, AI debugging, vault/backups, NFC/geofencing, or widgets?
3. What would make this a must-have for your n8n setup?
We’re preparing for an early June launch on iOS and Android, and we’ll be opening a limited number of founding member slots at launch.
Would genuinely love your feedback, questions, and feature requests.
Report
The on-call angle is the real pitch here. I run WhatsApp bots for small businesses and failures never happen when I'm at the desk - it's always a webhook dying on a Saturday. Checking the failed execution from the phone instead of opening the laptop is exactly the gap. Question: when the AI diagnoses a failed execution, does it point to the specific node and param, or is it more a plain-language summary?
Replies
Nodey
The on-call angle is the real pitch here. I run WhatsApp bots for small businesses and failures never happen when I'm at the desk - it's always a webhook dying on a Saturday. Checking the failed execution from the phone instead of opening the laptop is exactly the gap. Question: when the AI diagnoses a failed execution, does it point to the specific node and param, or is it more a plain-language summary?