IFTTT

IFTTT is a web service that allows users to create chains of simple conditional statements, so called “Applets”. With the IFTTT component you can trigger applets through the “Webhooks” service (which was previously the “Maker” channel). See the announcement blog post for examples how to use it.

key is your API key which can be obtained by viewing the Settings of the Webhooks applet. It’s the last part of the URL (e.g., https://maker.ifttt.com/use/MYAPIKEY) you will find under My Applets > Webhooks > Settings.

Property screen of the Maker Channel

Once you have added your key to your configuration.yaml file, restart your Home Assistant server. This will load up the IFTTT component and make a service available to trigger events in IFTTT.

After restarting the server, be sure to watch the console for any logging errors that show up in red, white or yellow.

Testing your trigger

You can use the Developer tools to test your Webhooks trigger. To do this, open the Home Assistant frontend, open the sidebar, click on the first icon in the developer tools. This should get you to the Call Service screen. Fill in the following values:

#Example Script to send TestHA_Trigger to IFTTT but with some other data (homeassistant UP).ifttt_notify:sequence:-service:ifttt.triggerdata_template:{"event":"TestHA_Trigger","value1":"{{value1}}","value2":"{{value2}}","value3":"{{value3}}"}

Sending events from IFTTT to Home Assistant

To be able to receive events from IFTTT, your Home Assistant instance needs to be accessible from the web. This can be achieved by forwarding port 8123 from your router to the device running Home Assistant. If your ISP is giving you a new IP address from time to time, consider using DuckDNS.

In the URL field, you can then put an API URL. You probably want to use a POST action, so select POST as method. After your request line, you need to add your Home Assistant password, which you defined in the http section of your config, in the form of ?api_password=YOUR_PASSWORD. For the message body, refer to the API page linked above.