> 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/value-stream-modeller/value-stream-designer/integration-with-make/configuring-make-connection.md).

# Configuring a Connection between VSM and Make Modules

Make modules are components that are used for creating scenarios in Make.

{% hint style="info" %}
To learn more about the way they work, see [Types of Modules](https://www.make.com/en/help/modules).
{% endhint %}

The connection between VSM and the modules in Make is normally created automatically. However, if you add the module in Make when creating a scenario and the connection is not established, you can configure it manually.

{% stepper %}
{% step %}

#### Add an Orchestration module in Make

Add an Orchestration module in Make, for example a **Trigger Event**. An **Emporix Orchestration** window pops up, where you can check all the module's details and enter the required data.

<figure><img src="/files/JvXKFsDOR1NdMhHqJIzi" alt="Emporix Orchestration Trigger Event module configuration" width="538"><figcaption><p>Trigger Event module configuration window in Make</p></figcaption></figure>
{% endstep %}

{% step %}

#### Open the connection configuration

To open the connection configuration, choose **ADD** in the connections section. The **Create a connection** window is displayed.

<figure><img src="/files/rijlNBC0QkW4U68C3H6L" alt="Create a connection window in Make" width="350"><figcaption><p>Create a connection window for an Emporix Orchestration module</p></figcaption></figure>
{% endstep %}

{% step %}

#### Enter the Event Source ID and Secret

Enter the **Event Source ID** and the related **Secret**. You can copy and paste the ID and the secret from the Emporix Management Dashboard. To find the **Event Source ID** and the **Secret**, go to **VSM** → **Admin** → **Settings**.

<figure><img src="/files/ho0CsFeM110zfCYdFRUf" alt="VSM Admin Settings with Event-Receiver Endpoint source and secret"><figcaption><p>Event-Receiver Endpoint source and secret in VSM Admin Settings</p></figcaption></figure>
{% endstep %}

{% step %}

#### Choose the environment

Choose the **environment** with which you want to establish the connection.
{% endstep %}

{% step %}

#### Enter the Client ID and Secret

Enter the **Client ID** and the client **Secret**. You can copy and paste the ID and the secret from [Emporix Developer Portal](https://dashboard-login.emporix.io/devportal/login). To find the **Client ID** and the **Secret**, go to **Developer Portal** → **OE API Keys**.

<figure><img src="/files/TcH12caoHQ1mACsRMXsG" alt="OE API Keys in the Emporix Developer Portal"><figcaption><p>Client ID and Secret in the Emporix Developer Portal OE API Keys section</p></figcaption></figure>
{% endstep %}

{% step %}

#### Save the connection

Choose **SAVE** to create the connection.
{% endstep %}
{% endstepper %}


---

# 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/value-stream-modeller/value-stream-designer/integration-with-make/configuring-make-connection.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.