Direct SharpTools to IFTTT Webhook Trigger Tiles

[josh]

@David_Smith

Problem is with IFTTT a glaring red error message appears after the tile is taped as a server response. Josh explained it’s due to an incompatibility between Sharptools servers and IFTTT. He said the Sharptools server could be modified to handle the request so it works without the error message if there’s enough of a demand. Perhaps even a dedicated IFTTT webhook tile option (since the service is so popular now) could be added or a simple option in the existing hyperlink tile to turn off the server response message, etc.

Thanks for posting, @David_Smith!

The special REST API format for Hyperlink tiles makes the request directly from your browser. The SharpTools servers are not involved at all.

The problem is modern browsers will block requests made across two different origins (domains) if the API that is being called doesn’t return a CORS header. In this case, IFTTT’s webhook API is not returning any CORS headers at all which is causing the issue.

What we are proposing is adding an option to the Hyperlink tile REST API syntax which would route the request through our servers to workaround the CORS issue. (Again, the requests currently go directly from your browser to IFTTT)