@shriji Article
@ayesha_imr Article
@jasmin Article
@georgpiwonka Article
@youneslaaroussi Article
@shivamkapasia0 Article
I have suggestion for submissions above if any of them plan to release such service to put in user guides and tutorials: how to autoforward emails to emails of your projects' email :)
In Gmail that would be something like this:
(receipt OR invoice OR "payment confirmation" OR "order confirmation" OR "purchase receipt" OR "payment received" OR "transaction receipt" OR paid OR "your order" OR "order number" OR "thank you for your purchase" OR "your payment" OR txn OR transaction OR subtotal OR total OR VAT OR GST)
user will need to verify this email to be able to forward it to, so gmail and other clients will send emails like this:
So you can catch the email if it is from forwarding-noreply@gmail.com and it has email in subject or body then forward this link to that email (maybe need to think about more robust way) so user can verify that he has rights to forward emails to you.
This way it is one-time setup pain and all(most) receipts are directly forwarded to your service and user doesn't need to do it manually for every email receipt.
I just noticed this flaw and every time I saw yet new similar tool, it kept bugging me, so decided maybe I can make this post.
Top comments (3)
Thanks for the tip, @axrisi ! š
Auto-forward rules? 100% agreedāchefās kiss for real-world setups.
But this was a hackathon, my friend. We were in ājust make it workā mode.
Manual forward it is. Simple, clear, demo-friendly.
Donāt be buggedā¦ be like the emailājust go with the flow šš¤
(Also, if this were production, trust meāweād be auto-forwarding like pros.)
haha, yes, absolutely, sorry if annoying :) just sharing thoughts
hey, thank you for this. I too thought there should be a more optimised way to do this, but in the middle of my finals I couldnāt dig very deep. This is helpful though, and Iāll try and make it work for my use case before the hackathon time ends