Hello and welcome to this video overview of the MUSE Automator node pallet.  This will be a short outline on the nodes that are unique to MUSE and their functions within an Automator project. 
The first node that we will talk about is the Controller node. The Controller node provides your flows simulator or MUSE controller context and programmatic access to the devices that have been added to the controller.  Every project that runs on a MUSE controller must have a Controller node.
The next node in the Muse Automator pallet is the Status node. The Status node is used to get the status or state of a specific device parameter.  The Status node does not provide unsolicited feedback.  It provides the state or value of the requested parameter when the Status node is triggered. 
Below the Status node, we have the Event node.  The Event node is used to listen for changes in the state of a parameter. When the Event node is triggered by a change in a monitored parameter, it provides that unsolicited data to the project and begins the chain of a flow.
The last MUSE Automator node in the pallet is the Command node. This node is used to control first party Harman devices, interact with programming modules, or send strings through first party devices to control third party devices.
Notice, the remaining nodes in this section have all been greyed out.  The Control Panel, UI Control, UI Feedback, and Navigate nodes have all been deprecated and should no longer be used.  They still exist so that if projects created in older versions of Automator are downloaded, the program can recognize them and inform you of the differences between the new and old versions of the node.
Moving down into the Touch Panel node pallet, we have the Control Panel node. The Control Panel node is used to add touch panels to the flow as well as create panel groups. Each touch panel and group requires its own Control Panel node.
The next node in the Touch Panel pallet is the UI Control node. The UI Control node is used to trigger button and level events from the touch panel file. 
Moving on, we have the UI Feedback node. The UI Feedback node is used for updating feedback on the touch panel, such as changing button states, level values, or button text. 
The final node is the UI Navigation node. This UI Navigation node is used to change which page is displayed on your touch panel. With this, you can execute page flips, show and hide popup pages, or send custom commands to your touch panel.