> For the complete documentation index, see [llms.txt](https://developer.emporix.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.emporix.io/vsm-guides/value-stream-designer.md).

# Value Stream Designer

- [Value Stream Components](https://developer.emporix.io/vsm-guides/value-stream-designer/process-components.md): Learn about the building blocks of value streams.
- [Triggers](https://developer.emporix.io/vsm-guides/value-stream-designer/process-components/triggers.md): Learn about triggers that initiate value streams.
- [Process steps](https://developer.emporix.io/vsm-guides/value-stream-designer/process-components/process-steps.md): Learn about process steps—scenarios, subflows, cloud functions, and AI agents.
- [Conditions](https://developer.emporix.io/vsm-guides/value-stream-designer/process-components/conditions.md): Learn how to use filters, branching, and looping conditions to control triggers and process steps.
- [Creating a Value Stream](https://developer.emporix.io/vsm-guides/value-stream-designer/creating-value-stream.md): See how to design your custom process.
- [Integration with Make](https://developer.emporix.io/vsm-guides/value-stream-designer/integration-with-make.md): VSM uses Make's functionality for configuration of value streams. Learn more about the tool.
- [VSM and CE Make Modules](https://developer.emporix.io/vsm-guides/value-stream-designer/integration-with-make/make-modules.md): VSM Make modules bring specific functionality and are responsible for specific actions. Get familiar with the VSM-specific modules available in Make.
- [Configuring a Connection between VSM and Make Modules](https://developer.emporix.io/vsm-guides/value-stream-designer/integration-with-make/configuring-make-connection.md): Learn how to establish a connection between VSM and Make.
- [Process Context](https://developer.emporix.io/vsm-guides/value-stream-designer/process-context.md): Process context plays a significant role in managing value streams. Learn the details.
- [Datastore](https://developer.emporix.io/vsm-guides/value-stream-designer/datastore.md): Build and use a datastore to keep your data for easy reuse.
- [Data Flow between VSM and Celonis](https://developer.emporix.io/vsm-guides/value-stream-designer/celonis-data-flow.md): See how VSM value streams integrate with Celonis through Make scenarios, enabling signal-based triggers and action feedback for seamless data exchange.
- [Retrieving Data from Celonis](https://developer.emporix.io/vsm-guides/value-stream-designer/celonis-data-flow/retrieving-data-from-celonis.md): Learn how to initiate and manage value streams in Value Stream Modeller using Celonis signals as triggers.
- [Sending Data from VSM to Celonis](https://developer.emporix.io/vsm-guides/value-stream-designer/celonis-data-flow/sending-data-to-celonis.md): See how you can transfer data from VSM to Celonis using dedicated extractors.
- [Sending Form Submission Data from VSM to Celonis](https://developer.emporix.io/vsm-guides/value-stream-designer/celonis-data-flow/sending-form-submission-data-to-celonis.md): See how you can transfer form submission data from VSM to Celonis using dedicated extractors.
- [Sending Forms Magic Links Data from VSM to Celonis](https://developer.emporix.io/vsm-guides/value-stream-designer/celonis-data-flow/sending-magic-link-data.md): See how you can transfer forms magic links from VSM to Celonis using dedicated extractors.
- [Versioning](https://developer.emporix.io/vsm-guides/value-stream-designer/versioning.md): See how versioning is handled in value streams.


---

# 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://developer.emporix.io/vsm-guides/value-stream-designer.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.
