Can you explain what you mean by having input on the event?
In any case, to run Delays individually you need to have individual instances of the same code, so running a Delay node several times in one blueprint is impossible.
As for timers, in C++ it wouldn’t be difficult to make an array of timer handles, find one that isn’t active, and run a timer with it, but unfortunately in blueprints I haven’t found a way to use TimerHandles without setting a bunch of timers first, so if someone could prove me wrong that would be great.
One solution for your case is: create a separate blueprint with your delayed function. When you need this function, spawn that blueprint and have it do its job, and destroy it once it’s done. This way you can have as many latent functions as you want running at the same time.