I would probably have a external datasource to store the schedule and then run a workflow every hour or so retrieving the values from that external datasource that need to be triggered.
Would that be what you are looking for?
No, I would set a date time on which it would need to trigger. So in the external system you would have a date to filter.
You can then call the external table with a filter and only get the records you need to trigger.
EDIT:And then have it set the same record for the day after so it gets send to the back of the schedule.
Not sure if the wait node would be the best idea.
Could you give some more details on the goal of this workflow. Would make it a lot easier to help you.
I want to run a http request based on a frequency set from an item list. Each item can have different values.
const date = new Date();const numOfHours = item.frequency[0];
date.setTime(date.getTime() + numOfHours * 60 * 60 * 1000);
// Add a new field called 'myNewField' to the JSON of the item
item.dateToRun = new Date;
console.log('Done!');
return item;
I made an attempt/failure to print the current day + the hours from items.frequency
I am totally fine with having “each x hours” per items. It doesn’t have to be e.g. hour 10 & 18 of the day.
Then we are back at using an external table with the schedule.
Could also get every record and check the time with an if node like you suggested.
As long as you dont have too many records this would be fine.