# Elsa Workflows
[](https://github.com/elsa-workflows/elsa-core/actions/workflows/packages.yml)
[](https://www.nuget.org/packages/Elsa/)
[](https://hub.docker.com/repository/docker/elsaworkflows/elsa-v3)
[](https://discord.gg/hhChk5H472)
[]( http://stackoverflow.com/questions/tagged/elsa-workflows )
[](https://gurubase.io/g/elsa)
[](https://deepwiki.com/elsa-workflows/elsa-core)
<!-- DeepWiki badge generated by https://deepwiki.ryoppippi.com/ -->
### [For Elsa 2, Click Here](https://github.com/elsa-workflows/elsa-core/tree/2.x)
## Introduction
Elsa is a powerful workflow library that enables workflow execution within any .NET application. Elsa allows you to define workflows in various ways, including:
- Writing C# code
- Using a visual designer
- Specifying workflows in JSON
### Try with Docker
To give the Elsa Studio + Elsa Server a quick spin, you can run the following command to start the Elsa Docker container:
```shell
docker pull elsaworkflows/elsa-server-and-studio-v3:latest
docker run -t -i -e ASPNETCORE_ENVIRONMENT='Development' -e HTTP_PORTS=8080 -e HTTP__BASEURL=http://localhost:13000 -p 13000:8080 elsaworkflows/elsa-server-and-studio-v3:latest
```
> This Docker image is based on a reference ASP.NET application that hosts both the workflow server and designer and is not intended for production use.
For any non-development deployment, inject a secure random JWT signing key through environment variables or a secrets manager instead of using committed appsettings values. For code-first hosts such as `Elsa.Server.Web`, set `Identity__Tokens__SigningKey`. For shell-based hosts, set the shell feature key, for example `CShells__Shells__Default__Features__Identity__SigningKey`.
By default, you can access http://localhost:13000 and log in with:
```
Username: admin
Password: password
```
### TLS and custom certificate authorities
All Elsa Docker images now ship with the operating system's certificate authority bundle baked in at build time. This means you can call public HTTPS endpoints such as `https://example.com` without any additional configuration.
If you need to trust a private or corporate CA, mount the certificate bundle into the container and reference it via `EXTRA_CA_CERT`:
```bash
docker run \
-v /path/to/company-ca.crt:/certs/company-ca.crt:ro \
-e EXTRA_CA_CERT=/certs/company-ca.crt \
elsaworkflows/elsa-server-and-studio-v3:latest
```
On startup, the container copies the certificate into `/usr/local/share/ca-certificates` and runs `update-ca-certificates`, making the trust available to .NET, OpenSSL, curl, and other system components. Multiple certificates can be provided by pointing `EXTRA_CA_CERT` at a directory containing `.crt` or `.pem` files.
In highly restricted environments where you cannot modify the system trust store, you can instead rely on the standard `SSL_CERT_FILE` or `SSL_CERT_DIR` environment variables:
```bash
docker run \
-v /path/to/company-ca-bundle.pem:/certs/custom.pem:ro \
-e SSL_CERT_FILE=/certs/custom.pem \
elsaworkflows/elsa-server-and-studio-v3:latest
```
> ℹ️ Installing the CA bundle adds roughly 300KB to the Debian-based images. No package managers run at container startup; all trust updates happen immutably at build time or via the mounted certificates shown above.
## Table of Contents
- [Documentation](#documentation)
- [Training](#training)
- [Known Issues and Limitations](#known-issues-and-limitations)
- [Features](#features)
- [Roadmap](#roadmap)
- [Use Cases](#use-cases)
- [Coding Workflows](#coding-workflows)
- [Designing Workflows](#designing-workflows)
- [Contributing](#contributing)
- [Support](#support)
- [Community Support](#community-support)
- [Professional Support](#professional-support)
## Documentation
[Elsa Documentation Website](https://docs.elsaworkflows.io/).
- [Core source and local development](core/docs/README.md)
- [Default Admin User bootstrap (shell + legacy feature system)](core/src/modules/Elsa.Identity/README.md)
- [Studio source and local development](studio/docs/README.md)
- [Extensions source and package boundaries](extensions/docs/README.md)
- [Official application hosts and images](apps/README.md)
- [.NET project templates](templates/README.md)
- [Consolidated 3.10 package proof and publication boundaries](docs/integration-program/consolidated-package-proof.md)
## Training
Prefer a guided path? The [Elsa+ training courses](https://www.elsaworkflows.io/elsa-plus/training) take you from the basics to advanced patterns, with hands-on labs.
## Known Issues and Limitations
Elsa is continually evolving, and while it offers powerful capabilities, there are some known limitations and ongoing work:
- Documentation is still a work in progress.
- Input/Output is not yet implemented in the Workflow Instance Viewer.
- Starting workflows from the designer is currently supported only for workflows that do not require input and do not start with a trigger; this is planned for a future release.
- The designer currently only supports Flowchart activities. Support for Sequence and StateMachine activities is planned for a future release.
- UI input validation is not yet implemented.
## Features
Elsa offers a wide range of features for building and executing workflows, including:
- Execution of workflows in any .NET application with support for .NET 6 and beyond.
- Support for both short-running and long-running workflows.
- A programming model loosely inspired by Windows Workflow Foundation.
- A web-based drag & drop designer with support for custom activities.
- Native support for activity composition, including activities like `Sequence`, `Flowchart`, and `ForEach`.
- Parallel execution of activities.
- Built-in activities for common scenarios, such as sending emails, making HTTP calls, scheduling tasks, sending and receiving messages, and more.
- Workflow versioning and migration via API.
- Easy integration with external applications via HTTP, message queues, and more.
- Actor model for increased workflow throughput.
- Dynamic expressions with support for C#, JavaScript, Python, and Liquid.
- Persistence agnostic, with support for Entity Framework Core, MongoDB, and Dapper out of the box.
- [Elsa Studio](studio/src): a modular Blazor dashboard app for managing and designing workflows.
## Roadmap
See [ROADMAP.md](./ROADMAP.md) for the current roadmap and [#3232](https://github.com/elsa-workflows/elsa-core/issues/3232) for historical roadmap discussion.
## Use Cases
Elsa can be used in a variety of scenarios, including:
- Long-running workflows such as order fulfillment and product approval.
- Short-running workflows such as sending emails and generating PDFs.
- Scheduled workflows such as sending daily reports.
- Event-driven workflows such as sending welcome emails when a user signs up.
## Coding Workflows
Elsa allows you to define workflows in code using C#. The following example shows how to receive HTTP requests and send an email in response:
```csharp
public class SendEmailWorkflow : WorkflowBase
{
protected override void Build(IWorkflowBuilder builder)
{
builder.Root = new Sequence
{
Activities =
{
new HttpEndpoint
{
Path = new("/send-email"),
SupportedMethods = new(new[] { HttpMethods.Post }),
CanStartWorkflow = true
},
new SendEmail
{
From = new("alic@acme.com"),
To = new(new[]{ "bob@acme.com" }),
Subject = new("Your workflow has been triggered!"),
Body = new("Hello!")
}
}
};
}
}
```
## Designing Workflows
Elsa allows you to define workflows using a visual designer. The following example shows how to receive HTTP requests and send an email in response:
## Contributing
We welcome contributions from the community and are pleased that you are interested in helping to improve the Elsa Workflow project! Here are the steps to contribute to our project:
### 1. Fork and Clone the Repo
To get started, you'll need to fork the repository to your own GitHub account. You can do this by navigating to the [Elsa Workflow GitHub repository](https://github.com/elsa-workflows/elsa-core) and clicking the "Fork" button in the top-right corner of the page. Once you have forked the repo, you can clone it to your local machine using the following command:
```bash
git clone https://github.com/YOUR_USERNAME/elsa-core.git
```
Replace `YOUR_USERNAME` with your GitHub username. For more information on forking a repo, check out the GitHub documentation [here](https://docs.github.com/en/github/getting-started-with-github/fork-a-repo).
### 2. Open the Shared Solution
Open the root `Elsa.sln` in Visual Studio, JetBrains Rider or Visual Studio Code. Core, Extensions, Studio and Apps have separate product roots. Core, Extensions and Studio use `src/`, `test/` and `docs/`; Apps keeps application hosts in `apps/src/`, container-policy tests in `apps/scripts/tests/` and documentation in `apps/docs/`. The root solution filters select focused development subsets while retaining required project dependencies.
- [Core development](core/docs/README.md): backend hosts, workflow modules and Core tests.
- [Extensions development](extensions/docs/README.md): extension modules, tests and samples.
- [Studio development](studio/docs/README.md): Blazor hosts, browser bundles and Studio tests.
- [Apps development](apps/README.md): official net10 hosts and six image profiles consuming released packages.
- [Templates development](templates/docs/README.md): independent Elsa 3 project-template pack and isolated starter smoke tests. Build `Elsa.Templates.slnf`, which selects `templates/Elsa.Templates.slnx`; Templates has navigation items only in the shared solution to preserve independent packaging.
Run build and test commands from the repository root. See [CONTRIBUTING.md](CONTRIBUTING.md) for the workflow and [AGENTS.md](AGENTS.md) for repository conventions. These source-development commands do not publish packages or change source-repository ownership.
### 3. Submit a PR with Your Changes
Once you have made your changes, commit them and push them back to your fork. Then, navigate to the original Elsa Workflow repository and create a new Pull Request. Ensure your PR description clearly describes the changes and any relevant information that will help the reviewers understand your contributions. For a detailed guide on creating a pull request, visit [Creating a pull request from a fork](https://docs.github.com/en/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork).
### 4. Open an Issue First
Before you start working on your changes or submit a pull request, please open an issue to discuss what you would like to do. This step is crucial as it ensures you don't spend time working on something that might not align with the project's goals or might already be under development by someone else. You can open an issue [here](https://github.com/elsa-workflows/elsa-core/issues).
This approach helps us streamline contributions and ensures that your efforts are aligned with the project's needs and priorities. We look forward to your contributions and are here to support you throughout the process. Thank you for contributing to the Elsa Workflow project!
## Support
There are various ways to get support for Elsa Workflows, ranging from community-driven channels to enterprise-level services.
### Community Support
Elsa has an active and helpful community where you can find support through multiple channels:
- [GitHub Issues](https://github.com/elsa-workflows/elsa-core/issues) for bug reports and feature requests.
- [GitHub Discussions](https://github.com/elsa-workflows/elsa-core/discussions) for open-ended conversations, questions, and community-driven support.
- [Discord](https://discord.gg/hhChk5H472) for real-time support and interaction with the Elsa community.
- [StackOverflow](https://stackoverflow.com/questions/tagged/elsa-workflows) for searching or asking technical questions.
### Professional Support
For organizations requiring professional support and long-term commitment, check out [Elsa+](https://www.elsaworkflows.io/elsa-plus), a growing ecosystem of premium services, tooling, and extensions around Elsa Workflows.