All Collections
User Guides
Insert Custom Fields inside Event's messages
Insert Custom Fields inside Event's messages

Include dynamic data from Devices and Variables inside your alerts.

Sergio M avatar
Written by Sergio M
Updated over a week ago

Ubidots Events Engine allows you to use custom fields about Devices, Variables and the Event itself into your alerts' messages and recipients. The following custom fields are currently supported:

  • Device ID: The ID of the device that contains the variable that triggered the event.

  • Device description: The description (in case it has one) of the device that contains the variable that triggered the event.

  • Device label: The device label of the device that contains the variable that triggered the Event.

  • Device name: The device name of the device that contains the variable triggered the Event.

  • Device properties: Properties of the device that contains the variable that triggered the Event. To specify the device property, double click on the custom field and type the property key after the "context" key. Example of a property with key = "city":

  • Last value: The latest value of the variable that triggered the Event.

  • Last value’s context: The context of the latest value of the variable that triggered the Event.

  • Last value's timestamp: Date and time of the latest value of the variable that triggered the Event.

  • Timestamp: Date and time of the value that triggered the Event. Technically, this could differ from "Trigger timestamp" by a few seconds, which is the time the Events Engine takes to process the Event conditions and trigger the Event.

  • Trigger timestamp: Date and time at which the Event was triggered.

  • Trigger value: The value of the variable that triggered the Event, at the moment of triggering.

  • Trigger value's context: The context of the value that triggered the Event.

  • Variable: A JSON-like object with the variable's data: name, ID, and properties.

  • Variable ID: Unique identifier of the variable that triggered the Event.

  • Variable name: Name of the variable that triggered the Event.

Custom fields are accessible from the Events actions:

Some Event actions might limit the amount of accepted Custom Fields.

Did this answer your question?