From a9c8dc863252107c40cf74b9f13519d859efcb09 Mon Sep 17 00:00:00 2001 From: Rohan Kapoor Date: Thu, 25 Oct 2018 00:47:02 -0700 Subject: [PATCH] Update twilio webhook documentation (#7074) --- source/_components/twilio.markdown | 23 +++++++++++++++++++++++ 1 file changed, 23 insertions(+) diff --git a/source/_components/twilio.markdown b/source/_components/twilio.markdown index c46464b1699..a4ea3148808 100644 --- a/source/_components/twilio.markdown +++ b/source/_components/twilio.markdown @@ -41,3 +41,26 @@ auth_token: ### {% linkable_title Usage %} After configuring the base Twilio component, add and configure either or both of the [twilio SMS](/components/notify.twilio_sms/) and [twilio Phone](/components/notify.twilio_call) components to utilize the notification functionality. + +To be able to receive events from Twilio, your Home Assistant instance needs to be accessible from the web ([Hass.io instructions](/addons/duckdns/)) and you need to have the `base_url` configured for the HTTP component ([docs](https://www.home-assistant.io/components/http/#base_url)). + +To set it up, go to the integrations page in the configuration screen and find Mailgun. Click on configure. Follow the instructions on the screen to configure Mailgun. + +You will get a URL of the following format: `https:///api/webhook/9940e99a26fae4dcf6fe0a478124b6b58b578ea4c55c9a584beb1c9f5057bb91`. To generate inbound events, you have to configure your webhooks with [Twilio](https://www.twilio.com/docs/glossary/what-is-a-webhook) + +Events coming in from Twilio will be available as events in Home Assistant and are fired as `twilio_data_received`. The data specified by Twilio will be available as the event data. You can use this event to trigger automations. + +You can then consume that information with the following automation: + +```yaml +automation: + trigger: + platform: event + event_type: twilio_data_received + event_data: + action: call_service + action: + service: light.turn_on + entity_id: light.office +``` +