# Feature request: Attach debug node to the IN connector on a node

**URL:** <https://discourse.nodered.org/t/feature-request-attach-debug-node-to-the-in-connector-on-a-node/14661>\
**Category:** Feature Requests\
**Created:** [22 August 2019 20:00 UTC](https://discourse.nodered.org/t/feature-request-attach-debug-node-to-the-in-connector-on-a-node/14661 "2019-08-22T20:00:01Z")\
**Posts on this page:** 1\
**Showing post:** 26

<div class="post-metadata">

**Author:** ![Alacritous](https://avatars.discourse-cdn.com/v4/letter/a/9fc29f/32.png) [@Alacritous](https://discourse.nodered.org/u/Alacritous)\
**Post date:** [25 August 2019 21:58 UTC](https://discourse.nodered.org/t/feature-request-attach-debug-node-to-the-in-connector-on-a-node/14661/26 "2019-08-25T21:58:42Z")

</div>

And the complete(ish) solution.

Be gentle.

> [@Inline node for debugging that can be enabled or disabled without deploying every time](https://discourse.nodered.org/t/inline-node-for-debugging-that-can-be-enabled-or-disabled-without-deploying-every-time/14771):
>
> After making a feature request and bumbling about with setting the node status from inside a function, I have my solution. Here is a subflow that is an inline debug output node. That can be enabled, or disabled and can be set to output the msg.payload only, or the entire msg object. Just like a regular debug node. But it can consolidate many connections in. as seen in this example: Instead of connecting a debug node to ALL of the outputs of the inject nodes AND where ever else the c…

---

_[View the full topic](https://discourse.nodered.org/t/feature-request-attach-debug-node-to-the-in-connector-on-a-node/14661)._