Nodey - Your n8n command center, now on your phone
byβ’
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.
Replies
Hi team,
First question comes to my mind is why we need an apps for this?
Why not just a simple web page?
Because I am already tired with hundreds of apps in my phone.
Thankss
Nodey
@mark_ph_mΒ I understand your reservations about apps... I hate having so many apps on my phone too... but really this is intended as a mobile companion... for when you're out and about and can't pull your computer out. I think it's a useful resource especially if, like me, you spend half of your life starting at an n8n canvas.
What would make this indispensable for me is confidence. If the app can reliably alert me before clients notice failures and help resolve issues within minutes, it becomes much more than a companion app and starts feeling like an operational safety net.
Nodey
@jason_scott8Β You get that with the Live Monitoring feature. Please give it a try! Would love to hear your thoughts :)
@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?
Nodey
@moh_codokiaiΒ Nodey's raw material is the n8n execution record β but that's richer than it sounds, because when an external service fails, its failure signature is captured in the failing node's error output: the 401 from an expired key, the 429 from a rate limit, the timeout from a slow database. So the execution detail view answers the first triage question at a glance β which node died and what the service said β by showing the full node chain with per-node status, timing, and error message. From there, failed executions get a one-tap AI diagnosis, and the Debug Companion chat can take the workflow's JSON and reason about whether the cause is your expression, your credentials, or their outage β and what to check next.
What it won't do... is probe your Postgres or your Stripe account directly: the goal is getting from "something broke" to "it's the Stripe node, 401, rotate the key" in a minute from your phone.