> 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/oe/value-streams/working-with-value-streams/cloning-make-scenarios.md).

# Cloning of Make Scenarios in OE Value Streams

You can clone a scenario prepared in Make to use it in your OE value stream. Go to the Make application and choose the **Clone** action for the selected scenario. You can copy all types of scenarios, either the ones that are used as triggers, or the ones that are prepared for the other process steps.

When you clone a scenario in Make, a **Clone** pop-up window is displayed where you should specify the name for the scenario's copy and select, or create, a new webhook to trigger the copy of the scenario.

Each Make scenario that’s invoked by the OE process engine, starts with a cloud event that is set as a trigger. This requires a unique webhook so the value stream engine routes the request to the proper scenario. When you add the scenario to the value stream, it sends requests to this webhook and not to the one of the original cloned scenario.\
This way the new cloned scenario gets invoked.

{% hint style="info" %}
To learn more about the scenarios details, see Make's documentation at [Scenario details](https://www.make.com/en/help/scenarios/scenario-detail).
{% endhint %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://developer.emporix.io/oe/value-streams/working-with-value-streams/cloning-make-scenarios.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.