Nodey

Checking the failed execution from the phone instead of opening the laptop is exactly the gap, a brilliantly executed idea.

Good to see Nodey: Your n8n command center, now on your phone ship. Which use case are you seeing the most demand for?

@thefamoushesham n8n users are usually pretty technical and already have dashboards, alerts, and monitoring in place. What made early users install Nodey instead of just relying on the tools they already had?There must have been a specific pain point that kept coming up?

@thefamoushesham One thing I keep thinking about:n8n workflows often connect multiple external services, APIs, databases, and AI models.When something breaks, the root cause is usually somewhere outside n8n itself.How do you approach troubleshooting in those situations? Can Nodey help narrow down where the failure originated, or is it primarily focused on the execution data coming from n8n?

What’s the main use case? If this is a tool for developers, they usually build things on a computer, not on a phone. Why is there such a strong focus on mobile?

Running n8n means workflows break at the worst times, away from a laptop. A command center on my phone to catch a failed execution and re-run it is the obvious missing piece. Can Nodey edit a node mid-flow, or is it monitoring + triggering for now?

Mobile access to n8n workflows is a gap that's been surprisingly underserved. n8n's web UI is powerful but it's not really built for mobile triage. The interesting challenge is maintaining a coherent state view when workflows can be mid-execution. How do you handle real-time execution monitoring on mobile? WebSockets to the n8n instance directly, or does Nodey proxy the state updates?

Interesting idea. Can you actually trigger n8n workflows from the app, or it's just monitoring for now?

Does it show the exact run logs and suggest a fix, or does it just summarize what went wrong?

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?

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.