> For the complete documentation index, see [llms.txt](https://university.gonexa.fr/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://university.gonexa.fr/doc/en/advanced-features/doc-and-flows/flow-examples-org.md).

# The Flow Org: pre-built flow examples

Explore our example flows in a read-only Salesforce demo org, with no credentials required.

The Flow Org is a Salesforce demo org that brings together our example flows. Get inspired by our customers' most common use cases before building your own.

## What you will find there

* The Gonexa Doc, Gonexa Sign and Gonexa RF flows most used by our customers
* Their complete configuration: Gonexa actions, variables, conditions

## Access the Flow Org

{% stepper %}
{% step %}

### Open the Test Drive

The Flow Org is available through the Gonexa Test Drive on the Salesforce AppExchange.

<a href="https://appexchange.salesforce.com/try?listingId=a0N3A00000FMiJiUAL&#x26;type=TestDrive" class="button primary" data-icon="arrow-up-right-from-square">Access the Flow Org</a>
{% endstep %}

{% step %}

### Choose the "Try in a test drive org" trial type

In **Step 1 – Choose a trial type**, select the **Try in a test drive org** card (it turns blue once selected).

{% hint style="danger" %}
**Warning**

Do not choose **Try in your sandbox**: that option installs the Gonexa package in your own sandbox and does not give access to the Flow Org.
{% endhint %}
{% endstep %}

{% step %}

### Enter your contact details

In **Step 2 – Share your contact info**, fill in the required fields:

| Form field         | What to enter                 |
| ------------------ | ----------------------------- |
| **First Name**     | Your first name               |
| **Last Name**      | Your last name                |
| **Company**        | Your company name             |
| **Email**          | Your business email address   |
| **Country/Region** | Your country (drop-down list) |

You can also click **log in to your Trailblazer account** to have these fields filled in automatically from your Trailblazer account.

The **I'd like to receive news and updates about Gonexa's other products and services** checkbox is optional.

{% hint style="info" %}
By submitting the form, you accept the Salesforce Program Agreement and agree that your contact details are shared with Gonexa, as stated below the form.
{% endhint %}
{% endstep %}

{% step %}

### Launch the Test Drive

Submit the form with the button at the bottom of the page to start the Test Drive. The Flow Org then opens in a new tab.
{% endstep %}

{% step %}

### You are logged in automatically

You land in the org as a trial user. No username, password or verification code is required.
{% endstep %}

{% step %}

### Open the flows

From **Setup**, go to **Flows**, then open the flow of your choice in Flow Builder.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
**Read-only**

You can view everything, but you cannot edit or save anything in the Flow Org.
{% endhint %}

## Reproduce a flow in your org

* Open each element of the flow to see its configuration (Gonexa actions, variables, conditions)
* Recreate the flow in your Sandbox, then test it before deploying it to Production

{% hint style="warning" %}
**Tip**

Start with the flow closest to your use case and adapt it to your objects.
{% 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 by asking a question.

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

```
GET https://university.gonexa.fr/doc/en/advanced-features/doc-and-flows/flow-examples-org.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.