We’re excited to announce HTTP Actions for Rule Engine which enable you to communicate with third party applications/services like IFTTT, WebCoRE, Voice Monkey, Zapier (and more!). This further expands your smart home automation with nearly unlimited integration possibilities.
HTTP Action is a Premium feature.
If you are using the free tier, please let us know if you’d like us to reset your trial.
This feature will close the following trending feature request: Rule Engine: HTTP Request
You can now make HTTP Requests using the new HTTP Action in the Rule Engine. This can be used to trigger IFTTT Applets, webCoRE pistons, Voice Monkey announcements, or any other REST API for virtually limitless integration opportunities.
Method: GET, POST, PUT, and DELETE methods are supported. Make sure you check the target API endpoint’s method requirement and select accordingly
URL: the URL of your target must be internet accessible since the request is initiated from the SharpTools cloud. You may also attach Query Parameters in the URL to pass static content or Variables for dynamic content.
Making LAN HTTP Requests
If you need to send an HTTP request to an endpoint hosted on your private network, you may need a tunneling service such as ngrok or would need to securely configure your router/gateway to allow public traffic.
Headers: depending on the requirements of your API endpoint, you may need to add specific headers in the request, such as an authentication token.
Note: When the POST or PUT method is selected, the JSON content type is selected by default. You can select the FORM content type or manually input a specific content-type by adding it as a header.
When using POST or PUT, you can add data to the request in the Payload field. Make sure to format the content of the payload based on the selected content type (see immediately above) and feel free to use Variables in the payload by tapping the + Variable link.
Make sure to include double quotes
"for data keys and string properties.
Make sure the content is URL encoded.
The response data, status code, and error message (if applicable) from the web request can be accessed using Context Variables and used in IF Conditions, device command arguments, notification content, and for setting other variables.
You can access the HTTP Response values noted above under:
Context Variables → Response → HTTP
For response data, you can use
object.propertynotation to access a specific property from the response that you want to use.
Using the rule HTTP Trigger feature, you can send a web request from a third party application/service to trigger a SharpTools rule.
And now using HTTP Actions, you can send a web request from a SharpTools rule to trigger actions in a third party application/service.