Open EyeOpen gate on selected weekdays at 07:30 AM
Other popular EyeOpen workflows and automations
-
-
-
Close your EyeOpen gate when an iOS Shortcut starts
-
-
Close your EyeOpen gate automatically every day
-
-
Open your gate with Google Assistant and EyeOpen
-
-
Close your EyeOpen gate when a Webhook event is received
-
-
Ask Siri to Send email to IFTTT and open the gate
-
-
Open your gate with EyeOpen every day at a set time
-
-
Open your EyeOpen garage when an iOS Shortcut runs
-
-
Log EyeOpen gate openings to Google Calendar
-
Create your own EyeOpen and Timberwolf Server 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.
26 triggers, queries, and actions
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
Object value has changed
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 a Timberwolf Server object has changed.
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
Sensor 1 - Biitween
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 Biitween sensor 1 triggered
Sensor 2 - Biitween
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 Biitween sensor 2 triggered
Sensor 3 - Biitween
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 Biitween sensor 3 triggered
Sensor 4 - Biitween
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 Biitween sensor 4 triggered
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 Timberwolf object value changes
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 returns a list of value changes recorded after this query is created.
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.
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 gat
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.
Relay 1 - Biitween
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 Relay 1 in Biitween
Relay 2 - Biitween
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 Relay 2 in Biitween
Relay 3 - Biitween
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 Relay 3 in Biitween
Relay 4 - Biitween
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 Relay 4 in Biitween
Set value
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.
Set a Timberwolf Server object to a specified value. The selected Timberwolf Server will convert the textual value to the datatype of the target object. You can connect the target object to another subsystem like KNX, 1-Wire, Modbus, MQTT, HTTP or Timeseries
Switch off
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 set a boolean Timberwolf object false.
Switch on
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 set a boolean Timberwolf object true. You may connect the object on your Timberwolf Server to other services like KNX, 1Wire, Modbus oder MQTT.
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.
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 gat
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
History of Timberwolf object value changes
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 returns a list of value changes recorded after this query is created.
Object value has changed
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 a Timberwolf Server object has changed.
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.
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
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.
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
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!
GET STARTED
How to connect to a EyeOpen automation
Find an automation using EyeOpen
Find an automation to connect to, or create your own!Connect IFTTT to your EyeOpen account
Securely connect the Applet services to your respective accounts.Finalize and customize your Applet
Review trigger and action settings, and click connect. Simple as that!Upgrade your automations with
-
Connect to more Applets
Connect up to 20 automations with Pro, and unlimited automations with Pro+ -
Add multiple actions with exclusive services
Add real-time data and multiple actions for smarter automations -
Get access to faster speeds
Get faster updates and more actions with higher rate limits and quicker checks
More on EyeOpen and Timberwolf Server
About EyeOpen
Eyeopen is the premier choice for gate and door automation ecosystem. Eyeopen allow you to stay connect to your property at all times and keep an eye on what matters most to you.
Eyeopen is the premier choice for gate and door automation ecosystem. Eyeopen allow you to stay connect to your property at all times and keep an eye on what matters most to you.
About Timberwolf Server
The Timberwolf Server is a very powerful multi-protocol gateway with visualisation, logic, Influx time series database, graphical analysis with Grafana and extensible with Docker Containers.
The Timberwolf Server locally supports 10 protocols in parallel with tens of thousands of data points that can be linked and recorded at will with each other and with other IFTTT services.
Cloud based services meets local Smarthome installation.
Documentation about Timberwolf Server integration with IFTTT
The Timberwolf Server is a very powerful multi-protocol gateway with visualisation, logic, Influx time series database, graphical analysis with Grafana and extensible with Docker Containers.
The Timberwolf Server locally supports 10 protocols in parallel with tens of thousands of data points that can be linked and recorded at will with each other and with other IFTTT services.
Cloud based services meets local Smarthome installation.
Documentation about Timberwolf Server integration with IFTTT