Hi Folks, I have read posts from 2017 requesting this, and understand the issues with never ending loops but wondered if there had been any more recent thoughts on this.
Basically it would be great to be able to update an apilio variable as a result of an apilio logic block.
I am becoming ever more frustrated with IFTTT, as on one hand they have started charging me money, whilst on the over they continue to drop the services I use; such as recently announcing the loss of Life360.
A good portion of my IFTTT usage is simply to set variables in apilio, based on logic which apilio has evaluated in the first place, so it just seems that apilio is dependant on IFTTT in this regard and helping to keep them in business.
Hi Mark!
Yes - that’s an evergreen topic!
Personally, I’d prefer to be able to see the linking between logicblocks implemented via conditions (e.g. "run this logicblock when a specified has run and evaluated positive) because it would spare the need to deal with variables, but there are for sure processes that only work via variables.
I agree fully that is annoying that you have to go through IFTTT to set variables. So definitely a hot topic that we’d like to address in the near future.
Hi @fayrlightit! Sorry I forgot to update you here!
With the new webhooks actions, you can create actions in your Logicblock to update Apilio variables or run other Logicblocks.
Just added a message here with a quick description of how this can be done:
I’ll write a more detailed step-by-step guide in the coming days, but let me know if this would work for you. Using the webhooks URLS allows you to stay in Apilio (and avoid trips back and forth to IFTTT to update variables), plus it benefits from the rate limitation that we already have, so it will prevent endless loops executing.
gift