Close menu
Explore Plans
Mobile menu Close menu
Back

Fing to Merik integrations

Automate your workflows between Fing and Merik with IFTTT.

Create your own Fing and Merik 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.

41 triggers, queries, and actions

A Fingbox goes offline

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 fingbox get disconnected from the network. This is usually an indication that the network connectivity is not working

A Fingbox is back online

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 fingbox get re-connected to the network. This is usually an indication that the network connectivity came back online

A user arrived

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 user is detected in or nearby your network.

A user left

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 user is no more detected nearby.

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

Device is OFF

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 device is detected OFF (offline) in your network.

Device is ON

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 device is detected ON in your network.

Everyone left

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 no one of a user group is detected in or nearby your network.

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

Internet IP 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 your public Internet IP changes.

Internet Outage event happened

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.
Trigger requires you only to have a free Fing Account, you don't need a Fingbox to use this! Trigger fires when there is an Internet outage event on your ISP impacting your location, both when it starts and it is resolved.

History of A Fingbox is back online

Pro plus icon
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 when a fingbox get re-connected to the network.

History of a user arrived

Pro plus icon
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 when a user was detected in or nearby your network.

History of device is ON

Pro plus icon
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 when a device was detected ON in your network.

History of devices found

Pro plus icon
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 when a new device is detected in your network.

History of everyone leaving

Pro plus icon
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 no one of a user group is detected in or nearby your network.

History of Internet Outage events

Pro plus icon
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 events when there was an Internet outage event on your ISP impacting your location, both when it starts and it was resolved. You only need to have a free Fing Account, you don't need a Fingbox to use this!

History of internet speed drops

Pro plus icon
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 instances when internet speed dropped or slow down was detected, on download or upload channel. Note: this query will only return future events after this Applet is created.

History of someone arrived

Pro plus icon
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 when someone of a user group was detected in or nearby your network.

History of users left

Pro plus icon
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 time when a user was no longer detected nearby.

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

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.

Pause Internet access

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.
Suspend the access to internet for a given user or category.

Play LED effect

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 play a light effect on Fingbox LED.

Relay 1 - JANO

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 JANO

Relay 2 - JANO

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 JANO

Relay 3 - JANO

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 JANO

Relay 4 - JANO

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 JANO

Turn on Internet access

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.
Resume the access to internet for a given user or category.

A Fingbox goes offline

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 fingbox get disconnected from the network. This is usually an indication that the network connectivity is not working

A Fingbox is back online

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 fingbox get re-connected to the network. This is usually an indication that the network connectivity came back online

A user arrived

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 user is detected in or nearby your network.

A user left

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 user is no more detected nearby.

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

Device is OFF

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 device is detected OFF (offline) in your network.

Device is ON

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 device is detected ON in your network.

Everyone left

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 no one of a user group is detected in or nearby your network.

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 A Fingbox is back online

Pro plus icon
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 when a fingbox get re-connected to the network.

Build an automation in seconds!

You can add delays, queries, and more actions in the next step!

GET STARTED

How to connect to a Fing automation

Find an automation using Fing

Find an automation to connect to, or create your own!

Connect IFTTT to your Fing 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!
Get started

Upgrade your automations with

Start your free trial

More on Fing and Merik

About Fing

Fing helps you get more from your internet experience and smart home set-up. Connect with Fing Internet Outage Alerts and be in the know when your internet is down. Got a Fing monitoring unit? Fing's powerful presence detection technology uses your family's comings and goings to automate your favourite IFTTT-enabled devices and services.

Connect Fing

More integrations with Fing

About Merik

Merik specializes in access and automatic door solutions, offering products like garage door openers and industrial doors. Their IFTTT service seamlessly integrates Merik products with other online services, enabling custom automations, widget control, instant message notifications, and voice control for enhanced convenience and security.

Connect Merik

More integrations with Merik