2. Getting to know workflows

Fylamynt can help you tap into that right-brain creativity, with a visual and intuitive interface that makes automated workflow creation as easy as, well, drag and drop.

The workflow editor page offered in the product is where all the magic lies. You can simply drag, drop and connect nodes on the canvas to create a workflow that suits your needs.

How do I reach the Workflow Editor Page (Canvas)?

1. Click on "Workflows" available in the left panel of the product.

2. 
3. Click on "New Workflow +" available in the top right corner.

4. Enter a suitable workflow name

   1. Workflow name cannot start with aws, amazon, amzn

5. 
6. Select the trigger type.

   1. Trigger types are made available for selection once the integration is configured and authorized on the settings page.

7. Click on "Create Workflow"

8. 
9. There are three panels on this page that will help you create your workflow.

   1. Left Panel - Library of integration actions. Click on the "+" icon in the top left to open and close the library.

      1. 
   2. Center Panel - Canvas where you can drag and drop actions to connect them and create a workflow.

   3. Right Panel - Action configuration panel where you get to enter the input parameters and explore the output parameters for a particular action that you have selected.

      1. 

Please go through the following sections for more information on workflows.

1. Workflow as Code

2. Workflows are flexible

3. Workflows in action

Workflow as Code

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, controls, operators, and even nested workflows.

When action nodes are connected, the outputs of previous nodes can be consumed in downstream nodes. For example, the Instance ID of an EC2 instance that you want to stop, due to low resource utilization, can be retrieved from the output of Trusted Advisor.

Conditional nodes can also be added to evaluate variables and based on the result set the downstream action node destination. For example, let's add a conditional node to verify if AWS Trusted Advisor identified any low utilization EC2 instances. If no instances are identified then end workflow, otherwise stop the instances using the instance IDs extracted from Trusted Advisor.

Workflows also feature version control, which creates a new version of your workflow on every new save. You can manage your version by rolling back or deleting it.

Actions in a workflow are specific to performing service tasks. Fylamynt provides pre-built actions and service integrations, or connectors, to simplify and speed up workflow deployment.

Services can include:

• SaaS services such as DataDog, New Relic, Splunk, Sumo Logic, etc.

• SaaS execution services such as Terraform, Pulumi, CloudFormation, Ansible, etc.

• Public cloud services such as CloudWatch, EventBridge, EC2, RDS, etc.

• Kubernetes and Container services such as EKS, ECS, GKE, etc

Workflows in action

The following methods to run workflows in Fylamynt are supported:

• Manually

  • From the Workflow Editor page

    • 
  • From the workflow details page

    • 
• Scheduled

  • From the Workflow Editor page

    • 
    • 
  • From the workflow details page

    • 
• Automatically

  • Workflows can automatically be triggered from native monitoring services.

  • When a new workflow is created, you will be prompted to select the Trigger type for your workflow.

    • 
  • Here are some examples of integration trigger types. Fylamynt is constantly adding new integrations so please refer to the integrations listed on the console page here for an accurate list.

    • Manual

    • AWS Health (Service)

    • CloudWatch (Event)

    • Datadog (Monitor)

    • Amazon EventBridge (Rule)

    • Humio (Repository)

    • Instana (Entity type & name)

    • New Relic (Policy)

    • OpsGenie (Service)

    • PagerDuty (Service)

    • Prometheus (Alert)

    • ServiceNow (Category)

    • Splunk On-Call (Team name & Escalation policy)

    • Webhook

The trigger type selected during the creation of the workflow can be changed on the fly from within the editor.