If a webhook is triggered, get a mobile notification
How this automation works
Control your TMT Chow gate remotely using a simple web request. This Applet runs whenever your Webhooks event is received and automatically closes the selected gate. It's perfect for automating garage or gate control setups and works seamlessly with TMT Chow devices. Note: This requires a reachable webhook endpoint (URL).
If
Trigger ingredients
EventName
Value1
Value2
Value3
OccurredAt
Then
Action fields
uuid
pincode
You might also like...
View more Applets
Related services
Create your own TMT Chow and Webhooks workflow
Create custom workflows effortlessly by selecting triggers, queries, and actions. With IFTTT, it's simple: “If this” trigger happens, “then that” action follows. Streamline tasks and save time with automated workflows that work for you.
25 triggers, queries, and actions
ChowHub Sensor 1
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This trigger fires when ChowHub sensor 1 triggered
ChowHub Sensor 2
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This trigger fires when ChowHub sensor 2 triggered
ChowHub Sensor 3
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This trigger fires when ChowHub sensor 3 triggered
ChowHub Sensor 4
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This trigger fires when ChowHub sensor 4 triggered
Closed
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This trigger fires when the gate complete closed
Closing
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This trigger fires when the gate start closing
Hall Sensor Abnormal
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This trigger fires when the gate motor hall sensor broken
Opened
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This trigger fires when the gate complete opened
Opening
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This trigger fires when the gate start opening
Overcurrent
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This trigger fires when the gate stopped by overcurrent protection
Photocell
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This trigger fires when the gate stopped by safety device activated
Receive a web request
Realtime trigger
Realtime Applets run after the trigger service notifies IFTTT of a new trigger event. Since IFTTT is notified proactively of new trigger events, realtime Applets normally run within a few seconds of a trigger event occurring.
This trigger fires every time the Maker service receives a web request to notify it of an event. For information on triggering events, go to your Maker service settings and then the listed URL (web) or tap your username (mobile)
Abnormal record
Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns recent 7 days abnormal record of device.
History of web requests received
Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns a list of times when the Maker service received a web request to notify it of an event. For information on querying events, go to your Maker service settings and then the listed URL (web) or tap your username (mobile)
Make a web request
Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns the status code from a request made to the provided URL. If the response body is in the correct format it will also return the body’s extracted values. Please see the documentation link on the Webhooks service page.
Make a web request with JSON response
Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns the JSON response body. You can use filter code to parse it. Please see the documentation link on the Webhooks service page.
Operation record
Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns recent 7 days record of device operation.
ChowHub1
Action
An action is the task your Applet carries out after the trigger occurs. It defines what happens as the result of your automation and completes the workflow.
This action will help you to trigger Chow Hub 1
ChowHub2
Action
An action is the task your Applet carries out after the trigger occurs. It defines what happens as the result of your automation and completes the workflow.
This action will help you to trigger Chow Hub 2
ChowHub3
Action
An action is the task your Applet carries out after the trigger occurs. It defines what happens as the result of your automation and completes the workflow.
This action will help you to trigger Chow Hub 3
ChowHub4
Action
An action is the task your Applet carries out after the trigger occurs. It defines what happens as the result of your automation and completes the workflow.
This action will help you to trigger Chow Hub 4
Close
Action
An action is the task your Applet carries out after the trigger occurs. It defines what happens as the result of your automation and completes the workflow.
This action will help you to close the gate
Make a web request
Action
An action is the task your Applet carries out after the trigger occurs. It defines what happens as the result of your automation and completes the workflow.
This action will make a web request to a publicly accessible URL. NOTE: Requests may be rate limited.
Open
Action
An action is the task your Applet carries out after the trigger occurs. It defines what happens as the result of your automation and completes the workflow.
This action will help you to open the gate.
Abnormal record
Query
A query lets your Applet retrieve extra data that isn't included in the trigger, so that your automation can include more complete or useful information.
This query returns recent 7 days abnormal record of device.
ChowHub Sensor 1
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This trigger fires when ChowHub sensor 1 triggered
ChowHub Sensor 2
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This trigger fires when ChowHub sensor 2 triggered
ChowHub Sensor 3
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This trigger fires when ChowHub sensor 3 triggered
ChowHub Sensor 4
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This trigger fires when ChowHub sensor 4 triggered
ChowHub1
Action
An action is the task your Applet carries out after the trigger occurs. It defines what happens as the result of your automation and completes the workflow.
This action will help you to trigger Chow Hub 1
ChowHub2
Action
An action is the task your Applet carries out after the trigger occurs. It defines what happens as the result of your automation and completes the workflow.
This action will help you to trigger Chow Hub 2
ChowHub3
Action
An action is the task your Applet carries out after the trigger occurs. It defines what happens as the result of your automation and completes the workflow.
This action will help you to trigger Chow Hub 3
ChowHub4
Action
An action is the task your Applet carries out after the trigger occurs. It defines what happens as the result of your automation and completes the workflow.
This action will help you to trigger Chow Hub 4
Close
Action
An action is the task your Applet carries out after the trigger occurs. It defines what happens as the result of your automation and completes the workflow.
This action will help you to close the gate
Closed
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This trigger fires when the gate complete closed
Closing
Polling trigger
Polling Applets run after IFTTT reaches out to the trigger service and finds a new trigger event. These trigger checks occur every 5 minutes for Pro and Pro+ users, and every hour for Free users.
This trigger fires when the gate start closing
Build an automation in seconds!
If
Select a trigger the automation will use
Then
Select an action the automation will perform
You can add delays, queries, and more actions in the next step!
More on TMT Chow and Webhooks
About TMT Chow
Chow! Create full house of wonderfulness.
Chow! Create full house of wonderfulness.
About Webhooks
Learn to use webhooks and integrate other services on IFTTT with your DIY projects. You can create Applets that work with any device or app that can make or receive a web request. If you'd like to build your own service and Applets, check out the IFTTT Developer Dashboard. Connect a webhook to any of the 750+ apps and services on IFTTT.
Learn to use webhooks and integrate other services on IFTTT with your DIY projects. You can create Applets that work with any device or app that can make or receive a web request. If you'd like to build your own service and Applets, check out the IFTTT Developer Dashboard. Connect a webhook to any of the 750+ apps and services on IFTTT.