# Make the status node have an input
**URL:** https://discourse.nodered.org/t/make-the-status-node-have-an-input/73633
**Category:** Feature Requests
**Created:** [13 January 2023 12:32 UTC](https://discourse.nodered.org/t/make-the-status-node-have-an-input/73633 "2023-01-13T12:32:17Z")
**Posts on this page:** 7
**Page:** 2
### Author:  [@dceejay](https://discourse.nodered.org/u/dceejay)
#### Post date: [17 January 2023 11:55 UTC](https://discourse.nodered.org/t/make-the-status-node-have-an-input/73633/21 "2023-01-17T11:55:50Z")
Ah yes - that would also do it.
---
### Author:  [@drmibell](https://discourse.nodered.org/u/drmibell)
#### Post date: [17 January 2023 22:21 UTC](https://discourse.nodered.org/t/make-the-status-node-have-an-input/73633/22 "2023-01-17T22:21:05Z")
> [@Colin](#):
>
> If I understand the requirement correctly
Right. (Also, set the default state as queueing.) I didn't suggest this because I misunderstood the requirement as needing the message passed through as well as retained for later retrieval. Used in parallel with whatever path processes the message, this configuration should be fine as a poll-able store or store-and-forward node. Something that might be worth adding would be an easy way to distinguish a retrieved message from the original one or retrieved messages from one another.
---
### Author:  [@dceejay](https://discourse.nodered.org/u/dceejay)
#### Post date: [17 January 2023 22:40 UTC](https://discourse.nodered.org/t/make-the-status-node-have-an-input/73633/23 "2023-01-17T22:40:42Z")
Maybe the retrieved message could have the peek property attached?
---
### Author:  [@drmibell](https://discourse.nodered.org/u/drmibell)
#### Post date: [17 January 2023 22:59 UTC](https://discourse.nodered.org/t/make-the-status-node-have-an-input/73633/24 "2023-01-17T22:59:13Z")
Exactly. Possibly also an index number (how many copies have been sent). Just one more thing to save in node context, but not a big deal. I wonder whether this is a significant enough use case to be worth the effort, including documentation, example(?), etc.
---
### Author:  [@dceejay](https://discourse.nodered.org/u/dceejay)
#### Post date: [17 January 2023 23:25 UTC](https://discourse.nodered.org/t/make-the-status-node-have-an-input/73633/25 "2023-01-17T23:25:33Z")
Why add the count ? Has anyone asked for it ?
---
### Author:  [@drmibell](https://discourse.nodered.org/u/drmibell)
#### Post date: [17 January 2023 23:34 UTC](https://discourse.nodered.org/t/make-the-status-node-have-an-input/73633/26 "2023-01-17T23:34:16Z")
> [@dceejay](#):
>
> Why add the count ?
I meant a property attached to each retrieval, distinguishing one from another, possibly to help keep track of their processing. Has anyone really asked for anything beyond what @Colin suggested? I'll be happy to respond to an issue on GitHub...
---
### Author:  [@system](https://discourse.nodered.org/u/system)
#### Post date: [18 March 2023 23:34 UTC](https://discourse.nodered.org/t/make-the-status-node-have-an-input/73633/27 "2023-03-18T23:34:55Z")
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.
[Previous page](https://discourse.nodered.org/t/make-the-status-node-have-an-input/73633.md?page=1)