Path specifiers use a specific syntax and require knowledge about the event data you'll be receiving from the event. For example, given this Indigo event data:

{
    "foo": 1234567890,
    "bar": "Baz",
    "data": ["Thing 1", "Thing 2"],  # a list
    "more_data": {'a': 1, 'b': 2},  # a dictionary
    "timestamp": "2025-08-07T14:32:21",
}

You could use path specifiers like these to have the associated data inserted into the variable you chose (leave off the quotes):

• bar equals “Baz”
• data equals [“Thing 1”, “Thing 2”]
• more_data['b'] equals {'a': 1, 'b': 2}

So setting the path specifier to one of the above, would reference/access the corresponding value shown. If you want to go deeper into the payload, specifiers can be chained together like this:

{
    "foo": 1234567890,
    "bar": "Baz",
    "data": [
        "Thing 1",
        [
            "Thing A",
            "Thing B",
            "Thing C"
        ]
    ],
    "more_data": {
        "a": 1,
        "b": 2,
        "c": [
            1,
            2,
            3,
            4,
            5
        ]
    },
    "timestamp": "2025-08-07T14:32:21"
}

You can go deeper like this (again, leave off the quotes):

• data[0] equals “Thing 1” # The index of the list element, the index starts at zero
• data[1][2] equals “Thing C” # The second element (index 1) of “data” is a list and the third element (index 2) of that list is “Thing C”
• more_data.a equals 1 # The value of key “a” is 1
• more_data.c[3] equals 4 # The value of key “c” is a list and the fourth element (index 3) of that list is 4

You can chain these path specifiers as needed, such as some_json[3].a.foo[9]