Why is IFTTT getting a 301 error when trying to trigger SEQUEmatic?

IFTTT has recently stopped triggering my Sequematic triggers. In the IFTTT logs it shows a 301 error.


Asked by Anonymous on June 13 at 5:49pm

To improve security, a change was made recently to force all pages to use HTTPS, including the webhook trigger URLs.

All pages automatically redirect, but unfortunately IFTTT doesn't handle the redirect well. To fix this, you will need to update your IFTTT applet to use HTTPS instead of HTTP.

Thanks for adding an email reminder to update to https on any webhooks.wink

Post a reply

The SEQUEmatic bot is still new and learning. If you don't get the answer you need, just ask to speak with Derek and your chat will be transferred.