> For the complete documentation index, see [llms.txt](https://docs.justransform.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.justransform.com/development/business-processes/activating-a-business-process.md).

# Activating a Business Process

Business Processes can be activated within the Connections panel. Accessed through clicking Development > "**Connections"** link on the left side of the application.

1. You will see the details of the connection on the details tab. For example, in an SFTP connection, you will see the following

<figure><img src="/files/gwlUoZdeYqU8GcePh16M" alt=""><figcaption></figcaption></figure>

{% content-ref url="/pages/4UxXq4ZPX00Ld1fa8ih3" %}
[Creating a Connector](/development/connections/creating-a-connector.md)
{% endcontent-ref %}

{% content-ref url="/pages/HbVxPR1CE2Dvj5TfFTc7" %}
[Updating a Connector](/development/connections/updating-a-connector.md)
{% endcontent-ref %}

Business Processes can be used in four scenarios within a connection. The Business Process will be activated based on the stage of the connection transformation lifecycle.

**Business Process to be executed for incoming file**

Any Business Process activated here will get executed as soon as a message is received by the connection.

**Business Process to be executed for Outgoing file**

Any Business Process activated here will get executed when this connection is used as an **outbound** connection.

**Business Process to be executed for Synchronous Response**

Any Business Process activated here will get executed **asynchronously** when this connection receives a synchronous response.

**Business Process to be executed for Acknowledgement**

Any Business Process activated here will and will send back as an **asynchronous** acknowledgement back to the sender.


---

# 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://docs.justransform.com/development/business-processes/activating-a-business-process.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.