TABLE OF CONTENTS

Events

An event is an action that is automatically perform based on an Event Trigger. For example, you could use an event to send an email whenever a user submits a form. In this case, the trigger would be the submission of the form, and the event would be the action of sending the email. Events can also be included in workflows. For example, you could use an event to change a status once a workflow task is complete.

Event Components

Events have two components: a trigger and an action.

  • The trigger determines when the event will occur. For example, an event can be triggered when a user creates a folder or uploads a file, when a user submits a form, or when a row is added to a data set.
  • The action defines what will happen when the event is triggered. For example, the event could reassign a task, change a status, or activate a workflow.

An event can have multiple triggers and actions. An event will automatically execute when at least one of the triggers occurs. When the event is triggered, all of the actions will be performed. Note that you can temporarily disable an event if you want to prevent it from executing.

Examples

Let’s look at a few examples of events you might want to create.

  • When a file is uploaded (trigger), activate a workflow (action).
  • When a status is changed (trigger), send an email notification (action).
  • When a form question is answered (trigger), create an attribute to capture the answer as a variable (action). This variable can be used in subsequent automations.


A Note on Event Inheritance

In use cases where there are multiple companies in the Blue Relay system, events that are created and configured at the parent-company level can also be triggered from a child company. However, events created within the child company will not be triggered from the parent company. When an event needs to be triggered regardless of the active company, it should be created within the parent company.