> For the complete documentation index, see [llms.txt](https://v4.elsaworkflows.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://v4.elsaworkflows.io/essentials/readme.md).

# Elsa 4 documentation

Elsa lets you describe a workflow, publish it, run it, and inspect what happened. Elsa 4 is preview software. These pages introduce the reference server and visual client, with a small local workflow you can try.

Using Elsa 3? Continue with the [Elsa 3 documentation](https://docs.elsaworkflows.io/). Check the version before applying an Elsa 4 example to an existing application.

Choose a path:

* [Try Elsa locally](/essentials/essentials/quickstart.md), then [create your first workflow](/essentials/essentials/first-workflow.md).
* [Essentials](/essentials/essentials.md) for the server, source-build instructions, and architecture.
* [Extensions](/extensions/extensions.md) for optional modules and their extension points.
* [Studio](/studio/studio.md) for the visual client and the documented Workbench pairing.

`Elsa.Workbench` is a reference host that composes Elsa features. A custom host can include a different set of capabilities. Studio is the visual client used with that server; check the server and Studio versions together.

The quickstart uses an explicitly recorded image pair. Other source guides may describe current development rather than a released package. Each verification record applies to its named revisions and environment.

These pages are maintained in the Foundation repository. [Propose a documentation change](/contributing/contributing.md) through GitHub.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://v4.elsaworkflows.io/essentials/readme.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.