﻿---
title: Core components
description: Learn about the core components that make up Elastic workflows.
url: https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/5583/explore-analyze/workflows/core-components
products:
  - Elastic Cloud Enterprise
  - Elastic Cloud Hosted
  - Elastic Cloud Serverless
  - Elastic Cloud on Kubernetes
  - Elastic Stack
  - Kibana
applies_to:
  - Elastic Cloud Serverless: Preview
  - Elastic Stack: Preview since 9.3
---

# Core components
Workflows are composed of three core elements that make workflow automation possible: triggers, steps, and connectors. Together, these components define when workflows run, what they do, and what external systems they connect to.

## Triggers

Triggers define _when_ a workflow runs. A trigger is an event or condition that initiates a workflow, such as an alert firing or a scheduled time occurring. Every workflow begins with a trigger.
Examples of triggers include:
- A user runs a workflow manually
- A specific time or interval is reached
- A detection alert is generated

For more information, refer to [Triggers](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/5583/explore-analyze/workflows/triggers).

## Steps

Steps define _what_ a workflow does. A step is an individual unit of logic or action within a workflow. Steps control how data moves, how decisions are made, and what results are produced. Workflows can contain one or more steps, executed in sequence.
For more information, refer to [Steps](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/5583/explore-analyze/workflows/steps).

## Connectors

Connectors define _where_ workflows can reach. A connector is the interface between Kibana and an external system, allowing workflows to act on or respond to events and services outside of Kibana.
For more information, refer to [External systems and apps steps > Connector-based actions](/elastic/docs-content/pull/5583/explore-analyze/workflows/steps/external-systems-apps#connector-based-actions).