Serial Trigger

The Serial Trigger will trigger a workflow whenever the Edge Compute device receives enough data via Serial to satisfy the configured trigger.

Node Properties

The Serial Trigger has several pieces of configuration in order to successfully listen for data.

• Serial Path: (Required) The serial port to listen on.
• Baud Rate: (Required) The baud rate, speed of communication over a data channel, which by default is 9600. For agent versions prior to 1.19.2 the following are accepted baud rates: 110, 300, 600, 1200, 2400, 4800, 9600, 14400, 19200, 38400, 57600, 115200, 128000, 256000. As of agent version 1.19.2 you may specify any positive integer for this field.

In the Gateway Edge Agent versions prior to 1.19.0, the following options are defaulted:

• Data Bits: 8
• Stop Bits: 1
• Parity: none
• RTS/CTS: false

However, in versions 1.19.0 and higher you may specify these options.

• Parity: (Required) The parity, whether or not a parity bit is set and its value. By default, this is none. Other valid values include even, odd, mark, and space.
• Data Bits: (Required) The number of bits per character, set to 8 by default. Other valid values include 5, 6, and 7.
• Stop Bits: (Required) The number of stop bits to signal the end of a character. Default is 1, may also be set to 2.
• RTS/CTS Handshake: (Required) Boolean that indicates whether RTS/CTS handshaking is in use. Default is false.
• Write After Port Opens: (Optional) Field where after the port opens this string will be written once. It will also be encoded using the Output Ending field.
• Write On Open Encoding: (Required if a value is set for Write After Port Opens) This denotes the encoding of the "Write After Port Opens" field. The following are valid character encoding options: ASCII, UTF-8 (default), UTF16LE, Base64, Binary, Hex. This field has been added as of agent version 1.19.2.
• Parse Method: (Required) By default, the value is Delimiter. This field can either be Byte Length or Delimiter, and it tells the serial port listener how to chunk up the data as it is received.
• Delimiter: This field is required if the parse method is Delimiter. The Serial Trigger fires with the serial data received once the delimiter is encountered. This delimiter will not be included in the serial data on the payload.
• Delimiter Encoding: (Required if Parse Method is set to Delimiter) This denotes the encoding for the delimiter. The following are valid character encoding options: ASCII, UTF-8 (default), UTF16LE, Base64, Binary, Hex. This field has been added as of agent version 1.19.2.
• Byte Length: This field is required if the parse method is Byte Length and it is the number of bytes to wait for before firing the trigger.
• Output Encoding: (Required) This denotes the encoding for the received serial message. The following are valid character encoding options: ASCII, UTF-8 (default), UTF16LE, Base64, Binary, Hex.

Payload

The payload will include the following under the data object ...

• path: The serial port path that the data was received on.
• serial: The data that was received from the serial port up until the delimiter was hit.

Given a serial message received on port /dev/ttyUSB0 with the contents Hello, Serial!, a Serial Trigger workflow payload will look like the following:

▶
(root){} 17 keys
▶
agentEnvironment:{} 1 key
agentVersion:"1.31.0"
applicationId:"555555555555eeeeeeeeeeee"
applicationName:"My Great Application"
▶
data:{} 2 keys
path:"/dev/ttyUSB0"
serial:"Hello, Serial!"
▶
device:{} 8 keys
deviceId:"222222222222bbbbbbbbbbbb"
deviceName:"My Great Device"
▶
deviceTags:{} 2 keys
flowId:"333333333333cccccccccccc"
flowName:"My Great Workflow"
flowVersion:"myFlowVersion"
▶
globals:{} 3 keys
isConnectedToLosant:true
time:Tue Aug 19 2025 14:48:10 GMT+0000 (Coordinated Universal Time) (Date object)
triggerId:"<unique trigger ID>"
triggerType:"serial"