General principles for triggers and actions

IntuiFace Composer gives you the ability to select triggers and associate them with a series of actions. This association between triggers and actions is key to the no-code visual programming capability of IntuiFace. It enables you to create not just interactive presentations but true interactive applications with their own custom behavior and logic.

Triggers are events that occur in your experience. These events can be a user touching the display, the completion of a timer, changes in state of assets, collections and other elements in your experiences or any alert generated by external services accessed via interface assets.

Actions are events you can force to occur in reaction to a trigger. An action can be:

  • play a video
  • turn a page
  • move to another scene
  • rotate the display
  • execute function xxx exposed by a third party service
  • etc.

These actions can apply to any item in your experience - such as assets and collections - as well as to any external service or device accessible via an interface asset.

To better understand triggers and actions, have a look at the video below:


The simplest example of a trigger is when this button is pressed. Another type of trigger is a timer, such as when 5 seconds have elapsed. A third example is when this video reaches its end.

IntuiFace comes with many different triggers. Read Triggers overview for more details.

Actions, both local and remote

When "this button is pressed" occurs, an action can be triggered as a result. In fact, one trigger can activate any number of actions, enabling a virtually unlimited range of possibilities to make your experiences more lively and interactive.

Most actions will apply to elements in the same project (typically in the same scene as the element that activated the corresponding trigger). Actions applying to elements in the same experience are called local actions. To understand how to link triggers to actions, read Linking triggers to actions in Composer for more details.

IntuiFace comes many different actions. Read Actions overview for more details.

IntuiFace also enables multiple experiences to communicate with one another. Triggers in one experience can initiate actions in one or more distinct experiences. These actions are called remote actions. To understand how to link triggers to remote actions, read Creating Remote actions in the Composer for more details.

Remote actions are an advanced feature of IntuiFace. Please take some time to get familiar with triggers and actions before using them.

Remote actions enable the remote control of experiences over a network (Ethernet or Wi-Fi). Remote actions can be triggered not only by elements in your project but also by any third-party application on the same network. These calls are enabled by a simple URL-based syntax whose formalism is described here. In either case, all you need to know is the name of the target experience or, at the very least, the name of the computer on which the experience is running.

As it is possible for a single trigger to initiate actions in multiple remote experiences at the same time, this enables action synchronization between experiences, such as advancing all experiences at once to the same scene.

Illustrating the power of remote actions is the IntuiFace Remote Control for iOS and Android (aka. IntuiPad). IntuiPad enables you to remotely control your experiences from a tablet or other mobile device. Control is not just limited to Next Scene, Previous Scene and the like. You can actually entirely manipulate your remote experience on your handheld device. Read Remote control for iOS and Android for more details.

For a list of known limitations and recommendations for triggers and actions, visit this page.