What are Events?
Events within the Airkit platform contain a series of actions, which can be invoked in various ways. These actions can update variables, start voice & chat bots, alter the canvas, and much more.
What are different types of events?
There are a few types of events in the Airkit platform. These different types of events indicate how and where they can be invoked. The different types are:
- Starting Events → These start an Airkit Journey
- Journey Events → These are global events that can be initiated anywhere you can invoke an action
- Activity Group Events → These are events specific to an activity group (card, chat bot, & voice bot). Only actions within that group may initiate the event.
- Control Events → These are events specific to a control. They are typically associated with the activity of the control (For example: Button have a `Click` event, Text inputs have a `value changed` event)
- App APIs & Subscription Events → These are initiated whenever the api or subscription is triggered.
Every channel that allows for creation of an Airkit Journey has an associated event that is initiated when a new journey is created. These events allow for actions at the start of the journey that are specific to the channel.
For example, during the starting events of any voice or chat bots it is vital that you perform the actor setup. These could also allow you to dynamically decide what Web Flow the user starts on (like our Airbean demo!).
Journey events are globally available events that can be initiated anywhere. Typically, these are used to encapsulate meaningful, reusable sets of actions. For example, A reminder message event might log a metric, initiate a reminder message chat bot, and schedule a follow up reminder for the next day.
Activity Group Events
Activity Group events elevate meaningful interactions within that group that are meant to connect with the larger journey. These group specific events can also build inner group reusability, which is helpful when building templatized workflows.
Meaningful journey actions that occur within Activity group events will be illustrated in Journey Builder. One common use of Activity Group events is to create a final action when that Activity Group’s purpose is complete. For example, the end of a lead capture can initiate a `Submit` Activity Group Event that has the customer details as an input. This would signify the end of that activity group. This helps build reusable activity groups.
These events are tied to specific user interactions. Controls that allow for user interaction will have an actions tab in the inspector. These actions are specific to the control. For example, buttons have click events, but text inputs have `on enter` and `value changed` events.
On events that capture input from the user, that data will typically be available at `event.value`. In a text input, this will provide the characters the user has typed so far. For the scheduler, this will provide the selected timeslot. The type of data is control specific.
App APIs & Subscription Events
App APIs and Subscriptions initiate events if they successfully map to a journey. Data that is captured during the API / Subscription can be handed over to the event. These events allow you to trigger sets of actions associated with the incoming request.
For example, A Zendesk ticket status subscription would have an associated event that updated internal variables, and maybe notified the user if a meaningful event occurred. These provide you with the ability to perform asynchronous actions on specific journeys associated with these system events.