---
title: "Device triggers"
slug: "device-triggers"
tags: ["Devices", "Triggers", "Device Triggers", "Devices, Systems, and Machines"]
status: "update"
updated: 2026-10-27T17:10:41Z
published: 2026-10-27T17:10:41Z
canonical: "support.tulip.co/device-triggers"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://support.tulip.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Device triggers

*Learn how to set up triggers that integrate devices on the production floor.*

Device Triggers are triggers that fire when an event happens in a sensor on the production floor that is connected to Tulip.

With triggers, you can add external devices from Tulip’s [device list](/r230/docs/supported-devices) to apps. [Additional conditions](/r230/docs/how-to-add-triggers-with-conditions-ifelse-statements) can be added to the trigger based on the data collected from the device.

## Add a device trigger

In general, Tulip recognizes three types of device events that trigger an action:

- A simple device signal (e.g. barcode scanner output)
- A GPIO signal (e.g. pin changes)
- An Analog to Digital (ADC) event (e.g. change in voltage)

Device output can be stored in Variables, initiate a specific action or do both.

NOTE

A device output might be a single value (e.g. a number) or multiple values (e.g several analog outputs). When you create logical conditions with device outputs, use the variable data and not the variable name.

Access device triggers in the Step Tab of the Side Pane. Click **Add** next to **Machines and Devices**.

![Step tab triggers](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Step%20tab%20triggers.png)

### Example

Below is an example device trigger:

![](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/How%20to%20Add%20Device%20Triggers_103722056.png)

WHEN

- "device" "barcode scanner" outputs at "this station"

THEN

- "Data Manipulation" "Store" "Device Output" "data" location: "new_variable"

## List of all device triggers

Here is a list of all device triggers that are available by default in Tulip. These are available within the **When** logic in the trigger editor:

- Analog Voltage Input
- Atlas Copco MTF 6000
- Barcode Scanner
- Barcode Scanner (DataMan TCP)
- Barcode Scanner (Optical)
- Bobe Box USB
- Bosch RFID
- Bosch Rexroth Nexo
- Caliper or Depth Gauge
- Cognex In-Sight
- Cognex Insight 2000
- Fluke 28X Multimeter
- Footpedal
- GPIO
- Generic Serial Device
- Ingersoll Rand QX
- Insize Multichannel Digital Caliper
- Kolver
- Mettler Toledo SevenExcellence
- Omega HH806
- Pam CF
- RFID Reader
- Scale (Brecknell PS25)
- Scale (Dymo M10 USB)
- Scale (Dymo USB scale)
- Scale (Ohaus)
- Serial (Player Only)
- Stealth Switch
- Telnet
- Temperature / Humidity Sensor (Lascar)
- Temperature / Humidity Sensor (Phidgets)
- Temperature Gun
- Torque Multi-Tool Open Protocol
- Torque Tool Open Protocol
- Zebra Network Printer
- analyzer-Q2
- e-Screw
- kolver2AE job information
- serial barcode scanner

NOTE

Additional built-in drivers may appear depending on your instance's configuration settings.

## Further reading

- [How to Add an Ohaus Scale and Store Output in a Variable](/r230/docs/how-to-add-an-ohaus-scale-and-store-output-in-a-variable)
- [Using the Cognex DataMan TCP Driver](/r230/docs/using-the-cognex-dataman-tcp-driver)
- [Using the Torque Open Protocol Driver](/r230/docs/using-the-torque-open-protocol-driver)

---

Did you find what you were looking for?

You can also head to [community.tulip.co](https://community.tulip.co/?utm_source=intercom&utm_medium=article-link&utm_campaign=all) to post your question or see if others have solved a similar topic!

**Trigger**

**Triggers** are groups of logic that are tied to an app event, such as step open, timer, widget interaction, etc. App builders can add triggers to **widgets**, **machines**, **devices**, **apps**, and **steps**.

**Triggers** can contain **actions**, **transitions**, and **conditions**.

**Variables**

**Variables** are a location to store app information. Variables have a specific type that must match the contents they can store.

Variables are only accessible within a single application and are cleared when the app is restarted or completed.

**Step Tab**

In the **Side Pane**, the **Step Tab** is where you can adjust all of the **Step-level** settings, including **Step Triggers,** Step background, Step resolution, and more.![](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Step%20Tab.png)

**Side Pane** **(Context Pane)**

The **Side Pane** is the configuration pane on the right side of the **App Editor** where steps, apps, and widgets can be configured. **Triggers** can be added to adjust widget behavior.![](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Context%20Pane.png)