# Workflow A **workflow** is a set of tasks that needs to be executed in sequence to evaluate a configuration as part of an [optimization study](https://docs.akamas.io/akamas-docs/3.1.3/akamas-reference/glossary/optimization-studies). A **task** is a single action performed within a workflow. Workflows allow you to automate Akamas optimization studies, by automatically executing a sequence of tasks such as initializing an environment, triggering load testing, restoring a database, applying configurations, and much more. These are examples of common tasks that can be performed by a task * Launch remote commands via SSH * Apply parameters values in configuration files * Execute Spark jobs via spark-submit API * Start performance tests by integrating with external tools such as Neoload Workflows are first-class entities that can be defined globally and then used in multiple optimization studies. Akamas provides several [workflow operators](https://docs.akamas.io/akamas-docs/3.1.3/akamas-reference/workflow-operators) that can be used to perform tasks in a workflow. Some operators are general-purpose, such as those executing a command or script on a specific host, while others provide native integrations with specific technologies and tools, such as Spark History Server or load testing tools. ## Construct The construct to be used to define a workflow is described on the [Workflow template](https://docs.akamas.io/akamas-docs/3.1.3/akamas-reference/construct-templates/using-workflows) page. ## Commands A telemetry provider is an [Akamas resource](https://docs.akamas.io/akamas-docs/3.1.3/cli-reference#clireference-operations) that can be managed via CLI using the [resource management commands.](https://docs.akamas.io/akamas-docs/3.1.3/akamas-reference/cli-reference/cli-reference-2) ## User Interface The Akamas UI shows systems in a specific top-level menu.

The list of tasks is displayed when drilling down to each specific workflow.