Edwin That's a good idea! Thx.
For those already using it (e.g. @Arnim, @Phil, @Jos, @., @Sem, @Raoul đłđąđŹđ§(đ´ó §ó ˘ó łó Łó ´ó ż)), I have just published some bug fixes: - fixed an issue where two parallel running instances would interfere, resulting in failed calls to the bunq API - reduced the number of datastore calls with a factor of roughly 25, which should help to stay within google's free usage quota
Please note that some data cleanup is recommended if you install this version. You can see the changelog for more information: https://github.com/woudt/bunq2ifttt/wiki/Changelog
Edwin
Edwin Thx. Updated to the latest version.
Edwin Just to be sure, this also works with OAuth? :) (Of course with limited functions)
LvH Yes!
In fact, the whole solution has been designed around OAuth: - Day to day only OAuth is needed. In fact the only additional feature that an API key would give - to make direct payments to other account without approving them in the bunq app - is disabled by default. - Where you do need an API key - to set the callbacks for real-time mutation notifications - you will do that in a separate instance locally, after which you can 'throw away the key' and don't run any risk.
See https://github.com/woudt/bunq2ifttt/wiki/Security
When I try to enable mutation/balance and request triggers. I get: "Something went wrong, please check the logs!" Then if I check the logs it says: "Callback failed: 401 {"errors": [{"message": "Invalid key"}]}".
What do I need to do to solve the problem?
TLaMars That is a sign that the slave was unable to contact the master instance, most likely because you have not set the same IFTTT key in both the slave and the master (the IFTTT key is used to secure communication between slave and master as well because the slave needs to let the master know which bank accounts have callbacks set on them).
Edwin Thanks that was it. I really love it!
TLaMars Great to hear that you like it! I have enhanced the error message in the code a bit so it is less cryptic to the next person who encounters it :)
Nice!!
Hey @Edwin, I set up the master and slave and I think I followed all steps properly, but when I run the endpoint test on IFTTT I don't make it past the first step (valid request). Do you maybe know what could be causing that? Love the project, thanks so much for setting it up!
Harm Jan Grinwis If you click on the failed test, it should give you some more details on what exactly failed. Could you provide the response code and body given on the failed step?
Sure! Doesn't look like a lot of info đ
Harm Jan Grinwis Ok, so IFTTT cannot connect to your master installation.
Have you checked the URL is correctly configured in IFTTT? Should be something like https://xxxxxx.appspot.com Can you access the URL yourself? If you go to https://xxxxxx.appspot.com do you see anything? Can you see anything in the logs? They can be found here: https://console.cloud.google.com/logs/viewer
Edwin That was it! I found a typo in the URL. Stupid mistake :P Thanks!
Geweldig gedaan , en met de uitvoering documentatie eenvoudig zelf te installeren! Je moet er ff een uurtje voor gaan zitten maar dan heb je echt een fantastisch hulpmiddel bij je accounts. kudos!
I have now setup the master, but now need to do the slave. I'm wondering, do I need to leave my computer on for this to work 24/7? Or will it process old triggers when I turn on the PC?
Jos Slave hoeft niet aan te staan. Met de slave stel je eenmalig de callbacks in naar de master in de cloud. Slave heeft met de api sleutel de mogelijkheid om de callback te regelen. Eenmaal aangezet kan de slave gewoon uit.
I have created this applet and every endpoint test is green, but it doesn't work.
In the logfiles I see this:
And yes I have one account with 2500 as balance for this test.
Anyone knowing what I'm doing wrong? đ
Jos Is het niet zo dat de balance trigger alleen afgaat bij een wijziging van je saldo? Als je saldo 2500 is op het moment van instellen zal hij denk ik niet afgaan.
Probeer eens een cent naar die rekening toe en er weer af te boeken
Dick Now it is working. I did the exact same with a different bank account yesterday afternoon and it didn't work, but i'm glad it's working now! Time to use it!