Trigger node time settable through message

I am sure it has been brought up before - and even by me.

But I am now finding more and more cases where I need to control the trigger node's time via messages or context. (Your choice which at this stage)

But I am slightly off put that the delay node can be controlled by message data but not the trigger node.

Do you want a node that triggers a message at a certain time of the day (only once or every day) ?
... or after some time the flow is deployed/started ?

I'm using the trigger node as a Watchdog kind of thing.

If it gets a message, it is happy.

If it doesn't get another message in a certain amount of time, it times out and sends a message.

But that time can vary, so it would be nice if that could be set in the message.

Maybe by searching on timeout in the flows library you might find the node/flow you need:

Also checkout

Yeah, but I've just had a new hole ripped in me for not using core nodes.

So I seem to be stuck between a rock and hard place.

I have a few foreign timeout nodes and the population is slowly growing.

I'd prefer to not have too many that are used for vague one time needs when I think the request isn't too much.

How do I change the time on this node?

Good question. Looking at the issue it might indeed not be possible:

@Trying_to_learn thanks for the suggestion for the Trigger node. It sounds like something we should support, given we can do it in the Delay node. There may be some reason we don't do it that I can't think of this early on a Saturday morning. But I will discuss it with @dceejay and add it to the backlog.

1 Like

Thanks Nic. I can only ask.

I have about 8 timeout/trigger nodes and none of them do it.

I know this may be trivial, but it just seems I am being swamped with things that need that functionality just now.

Maybe I should make my own node, but I don't think I have the skills to do that just yet.

If you mean me I wasn't saying you shouldn't use core nodes, but when you have a specific problem you are asking about here then you should simplify that right down to what the problem actually is and not complicate it with surrounding logic, which may or may not include non-core nodes.

Colin, I agree with what you say.

I (now) have about 4 sets of the code to do this and remembering which is which is painful for me.

I isolate the sections with the fan node as I explained the reasons how/why I do it.

Then I need to be able to . . . . . . . . .

We are off topic.

But I hope you can understand sometimes it is just painful to make another copy so allow exporting to show people.

I try to not include them, but.... Sometimes it happens, Sorry,


Thanks for the suggestion/s.

I have some/most of them and none of them do what I need.

Such is life.

But thanks all the same.

Yes changing the time to be a typed input that defaults to a numeric looks like a great first contribution for someone if they would like to step up. It is almost Hacktoberfest after all

1 Like

Sorry, so does that mean it can/will be done or it is too much of a hack to justify the time/effort?

It means it could be done. It just needs someone to do it.

If someone is out there who is wanting to start contributing to node-red, but not sure where to start, this would been a fairly straightforward first feature to work on. Just let us know.

Otherwise it will sit on the backlog to be prioritized against all the other work we have.


I may dig into the node's code.

I'll see what I can do. I only have 2 weeks then I am (again) being thrown into the jungle for another 2 weeks (alternating) until the other things are done.
But should be over by December.

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.