A FLO is another word for an automated workflow or integration. Within Azuqua, FLOs are represented by a Trigger Event followed by a series of Actions and Logic Functions which are executed from left-to-right in Azuqua’s Visual Designer.
FLOs allow you to connect to and from various endpoints (SaaS Connectors, APIs, or databases) and:
- Begin with a Trigger (Event, Schedule, or API Endpoint)
- Execute a series of logic functions or actions
- Produce desired outcomes by consuming inputs from Connectors or Actions
How it Works
FLOs vary in complexity and are not based on the amount of data moving through the system or on the number of executions. Rather, they are defined by the components that make up the scenario. A simple scenario may only contain a few cards, while a more complex scenario can contain dozens of cards depending on the use case requirements.
API Endpoints let users set up a webhook in minutes to receive data from an external service. This is helpful when external systems don’t have a readily available API.
Azuqua uses this type of FLO internally for scheduling Design Desk sessions. It eliminates the need for back-and-forth emails, allowing the support team to spend more time with customers and driving product engagement.
A Scheduled FLOs run at a specific time or at recurring intervals specified by the user. This functionality is ideal for reporting, project auditing, or performing tasks that are independent of an external event.
This type of scenario saves the product and development team hours each week that were previously spent manually updating and communicating status changes on work items.
Application Events let users build automations that are triggered by an action or event that take place within an application. This includes new records, updated fields, or attachments.
This scenario helps support teams that use different applications, allowing each team to use their tool of choice resulting in improved speed and accuracy of ticket resolution.