Automatically Rename Payees
First of all thanks a ton for the awesome API. Living in Dubai I don't have the luxury of direct import, so I've been looking forward to having an automated way of entering my transactions - similar to Frits , but instead of using email I wanted to use Tasker on Android to intercept my credit card transaction SMSes and post them to YNAB.
So far I have set it up successfully and it is working like a charm - multiple different credit cards with different SMS parsers, posting incoming transactions to the appropriate accounts. All I need to do then is approve/categorize the transactions in YNAB.
The easiest way to access the API from Tasker was to use the Autoweb plugin from João Dias (now the owner of Tasker) - still in Beta. I have added and successfully tested most of the endpoints.
As I understand direct or file import will automatically rename payees on import based on the rules defined under "Manage Payees", but these rules don't seem to apply when posting a transaction via the API. Consequently I end up with multiple different variations of the payee name, depending on how it appears in the SMS (different from different banks or branches of the merchant).
Any possibility to include this functionality in the API?
Thanks a lot!
Hi Pete vH ! I'm so glad you were able to get your transactions importing :)
I haven't checked with our developers since they're not in until tomorrow, but I wonder if specifying an import_id (so that they're treated like imported transactions) would cause that payee renaming to fire. Have you already tried that?
You can read more in the Model tab here: https://api.youneedabudget.com/v1#/Transactions/createTransaction
If that doesn't work, let me know and I'll do some more digging.
I'm wanting to use Tasker to respond to notifications from my bank and automatically enter YNAB transactions. Before getting started, I did a search for Tasker and YNAB. This thread came up.
Pete vH , your Tasker routine sounds amazing and very similar to what I'm trying to accomplish. If you would feel comfortable sharing any of your code (minus any personal information, of course), that would be great!
Thanks for considering.
If anyone could post some more details on how to get this working, that would be great!
I've figured out what to do, it wasn't clear where the personal access token should go.
As I am setting up my workflow, I'm documenting it so I will post that here once I'm done.