We like to call this “workflow as code” because our user interface gets out of your way and lets you switch seamlessly between drag-and-drop and coding scripts in Python and JSON, without loss of information.
You can select from a comprehensive library of connectors and automated actions to connect any part of your cloud. You can select from a list of actions to create a workflow to solve a specific business task such as fixing an incident that caused the website to be down.
Workflows are flexible
Workflows can be a combination of actions, operators and even nested workflows. As you edit a workflow, Fylamynt will automatically fill in all the context needed for an action or a conditional operation. For example, the region, environment and input for specific actions (e.g. scanning a Terraform state file and importing all states) are autofilled.
Actions in a workflow are specific to performing service tasks. Fylaymnt provides pre-built actions and service integrations, or connectors, to simplify and speed workflow deployment.
Services can include:
SaaS services such as DataDog, Splunk, etc.
SaaS execution services such as Terraform, CloudFormation, Ansible, etc.
Public cloud services such as CloudWatch, RDS, etc.
Workflows in action
Workflow triggers can be manual, a “job” that is run on a schedule or an alert from monitoring service or tool (e.g. Splunk On-Call or PagerDuty alerts)