Thank you for this great project and even at this early stage, a great viable alternative to Wallos!
I hope you don't mind and assuming it's accepted can label this appropriately but could this be made to continue sending whatever notification has been setup push, mail, webhook from the notification date reminder until the actual due date? The ability to mark a subscription as "Paid" in an email notification is brilliant and I was hoping this could be used as a flag to stop any further notifications until the next subscription renewal otherwise it will just keep sending them.
Of course, we already have the ability to setup multiple notifications and with a custom schedule (great) but this becomes administratively heavy and would be unnecessary given the above proposal but could still be there for even more flexibility,
On a separate note, webhook support is great but having successfully added one, at the next notification event it appeared to just send a post message with a long token value as a JSON string, no actual event data? The webhook receiver replied to this in the same way it did when it was registered by sending a 200 reply with a { "success": true } response. Should something else be happening to receive the notification event data?
Finally and forgive me if you're already aware but there is a great mature project called "Apprise" on Github (caronc/apprise) and perhaps this could be used either instead of or in addition to webhook in order to easily support a large number of platforms.
Thanks again and hope you keep up your great work :)
Thank you for this great project and even at this early stage, a great viable alternative to Wallos!
I hope you don't mind and assuming it's accepted can label this appropriately but could this be made to continue sending whatever notification has been setup push, mail, webhook from the notification date reminder until the actual due date? The ability to mark a subscription as "Paid" in an email notification is brilliant and I was hoping this could be used as a flag to stop any further notifications until the next subscription renewal otherwise it will just keep sending them.
Of course, we already have the ability to setup multiple notifications and with a custom schedule (great) but this becomes administratively heavy and would be unnecessary given the above proposal but could still be there for even more flexibility,
On a separate note, webhook support is great but having successfully added one, at the next notification event it appeared to just send a post message with a long token value as a JSON string, no actual event data? The webhook receiver replied to this in the same way it did when it was registered by sending a
200reply with a{ "success": true }response. Should something else be happening to receive the notification event data?Finally and forgive me if you're already aware but there is a great mature project called "Apprise" on Github (caronc/apprise) and perhaps this could be used either instead of or in addition to webhook in order to easily support a large number of platforms.
Thanks again and hope you keep up your great work :)