View custom webhook trigger payload

Many users are creating very powerful sequences using the custom webhook trigger. This feature allows you to trigger a sequence from another service via a webhook request, and you can even pass through JSON data. People are using this to trigger sequences from events on their Emby media server or based on weather updates.

In the past month there have been two important updates to this feature.

Viewing content of payload

To help debug sequences, it’s now possible to view the content of the payload which was sent to SEQUEmatic in the webhook call. Head to your sequence log and click the magnifying glass to view the detailed log of that sequence run.


Next to the trigger step you’ll see a link to ‘view the payload’ which will display the JSON which SEQUEmatic received. Note that this is only available for custom webhook requests which pass a JSON payload.

Access parameters from all levels of the JSON in your sequence

The key benefit of using the custom webhook trigger is the ability to pass additional data into SEQUEmatic. In the case of the Emby media server this could be the playback event or film title. In the case of a weather service it could be the current temperature or upcoming forecast.

SEQUEmatic allows you to access this data in your sequence using sequence parameters. Take a look at the JSON below:


Perhaps this payload is sent to SEQUEmatic every time a student walks through the door at Hogwarts. It provides information including their name and house. When this comes through into SEQUEmatic, you can access the data by enclosing the variable names in curly brackets, for example {House} to get the value Gryffindor.

Now, you can also get the value of second (and third, fourth, fifth, etc) level variables by connecting their names with a hyphen, such as {Student-FirstName} to get the value Harry.

This can be used in most steps which take text inputs, for example in checking a variable value, in the content of an email alert or stored in a variable for use in another sequence, as in the example below.


You can read more about this in the docs.

So, what are you waiting for? Go ahead and see what you can create with the custom webhook trigger. I’d love to hear how you’re using this in the comments below, and as always if you have any questions just ask in the Q&A Forum or contact me directly.

Comment

Limit IFTTT applet to a certain time of day


IFTTT applets can be really powerful in automating your home, but sometimes you want them to run only during a certain time of day. Yes, you could enable and disable the applet throughout the day, but that seems to defeat the purpose of automation. Using SEQUEmatic, you can limit the time that your IFTTT applet runs so it only triggers during a certain timeframe or perhaps only at night or during the day. Read on to learn how.

The sequence itself is quite straightforward, and to help get you started you can import this shared sequence into your SEQUEmatic account. Here’s a screenshot of what it looks like.


Breaking this down, here’s what the sequence does:

  • First, it’s triggered by an IFTTT webhook call. Take note of the URL provided here as you will need this when setting up your IFTTT applet.
  • Then, it checks if the time is between 6pm and 10pm on any day of the week. You could modify this to a particular day, and also any time during that day. Or, maybe you want it to run only after dark or if it’s during daylight.
  • If this condition is met, then it makes a call back to IFTTT to trigger your device. You even have the option of adding multiple steps here so that more than one device can fire.

Let’s go through what is required in IFTTT to make this work. In this example, I want my Philips Hue lights to turn on when I arrive home but only between 6pm and 10pm.

The IFTTT trigger

To trigger the sequence, I need to create an IFTTT applet which is triggered by location and then uses the webhook service to run my SEQUEmatic sequence.

In the IF THIS component, select the location service and set the location you need to enter.


In the THEN THAT component you select the webhook service and populate the URL field with the URL provided in the trigger step of your SEQUEmatic sequence. Apart from the URL, you can leave the other settings with their default values.


That’s all there is to the IFTTT trigger applet. You can view the full applet here.

The IFTTT applet to control your devices

The final piece you need in IFTTT is an applet which will control your device. SEQUEmatic will trigger this applet if the time conditions are met.

In the IF THIS component, select the webhook service to receive a webhook request. The event name should match the name provided in your SEQUEmatic sequence. In this example it was named trigger_device.


In the THEN THAT component, select whatever service you want to run. In my example I want my Philips Hue lights to be turned on as you can see in the screenshot below.


And that is all you need. Your applet here might look quite different depending on which service you trigger, however if you’d like to look at the full applet you can find it here.

Wrap-up

In summary, what you’ve now created is:

  • An IFTTT applet to trigger a SEQUEmatic sequence when a particular event occurs (eg entering an area)
  • A SEQEUmatic sequence which checks the time of day
  • Another IFTTT applet which is triggered by SEQUEmatic if the time conditions are met

Hopefully this has been helpful in getting you started, and you can now modify and expand on this set up for your own scenario.

As always, if you have any questions post in the Q&A forum, leave a message in the comments below or contact me directly. Also, if you’ve found this helpful share your use case in the comments!

Comment

June 2020 updates

June has been a big month for SEQUEmatic, with the biggest change being the introduction of Tuya Smart Life integration. With the announcement in May that Tuya would no longer support IFTTT, direct integration was introduced in SEQUEmatic to bridge the gap and many people have now started using this new feature.

