Event Studio
Aisera’s Event Studio empowers customers to build robust AI automations triggered by a wider range of events, both internal and external. This update enables citizen developers to streamline workflows without writing a single line of code.
Machine-Triggered Workflows: Define automations that get triggered automatically based on events generated by external machines or systems. This enables powerful integrations and streamlined data-driven processes.
Customizable Data Types and Events: custom data types mapped to events can be defined to seamlessly integrate with any external system’s events, ensuring your workflows handle data precisely as needed.
Out-of-the-Box Support for Internal Events: Get started quickly with built-in data types and events for internal Aisera activities, like audit events. Leverage this functionality to automate internal tasks and gain deeper insights into system behavior while offering downstream integration with your operational systems.
Scheduled Automation Triggers: Define automations to trigger on a specific schedule, enabling proactive workflows that run at designated intervals.
Event Filtering for Granular Control: Filter events based on specific criteria to ensure your workflows only trigger when the right conditions are met.
Zero-Code Deployment: Build and deploy powerful automations entirely within the no-code interface, eliminating the need for coding expertise or code deployments.
Complete the following steps to define a Data Type:
Select Settings > Data Type to define a new Data Type.
Configure the Data Type to receive events from external systems and map the incoming payload to its fields - "$" represents the incoming payload. OOTB data types are available for internal events, such as Audit History.
For external systems, associate Data Types with Data Sources to normalize incoming data for processing from multiple sources.
Complete the following steps to create the Event Trigger:
Choose Settings > Event Studio to select or create an Event Trigger.
For a new Event Trigger, choose the Event Name, Trigger Type, and Trigger Status.
Associate your Data Type, Event Type, and Triggering Condition.
Specify the Workflow that will handle the event, and designate the Workflow Input Mapping.
Complete the following steps to create an Event Source:
Applicable to external sources only
Configure the source system to send events to the receiver configured above. The configurations vary by source system, but require the following:
Receiver endpoint url: this is available on the details page of the associated Data Source.
"app-key": this is available on the details page of the associated Data Source.
"event-type": this is one of the "Supported Event Types" defined on the Data Type. It is then used in step 2 of the Event Trigger configuration to filter incoming events.
The configurations steps for a number of source systems are also available on the Event Trigger details page.
See also: Setting up Ticket Concierge with Event Studio.
Last updated