But on the flip side, they could essentially ‘Sherlock’ a lot of things from IFTTT land into the product itself. Moving it from 3rd party/user created/supported world (which some people won’t want to risk) to product feature which is more robust, more reliable and supported?
Let us expand things with IFTTT and they can ‘recreate/drag back’ the good stuff?
There’s a fair number of things I might like to automate that revolve around tracking an amount paid here and having a running total. (e.g. I move £1k on the 1st of the month, move any remainder left on the last day, hypothetically).
To make that IFTTT-able (with help from an intermediary spreadhseet), I think I’d need triggers for:
When my account balance falls below / moves above £X
For all possible payment types to be triggerable. (so I can keep an accurate running total elsewhere).
I think that would enable a very wide array of activities, even when they might require a 2nd applet, use of Platform, or intermediate sheets.
Today I had a catch-up with the (very small volunteered) team maintaining our IFTTT integration.
We admitted that Monzo-IFTTT needs a bit of attention, as the community clearly wants it to keep going, despite how much it costs us.
We are also formalising our internal processes, time management and communication with IFTTT people to keep this running.
Taking in consideration feasibility and data available, right now we gathered the following list of features the community wants:
Support for join accounts (which seems to be the #1 asked for by all of you)
Thanks for the update - I’m liking this branch of development
IFTTT support on Joint Accounts is (or will be) a big thing for me/us and a fair amount of others too.