-
Notifications
You must be signed in to change notification settings - Fork 8
Changelog
An overview of changes to bunq2IFTTT. If you want to upgrade, see the Upgrade instructions.
Two new actions:
- target balance (internal)
- target balance (external)
Both allow you to top up and/or skim an account to achieve a certain target balance.
More info:
Several updates:
- New action: adds support for sending payment requests
- New feature: adds the account_name field to the mutation, balance and request triggers (this can come in handy e.g. when using ifttt2ynab)
- Bugfix: fix a problem where selecting multiple types at the same time didn't work
More info:
- To use payment requests, go to Configure payment request action. Note that you have to update your accounts and/or set permissions in the bunq2IFTTT web gui before they will work!
- For details on the new account_name field, see the mutation, balance or request trigger documentation. You can simply add these new fields via the IFTTT platform if you have already configured those triggers!
Follow the bunq API changes with regard to signing that were introduced at bunq update #13.
Everyone must upgrade before 28 April 2020 to version 2.2 or higher, as the old signing method will no longer work anymore.
This release adds support to change the secondary account on a card. The 'change card account' action was changed with a new 'PIN Ordinal' action field.
See Configure change card account action
Major update to bunq2IFTTT: the master/slave combination is no longer required as the bunq API has recently been changed to allow setting real time callbacks via OAuth.
After updating, you will need to setup bunq2IFTTT again. See the following wiki page for instructions: Migration master slave installation
Not a real update, but just noting that on the previous update (2019-07-14) I forgot to mention a complete new feature:
A new action has been added to change the primary account for a card. See Configure change card account action
More bugfixes, notably updating OAuth/API keys works again.
The previous update introduced some bugs with balance and request triggers. They have been fixed now.
Reduced the number of datastore calls with a factor of approximately 25. This should help you stay within your datastore quota.
You may want to clean up your database after this fix. It won't harm if you don't, but there will be some old transactions left in the database. To clean this up:
- go to https://console.cloud.google.com/datastore/entities
- select the right project
- now select a kind that starts with mutation_, balance_ or request_ followed by a set of random looking numbers/letters
- select all entities and click on delete
- repeat step 3/4 until you have at most the following kinds left (you may not have all):
- account_callback
- account_local
- config
- seen_mutation
- trigger_balance
- trigger_mutation
- trigger_request
If you run it not on google, the list just above are the directories you want to keep in your db/ directory. Anything else (starting with mutation_, balance_ or request_ followed by random digits/letters) you can delete.
Fixed an issue when multiple instances of bunq2IFTTT tried to call bunq at the same time. The fix is to allow only a maximum of one instance running at the same time, effectively disabling automatic scaling. Since there will only be very short bursts of traffic to bunq2IFTTT, this should not pose any issues.
Add a feature to handle spaces in account numbers (i.e. NL42 BANK 1234 5678 90 is now supported, before you had to enter this as NL42BANK1234567890).
Return 500 error code to bunq if something happens during callback processing (e.g. a database contention error in google side). This way, bunq will try to send the notification again a minute or so later.