When new data is added, or existing data is modified (eg: status of a service ticket is changed) or deleted
Periodically at a set time (eg: every Monday morning at 9 AM)
Events can be reused across bots. Depending on the data source some external configuration may be necessary.
An event represents a change to an entity (table).
In our example, as shown in the image below, the New Event is a “Data Change” event only triggered by additions to the “Employees” table.
External Data Change Events: If you want these events to fire based on manual/direct updates to the underlying data sources external configuration is necessary. Currently only Sheets and Salesforce data sources are supported. Please visit these links on information on how to do this with Sheets and Salesforce.
(Events generated due to any app action or as a result of data change due to an API call will fire without any external configuration.)
Below is an example of a “Schedule” event type. In the case below, where ForEachRowInTable is not enabled, you can select any event except “Data change” as a valid step type in the process. You may want to use this option if your process doesn’t rely on data in any table.
However, if the ForEachRowInTable option is enabled, the option to specify a filter condition appears. Use this option if you want to run a process for each row of data in the table.
Events are reusable components, they can be used inside multiple bots. In the events tab all the events have a reusability indicator (number on the bottom right) if that event is reused. The number tells you how many times is being used. In the example below, the "A new employees record is created" event is a shared component that is used in two bots.
Clicking on the number will show the list of bots where this event is reused:
Trying to delete an event that is used by any bot(s) will prompt a message indicating that: