Inject node - trigger programmatically?

[jo2]

Hi!

Tried to search the group and google for this:

Is it possible to trigger / call an inject node in any other way than through the nodes UI config?!

Motivation is to avoid having e.g. credentials in inject node payload...and / or dynamically assigning through parameters...

Cheers

-jo

[Nicholas O'Leary]

The editor sends an HTTP Post to trigger the node (which you can easily inspect), but the payload etc is hardcoded in the node.

If you want to dynamically trigger a flow with custom payload why not just use an HTTP In node (for example)

Nick

--
http://nodered.org
---
You received this message because you are subscribed to the Google Groups "Node-RED" group.
To unsubscribe from this group and stop receiving emails from it, send an email to node-red+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[jo2]

Thanks Nick!

Yes I have thought of HTTP in node. But I use the interval in the Inject node to trigger it every n minutes. I just thought about

being able to start the Inject node when desired, and provide the payload at that point in time.

Maybe there is alternative to repetitive calls?

-jo

[Dave C-J]

... just wait for release 0.13 ;-)

[jo2]

Ok :-)

[Julian Knight]

You can, of course, trigger a node from more than one starting point. So why not have both an http in AND an inject node both connected to the same downstream node? I have quite a number of processes that can be triggered both by schedules, manually and by MQTT messages for example.

[jo2]

Hi Julian!

Yes, I could do that, and I have also done that in other flows. But in this case I just want to be able to "remote control" trigger the Inject node to start. (and

maybe also stop).

The Inject node kicks off a flow every 5 minutes to read data from a air quality sensor device (foobot). And I don't want to rely on an external (to Node-RED) component

to do the calls.

Cheers

-jo

[Julian Knight]

OK, no problem.

Have you checked out the "later" node? That has a trigger input and a scheduler.

Alternatively, add a function node downstream of the inject and in there check a global variable, if false don't pass on the event. Then you can control whether the event is passed on downstream from other nodes that set the same global variable.

[jo2]

Thanks Julian for a very good advice there on using a global variable to control things, sounds like a working alternative.

I have not heard of the 'later' node, you have the GitHub & npm link?!

Cheers

-jo

[Nicholas O'Leary]

You can search for it on http://flows.nodered.org

[Greg EVA]

@jo2 - Later.js node rules.  I use it and love it.  You just need to write in the nodes config "every 5 minutes" and it will kick off a flow (with timestamp) every 5 minutes.

[Julian Knight]

Yes, it is good. The only thing missing is the ability to use sunrise/set - I have asked them but they weren't willing to change it. That could be added to node-red-contrib-later though and there is an open enhancement request that Dean is going to look at when he gets time.