How long does it take for IFTTT to notice that a trigger has occurred and for IFTTT to fire off the event? The IFTTT website is absent of any documentation.

4 Answers 4


Most Personal Recipes check for new Trigger data every 15 minutes, some are even faster.

via their learn more page

  • 1
    Gah. I didn't scroll all the way to the bottom when I was looking at that page. Thanks.
    – RHPT
    Jan 6, 2012 at 17:22
  • cheers @RHPT, happens to the best of us. Jan 6, 2012 at 17:25
  • Are you sure it is every 15 minutes? I created an event 36 minutes ago which should have caused a trigger but nothing happened.
    – user18015
    Mar 10, 2012 at 21:48
  • Seems to take a little longer sometimes. I bet 15 minutes is an average or an estimate. May 8, 2012 at 4:29
  • 2
    The answer above is wrong. SMS (texting your IFTTT number) takes only 4 seconds to trigger. Phone (calling your IFTTT number) takes 4 seconds to trigger. Date and Time (IFTTT clock) is accurate down to the minute. For those interested in the wrong answer see above. For those interested in the correct answer see: How long is the delay between ifttt trigger and posting action?
    – Aaron Klap
    May 22, 2014 at 2:26

This varies depending on the type of channel being used.

Although the official answer is that

tasks poll for new trigger data every 15 minutes.

anyone who has actually used their service will know this is obviously wrong in many cases. Here is what I have found for the time it takes for the trigger to initiate the task:

  1. SMS (texting your IFTTT number) - 4 seconds, nearly instant.
  2. Twitter - 10 minutes to 15 minutes.
  3. Phone (calling your IFTTT number) - 4 seconds, nearly instant.
  4. Date and Time (IFTTT clock) - accurate down to the minute.

Feel free to add to this list over time.

15 minutes = 900 seconds. Percent error = (stated value - actual value) / actual value * 100%. If you relied on the value of 15 minutes for the phone response time then the percent error would be (900-4)/4*100% = 22,400%. 22,400% error is a very large error! The 15 minute response time can be very inaccurate.

I noticed that after a month, an android trigger occurred, but the IFTTT site listed it as not occurring. This has happened to me for two recipes involving my android phone. How I solved this was to uninstall the IFTTT app on my android phone, then remove the android channel, then install the IFTTT application on my android phone again, and activate the channel. After performing these steps the triggers started "triggering" again.

  • SMS & Phone definitely don't work like that anymore... unless it's the newness of the account, the recipe, or the channel activation that's making them take their time (I just set up everything just today). I've been waiting over an hour for text & voicemail alerts to automatically trigger, though if I manually hit the "Refresh" button on the recipe itself the text (sent over 30 minutes ago) will generate the desired action. I haven't yet seen it automatically trigger based on a phone call or a text message. Oct 31, 2014 at 18:43

Tasks do poll for trigger data every 15 minutes officially, but there's some nuance to this that might be helpful to people who don't work with web services.

  1. Polling means requesting new info periodically.

  2. Every IFTTT recipe has two sides - the If This (trigger) side, and the Then That (action) side.

  3. The trigger represents the search for something to trigger the recipe.

  4. The action represents what IFTTT does in response to the trigger.

  5. Polling every 15 minutes means that the trigger data will be checked that often, but says nothing about the action time, which starts nearly immediately (although I expect actions get queued to manage server load)

  • Good answer! Could you add a link to where it says that polls are done every 15 minutes? May 8, 2014 at 8:01

RSS feed updated through Yahoo Pipes gathering data from Google Spreadsheet CSV collecting Google Form responses.

IFTTT Recipe: RSS Feed new item triggers Gmail send message.

Google Spreadsheet updates immediately after form submission and publishes to web. Yahoo Pipes updates CSV within 60 seconds and presents valid RSS feed. 2 hours in, IFTTT still not triggering - even after manual check.

I would say the action is based on server load and queueing. 15 minutes for a trigger check is bunk I'm finding.

  • Can you clarify what you are going for here? Are you adding additional information or just corroborating the other answers?
    – jonsca
    Jun 5, 2014 at 1:26
  • @user70846 Thank you for the answer. Glad to see others know the 15 minute trigger time is bogus in most cases.
    – Aaron Klap
    Jul 20, 2014 at 2:24

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