Blink when you receive a WhatsApp message
Other popular blink(1) workflows and automations
-
15
-
-
New FB Link.
3
-
-
If ambient temperature rises above specific level, send blink event
-
-
My Facebook Post
1
-
-
Someone's at the door!
9
-
-
When Adafruit releases a new product, blink!
9
-
-
Current temp < 33
37
-
-
blink(1) when I miss a call from an important someone
21
-
-
Blink! New follower.
30
-
Create your own blink(1) and Bouncie 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
Bouncie was reconnected
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 Bouncie adapter is plugged back into the vehicle.
Geo-Circle was entered
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 vehicle enters one of its geo-circles.
Geo-Circle was exited
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 vehicle exits one of its geo-circles
Insurance expiration reminder
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 vehicle's insurance is expiring.
Trip was completed
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 new trip is completed.
Vehicle care event
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 vehicle has a care event.
Vehicle drove a long distance
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 vehicle drives a long distance. Distance can be configured on drives alert page in the Bouncie App.
Vehicle drove at unusual time
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 vehicle drives outside the time range specified. Time range can be configured on drives alert page in the Bouncie App.
Vehicle had frequent hard brakes
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 vehicle brakes hard frequently
Vehicle had frequent rapid accelerations
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 vehicle has many rapid accelerations during at trip
Vehicle had unusual fuel economy
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 vehicle fuel economy on a trip is out of the defined range.
Vehicle has low fuel
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 vehicle has low fuel.
Vehicle renewal
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 vehicle renewal occurs.
Vehicle was idle for a long time
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 vehicle was idle for a long time during a trip.
Vehicle was over maximum speed
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 vehicle accelerated above specified maximum speed. Maximum speed can be configured on drives alert page in the Bouncie App.
Vehicle's battery is low or critical
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 vehicle's low/critical battery event occurs.
Vehicle's check engine light comes 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 the vehicles check engine come on.
History of Bouncie reconnections
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 the Bouncie adapter was plugged back into the vehicle.
History of trips completed
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 trip was completed.
History of vehicle brakes hard frequently
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 vehicle brakes hard frequently.
History of vehicle drove a long distance
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 vehicle drives a long distance.
History of Vehicle idles
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 vehicle was idle for a long time during a trip.
History of vehicle renewals
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 vehicle renewal occurred.
History of vehicle's check engine light ons
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 the vehicles check engine come on.
History of when vehicle drove at unusual times
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 vehicle drove outside the time range specified. Time range can be configured on drives alert page in the Bouncie App.
Send blink event
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 send your blink(1) a new event.
Bouncie was reconnected
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 Bouncie adapter is plugged back into the vehicle.
Geo-Circle was entered
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 vehicle enters one of its geo-circles.
Geo-Circle was exited
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 vehicle exits one of its geo-circles
History of Bouncie reconnections
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 the Bouncie adapter was plugged back into the vehicle.
History of trips completed
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 trip was completed.
History of vehicle brakes hard frequently
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 vehicle brakes hard frequently.
History of vehicle drove a long distance
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 vehicle drives a long distance.
History of Vehicle idles
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 vehicle was idle for a long time during a trip.
History of vehicle renewals
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 vehicle renewal occurred.
History of vehicle's check engine light ons
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 the vehicles check engine come on.
History of when vehicle drove at unusual times
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 vehicle drove outside the time range specified. Time range can be configured on drives alert page in the Bouncie App.
Insurance expiration reminder
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 vehicle's insurance is expiring.
Send blink event
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 send your blink(1) a new event.
Trip was completed
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 new trip is completed.
Vehicle care event
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 vehicle has a care event.
Vehicle drove a long distance
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 vehicle drives a long distance. Distance can be configured on drives alert page in the Bouncie App.
Vehicle drove at unusual time
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 vehicle drives outside the time range specified. Time range can be configured on drives alert page in the Bouncie App.
Vehicle had frequent hard brakes
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 vehicle brakes hard frequently
Vehicle had frequent rapid accelerations
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 vehicle has many rapid accelerations during at trip
Vehicle had unusual fuel economy
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 vehicle fuel economy on a trip is out of the defined range.
Vehicle has low fuel
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 vehicle has low fuel.
Vehicle renewal
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 vehicle renewal occurs.
Vehicle was idle for a long time
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 vehicle was idle for a long time during a trip.
Vehicle was over maximum speed
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 vehicle accelerated above specified maximum speed. Maximum speed can be configured on drives alert page in the Bouncie App.
Vehicle's battery is low or critical
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 vehicle's low/critical battery event occurs.
Vehicle's check engine light comes 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 the vehicles check engine come on.
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 blink(1) automation
Find an automation using blink(1)
Find an automation to connect to, or create your own!Connect IFTTT to your blink(1) 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 Discord and Instagram
About blink(1)
ThingM's new blink(1) is a small USB light to give you glanceable notice of anything on your computer or the internet. It packs three dimensions of information (color, brightness, and pattern) into a single tiny package that fits into any USB port on nearly every device.
ThingM's new blink(1) is a small USB light to give you glanceable notice of anything on your computer or the internet. It packs three dimensions of information (color, brightness, and pattern) into a single tiny package that fits into any USB port on nearly every device.
About Bouncie
Revolutionize your car ownership experience by staying connected with Bouncie.
Revolutionize your car ownership experience by staying connected with Bouncie.