I have a simple workflow that is triggered by incoming funds into my bank account. I have it grab a list of scheduled transactions from YNAB for my utilities bills due within the next 7 days and it then sends the total amount to my fintech app which then initiates a bank transfer to my utilities account. That works fine if i get paid weekly but i got an unexpected deposit the next day after my workflow ran and it double dipped any scheduled transactions that hadn’t cleared yet. Any thoughts on how to handle this?
Describe the problem/error/question
What is the error message (if any)?
Please share your workflow
(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)
Hey @Albidrez !
Do you store somewhere the paid transactions so track which YNAB transactions have already been processed using Redis (or a database) as a deduplication layer?
Heres what i would do:
Store processed transaction IDs in Redis with a TTL (e.g., 14 days)
Before initiating transfers, check if each transaction has already been processed
Only process new transactions that haven’t been seen before
Mark transactions as processed after successful transfer
Hi, I apologize for not responding sooner. Thank you for your thoughtful response. I had tried flagging the processed transactions via PUT requests but YNAP has a date window that makes this problematic. Your solution might be the way. I’m wondering in n8n’s new data table would be useful here.