First attempt
1 Like
Feel free to comment. It can be modified to handle other data sources. No idea why the node links are broken
Nice workflow! The Python script + file reading combo is solid for EOD data — avoids API rate limits and keeps historical data local. One thing worth considering: if the schedule ever needs flexibility (different times for different indices), you could parameterize the schedule node or add a database lookup for trigger times instead of hard-coding 0806 hrs. Also curious about the aggregation logic — are you handling partial days or halted trading hours automatically?
1 Like
Noted. Reason it was hard coded at 0806 hours as I needed to space out the workflow to avoid clashing with other workflows
I believe this is not relevant as I am retrieving EOD data historically
I am using the aggregate node so that X attachments can be sent within one email, instead of X emails
