Node Syntax

      Node Syntax


        Article summary

        Node Syntax

        Different types of nodes require different input syntax. Each node configuration guide describes these requirements. However, we've also gathered them into one list below for ease of reference:

        Node

        Type

        Syntax Requirements

        API Pull

        Input

        [[deviceid]]

        Pull Data

        Input

        Field names require double square brackets. I.e., [[field name]]


        <<_deviceid_>>

        Trigger

        Input

        <<_deviceid_>>


        Strings require quotation marks. I.e., 'String'

        Extract Device ID

        Function

        Field.Subfield
        (Useful for extracting devices in nested payloads. The date field will use the extracted JSON)

        Filter

        Function

        Quotation marks and parentheses are not required.

        Rule Builder

        Function

        Field names require double square brackets. I.e., [[field name]]


        Strings require quotation marks. I.e., 'String'


        Custom Table lookup: <<ct_lookup>>

        Formula

        Function

        Field names require double square brackets. I.e., [[field name]]


        Custom Table lookup: <<ct_lookup>>

        Gauge

        Visualization

        Data Field Name: no parentheses required.


        Min/max values and range require double square brackets. I.e., [[maximum]]

        Level

        Visualization

        Data Field Name: no parentheses required.


        Full level value and range require double square brackets. I.e., [[maximum]]

        Monitor

        Visualization

        Data Field Name: no parentheses required.


        Range requires double square brackets. I.e., [[maximum]]

        Tabular Data

        Visualization

        Reference fields require double square brackets. I.e., [[field name]]

        Email

        Output

        <<_deviceid_>>

        <<_devicename_>>

        ((field name))

        SMS

        Output

        <<_deviceid_>>

        <<_devicename_>>

        ((field name))