This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision |
| indigo_2025.1_documentation:events_data_path_specifiers [2025/10/22 19:25] – davel17 | indigo_2025.1_documentation:events_data_path_specifiers [2025/10/22 20:50] (current) – [Indigo-Supplied Event Data] jay |
|---|
| You can chain these path strings as needed, such as //''some_json[3].a.foo[9]''//. NOTE: if a path string is not provided, Indigo will return the entire payload. Any path that includes a collection (like the lists and dicts above), Indigo will convert it to JSON and respond with that data. | You can chain these path strings as needed, such as //''some_json[3].a.foo[9]''//. NOTE: if a path string is not provided, Indigo will return the entire payload. Any path that includes a collection (like the lists and dicts above), Indigo will convert it to JSON and respond with that data. |
| |
| ==== Indigo-supplied Event Data ==== | ==== Indigo-Supplied Event Data ==== |
| |
| | We updated most of the built-in events (Triggers, Schedules, etc) to pass through the event data that's specific to those events. All events, regardless of what they are, will contain the following values: |
| | |
| | <code> |
| | { |
| | "event-indigo-id": 127375748, |
| | "event-type": "VariableValueChangeTrigger", |
| | "source": "server", |
| | "timestamp": "2025-08-07T14:13:54" |
| | } |
| | </code> |
| | |
| | The ''event-indigo-id'' is the Indigo ID for the trigger, schedule, or action group. The ''event-type'' is the IOM event type. ''source'' is how the trigger was fired, and ''timestamp'' is an ISO formatted ''datetime'' of the event. |
| | |
| | Each specific trigger/schedule/action group may add additional data that will assist you later in the event processing chain. The following blocks provide samples of event data that Indigo supplies for various events. |
| === Action Groups === | === Action Groups === |
| <code> | <code> |