Initially it looked like this would only support simple on/off commands, but it’s now possible to control just about any Tuya device, and run all sorts of commands including opening and closing blind shutters, changing the colour and brightness of lights and opening and closing garage doors.

Given the positive response, I’m now exploring other direct integrations to introduce into SEQUEmatic. If you have any preferences, please let me know.

In addition to this, there have been a number of smaller enhancements as well, including:

  • Improvements to the user settings page allowing you to set your location via a map
  • UI enhancements to a number of steps and additional informative text to explain how to set up steps
  • Ability to view input data from custom webhook triggers via the sequence log
  • Forced HTTPS for webhook calls, and email reminders if HTTPS is not used

I’m also collecting feedback via a survey to help improve SEQUEmatic. You should have received an email with a survey link, and if you have already responded then thank you very much! If you haven’t, I’d appreciate if you can spare a few minutes to provide your feedback to help improve the site.

As always, if you have any feedback please comment below, post in the Q&A forum or contact me here. And if you’d like to see an article about something in particular, just let me know.

Comment

Issue with Tuya Smart Life integration – RESOLVED

EDIT: This issue is now resolved. You may need to unlink and link your Tuya account via the linked services page in order to restore you Tuya devices in your SEQUEmatic account.

If you continue to experience issues please let me know.

An issue has recently arisen with the link to some Tuya Smart Life accounts breaking. This means that Tuya devices may not trigger as expected and some sequences may not appear correctly when viewing the steps.

In some cases, unlinking and linking your account can resolve the issue, but not always.

I’m currently working with the Tuya support team to find a resolution and will post an update here once it’s resolved.

If this happens to your account, please don’t delete or modify your SEQUEmatic sequences. The steps may not appear correctly now with device names and statuses missing (see the screenshot below), but should be restored once the Tuya integration issue is resolved so it would be best to leave the sequence as it is for the moment.


Thanks for your patience while I work through this.

Comment

How to connect IFTTT to Tuya Smart Life

With the recent shutdown of the Tuya Smart Life service on IFTTT, many people are left wondering how to integrate their Tuya Smart Life devices with other smart devices around the home.

SEQUEmatic now supports direct integration with Tuya Smart Life. Combined with the IFTTT webhook service, SEQUEmatic can bridge that gap! Read on to learn how.

Link your Tuya account

First, you need to link your SEQUEmatic account to Tuya. Navigate to your settings page and click the Linked Services button.


Next, click Link account next to the description of the Tuya Smart Life service.


You will be redirected to the secure Tuya Smart Life login page, where you should login with your Tuya credentials.


Tuya will explain what it means to link your account, then you will need to click Confirm authorization to complete linking.


Once linking is complete, you will be redirected back to the Linked services page. You’ll notice the link which previous read Link account now reads Unlink account, confirming your account was successfully linked.

If you ever wish to disconnect your Tuya account from SEQUEmatic, you should return to this page and click the Unlink account link.


Create your sequence

If all you want to do is hook a service from IFTTT into your Tuya Smart Life device, then the SEQUEmatic sequence is very simple. However, if you’re new to SEQUEmatic I’d encourage you to explore the other step types and see what else you can achieve. Sequences can be very powerful and you might be able to create an even better home automation than you had before!

Anyway, the sequence you need will look like this. You can also view this here in the shared sequence library.


Let’s go through this step by step. First you should select the IFTTT webhook trigger. Enter anything for the event name, as long as it’s meaningful to you. Leave all the parameter fields blank. Here’s what I used in the sample sequence:


Then, you just need one other step which is the Tuya Smart Life step. I’ve chosen a single device, but you could also use a device group or scene. Select the action you want to perform or the property to modify as well as the new value, and that’s it! Here’s the step I created in the sample sequence.


While you’re here, if you want multiple Tuya Smart Life devices to be triggered, you can add any number of Tuya Smart Life steps to the sequence.

The IFTTT applet

Next head to IFTTT and create a new applet. The trigger, or if this component, should be the other smart device which should cause your Tuya Smart Life device to be triggered. In this example I’m using an eWeLink plug. Set up the trigger as you need, and then click next to create your action.

The action, or then that component, will use the webhooks service. There’s only one action available in this service, the make a web request action.


The only field you need to set in this action is the URL field. Head back to the SEQUEmatic sequence, and copy the URL provide in the trigger. Once copied, paste it into IFTTT.


Click through to save the applet, and your finished product should look something like this.


Now, when the other device (in this example the eWeLink plug called water feature) fires, it will make a webhook call to SEQUEmatic and trigger the sequence. The SEQUEmatic sequence will then control your Tuya Smart Life device!

If you have any questions getting set up, head over to the Q&A forums, post in the comments below or contact me here.

Comment

Previous pageNext page
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.