Nodey - Your n8n command center, now on your phone

@thefamoushesham congrats on the launch Hesham. Quick diagnose and resolve sounds like a winner.

@david_marko Yes, I think part of the reason why I developed this app is because of the back pain I was getting sitting so long in front of my computer. To answer your question... in the tests I've done, yes, it will point to the failure node but the response is usually provided in the format of long form text, which I now realise might not be the most convenient when people really want a quick look at their phones.

I've made a note of that for the next update... should be an easy JSON schema fix.

Thank you so much!

@thamibenjelloun It actually does. It will absolutely suggest a fix and will provide JSON that you can export with the tap of a button to your n8n instance. It will also pinpoint the failure node but the response is usually provided in the format of long form text, which I now realise might not be the most convenient when people really want a quick look at their phones. I've made a note of that for the next update... should be an easy JSON schema fix.

Thank you so much!

@dhiraj_patel5 ABSOLUTELY! This was one of the features I wouldn't compromise on. I tested a few other apps that did the same thing on iOS and Android and I was always so confused when they didn't have this basic feature. With Nodey, you can trigger any workflow you want within the app, we have widgets that allow you to trigger workflows from your homescreen, you can trigger workflows when you arrive or leave a location, and through NFC tags by waving an NFC tag across your phone!

@natalia_iankovych I think mainly it's because building and operating tend to come with different issues. You'll still have to build workflows at a desk, but workflows run 24/7 and it's unrealistic to expect to developers to remain at their desk on standby. Nodey allows you to handle the triage by sending a failure notification, telling you what node failed, allowing you to retry the workflow, deactivate so you don't keep burning through tokens and credits... or rebuild and optimise it using our AI tools. There is also a use case in that sometimes you want your workflows to be linked to the real physical world... for example, I've been using the location trigger feature to trigger workflows when I leave my home for the office. It's useful when you have workflows that are tied to physical locations.

And, in the case of manual trigger workflows that don't run on a schedule, you can still fire them from your phone without getting yourself on a desk.

There is also the Workflow Vault (which allows you to store your workflows and restore them to any n8n instance (useful if managing clients' instances)) and the AI Workflow Builder that builds the JSON for you and exports it directly to your n8n instance.

@kripanshu_shekhar Thank you — really appreciate it and let me know if there are any features you'd like added.

@anand_thakkar1 Neither, actually — Nodey talks straight to your instance with no middleman, but over REST polling rather than WebSockets. As far as everything that we've tried indicates, n8n's push channel (/rest/push) is internal-only — cookie-authenticated for the editor UI and unstable across versions — so the public API (/api/v1) effectively mandates polling for third-party clients. While an execution is live, Nodey polls it on a tight interval (5s default, remotely tunable so I can throttle fleet-wide if needed), then drops to iOS background refresh plus refetch-on-foreground otherwise — the instance stays the single source of truth, so the app never trusts a stale local view. And deliberately no proxy: your API key and execution payloads never touch any server of mine.

@oleksii_sekundant  The catch-and-re-run loop is exactly what's built: background polling flags the failed run, you get a notification, open the execution to see which node errored with its output, and retry (or stop/delete) it right there — plus toggle workflows and fire webhook triggers manually, via NFC tag, or by geofence. Node-level editing isn't in yet, and that's somewhat deliberate: the public n8n API has no granular node PATCH (you'd replace the whole workflow JSON), and an in-flight execution runs the version it loaded at start anyway — so "mid-flow edits" can't rescue a running execution even in theory. Where Nodey goes past pure monitoring is creation: the AI builder drafts complete workflows from a prompt and pushes them to your instance, and a debug companion reasons through why a node failed. Editing the canvas is the one thing n8n's web UI proves doesn't shrink to a phone — if I add it, it'll be parameter tweaks on a single node, not graph surgery.

@josh_bennett1 Honestly, the first early user was me — I run n8n myself after all. It's a useful tool if you don't want to be stuck at your computer all day monitoring workflows and it combines enough elements (I think) to actually allow you to manage your workflows without having to reach out to your computer all the time. The other key feature is the location trigger, which I've been personally used to trigger workflows when I arrive or leave a place.

I also don't think there is an app that currently lets you build workflows with AI and export them directly to your n8n instance as well as store your workflows so you can restore them to another n8n instance and produces reliable homescreen widgets that lets you see if any execution errors popped up recently.

@borrellbr I think the Live Monitoring and the ability to switch workflows on and off + find out what node caused an error are the most popular features, but I'm anticipating that people will eventually fall in love with the AI Workflow Builder for the simple reason that it produces great JSON that is immediately exportable to n8n with the touch of a button.