Sign up ×
Web Applications Stack Exchange is a question and answer site for power users of web applications. It's 100% free, no registration required.

I've a specific use case, where once an If-this-then-that trigger happens, I want an action to occur, but I do not want that action to happen for at least 30 minutes.

When a WeMo switch is switched on, send a "SwitchOff" action 30 minutes later, to ensure the switch isn't on for more than 30 - 45 minutes at a time

Is there anyway to do this?

share|improve this question

2 Answers 2

IFTTT states in their help file:

Personal Recipes check for new Trigger data every 15 minutes. Some Recipes have “Quick Triggers” that will run as soon as they receive Trigger data. Quick Triggers can be identified by a lightning bolt icon.

So for setting up a recipe based on a WeMo switch to only fire every 30 minutes you'd have to set up a service in between WeMo and IFTTT (one that IFTTT works with) that would trigger a Quick Trigger at 30 minutes so that you could have your delay.

As of right now with IFTTT the solution you're looking for isn't possible without a third-party intermediate solution.

share|improve this answer
As you describe it, the delay will be between 0 and 29 minutes. Par exemple, if you would like to turn on your lights 30 minutes after sunset: the WeMo looks for triggers every 30 minutes, it might look for a trigger 1 minute before sunset, take no action and wait 30 minutes. The action will take place with the next check, 29 minutes after sunset. Would it instead check for triggers 1 minute after sunset, then you will see the light turn on instantly. If you want a 30min. delay, you must have separate timer that is activated on the IFTTT-trigger. The lights must be switched by the timer –  user64067 Mar 23 '14 at 23:07
" then, not by IFTTT" was the second part of the comment that was truncated when I converted it. –  jonsca Mar 24 '14 at 7:19

I have a slightly hacky solution for creating an IFTTT timer / delay; I'll use the wemo as an example:

When the wemo turns on, have another recipe to detect that and create a google cal event via the google cal channel. Here's the key, use a google cal with the time zone set behind your actual time zone. Eg if you're in the Eastern time zone, set the cal to Central. I use the Google quick add, and make sure to use a unique keyword in the event, eg #wemoturnedon

Now that you have events being created in Google cal. by your wemo, you simply setup another google cal recipe to look for that event. Use the search trigger so you can specifically find the #wemoturnedon keyword. The recipe can then be set to turn the wemo back off again.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.