# Installing a prebuilt process flow

## Introduction

Installing a prebuilt process flow is a straightforward, one-click operation via the [Patchworks marketplace](https://doc.wearepatchworks.com/product-documentation/marketplace/marketplace-process-flows). All required components are installed and added to the relevant part of your Patchworks dashboard.

Once the installation is complete, you need to complete a few setup tasks in order to make the process flow live. This page details the [installation](#app-installation-steps) and [post-installation setup](#post-installation-steps-for-prebuilt-process-flows) steps required.

## What is installed?

When a prebuilt process flow is installed, all components (connectors, scripts, etc.) are added to the relevant area of your Patchworks dashboard - connectors are added to your [connectors page](https://doc.wearepatchworks.com/product-documentation/process-flows/cross-reference-lookups/accessing-cross-reference-lookups), custom scripts are added to [your scripts list,](https://doc.wearepatchworks.com/product-documentation/developer-hub/custom-scripting/accessing-custom-scripts) etc. 

For more information about the components of a prebuilt process flow please see [The anatomy of a prebuilt process flow](https://doc.wearepatchworks.com/product-documentation/process-flows/prebuilt-process-flows/the-anatomy-of-a-prebuilt-process-flow).

## Need to know

* If you install a prebuilt process flow which includes a connector that you have already installed from the [connector marketplace](https://doc.wearepatchworks.com/product-documentation/process-flows/prebuilt-process-flows/broken-reference), a fresh copy of that connector is installed alongside the existing one. You can then decide which one to use.
* When a prebuilt process flow is installed, it is **disabled** and set to a **draft** status. When you are ready, you should [enable](https://doc.wearepatchworks.com/product-documentation/process-flows/managing-process-flows/enabling-and-disabling-a-process-flow/enabling-and-disabling-a-process-flow-without-virtual-enviroments) and [deploy](https://doc.wearepatchworks.com/product-documentation/building-process-flows/process-flow-versioning#deploying-a-draft-or-inactive-version) the process flow. Keep in mind that your [Patchworks subscription tier](https://doc.wearepatchworks.com/product-documentation/getting-started/core-subscription-tiers) determines the number of process flows and connectors that you can deploy. 

## Prebuilt process flow installation steps

To install a prebuilt process flow, follow the steps below.

**Step 1**\
Select **marketplace** from the left-hand navigation menu, then access the [process flows](https://doc.wearepatchworks.com/product-documentation/marketplace/marketplace-process-flows) section.

**Step 2**\
Find the process flow that you want to install (if necessary, click the **view** button for a read-only view of the flow, to be sure):

<div align="left"><figure><img src="https://2440044887-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLYNcUBVQwSkOMG6KjZfz%2Fuploads%2FIKMQsZyCoiHoLvmamuWO%2Fview%20process%20flow%20b.png?alt=media&#x26;token=ba7feda9-ece3-4918-b4f4-d5a7540a3c2c" alt=""><figcaption></figcaption></figure></div>

{% hint style="info" %}
Don't forget that you can use the search bar to find process flows.&#x20;
{% endhint %}

**Step 3**\
Click the **install** button for the required process flow:

<div align="left"><figure><img src="https://2440044887-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLYNcUBVQwSkOMG6KjZfz%2Fuploads%2F7ttCmUwC2FomjmcCZiSh%2Finstall%20process%20flow%202.png?alt=media&#x26;token=147eb45a-681e-4319-8bfb-1762ae8afee7" alt=""><figcaption></figcaption></figure></div>

**Step 4**\
A confirmation message is displayed, advising that the process flow is queued for installation. Typically, installation is completed in a few seconds, but you can navigate away in the meantime. Once the installation is complete, you'll see a notification in your [notification centre](https://doc.wearepatchworks.com/product-documentation/marketplace/the-notification-centre).

## Post-installation steps for a prebuilt process flow

Having installed a prebuilt process flow, follow the steps below to complete its setup:

* [Stage 1: Check installed connectors & add required instances](#stage-1-check-installed-connectors-and-add-required-instances)
* [Stage 2: Update process flow connection shapes](#stage-2-update-process-flow-connection-shapes)
* [Stage 3: Check other shapes](#stage-3-check-other-shapes)
* [Stage 4: Deploy the process flow](#stage-4-deploy-the-process-flow)
* [Stage 5: Enable the process flow](#stage-5-enable-the-process-flow)

### Stage 1: Check installed connectors & add required instances

Select **process flows** <mark style="color:red;">|</mark> **connectors & instances** from the left-hand navigation menu. Here you'll find all of your installed connectors.

Any connectors installed via the prebuilt process flow will be shown here. If the process flow installs a connector that you already had, you'll find a fresh version of the connector next to your existing one, so you can decide which one to use.

<details>

<summary><img src="https://2440044887-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLYNcUBVQwSkOMG6KjZfz%2Fuploads%2FPq80F8deQ3i4P3iazHRj%2Ficon%20decision.svg?alt=media&#x26;token=61be5bf3-7235-45fe-af5f-726229df8dd6" alt="" data-size="line"> I have an existing version of this connector that I'd like to use</summary>

That's fine. Chances are that if you already have the connector installed, you will have existing [instances](https://doc.wearepatchworks.com/product-documentation/connectors-and-instances/connectors-and-instances-introduction#instances) that can be used. In this case, you can go straight to [Stage 2](#stage-2-update-process-flow-connection-shapes).

If you don't have all the instances that you need for your existing connector, you should [add them now](https://doc.wearepatchworks.com/product-documentation/connectors-and-instances/working-with-instances/adding-an-instance).

</details>

<details>

<summary><img src="https://2440044887-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLYNcUBVQwSkOMG6KjZfz%2Fuploads%2FPq80F8deQ3i4P3iazHRj%2Ficon%20decision.svg?alt=media&#x26;token=61be5bf3-7235-45fe-af5f-726229df8dd6" alt="" data-size="line"> I want to use the new connector installed by the process flow</summary>

The new connector will not have any associated instances, so you need to [add them now](https://doc.wearepatchworks.com/product-documentation/connectors-and-instances/working-with-instances/adding-an-instance).&#x20;

</details>

### Stage 2: Update process flow connection shapes

Once you're satisfied that all required instances are in place with your connector credentials, you need to apply these to connection shapes in the new process flow.&#x20;

To do this, select **process flows** <mark style="color:red;">|</mark> **process flows** from the left-hand navigation menu. Here you'll find [all of your process flows](https://doc.wearepatchworks.com/product-documentation/process-flows/accessing-your-process-flows), including any that you have installed from the marketplace.

Edit the new process flow and check all [connection shapes](https://doc.wearepatchworks.com/product-documentation/process-flows/building-process-flows/process-flow-shapes/standard-shapes/connector-shape) - you'll notice a warning symbol, indicating that the shape is not configured - for example:

<div align="left"><figure><img src="https://2440044887-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLYNcUBVQwSkOMG6KjZfz%2Fuploads%2FAxDHrZpc39DSjXsz7SfU%2Fconfigure%20connection%201.png?alt=media&#x26;token=e903fe2d-c439-4021-ba17-32a7a29298e1" alt="" width="359"><figcaption></figcaption></figure></div>

Click the **settings** icon for the connection shape and choose the required **instance** and **endpoint** (leave all other connection settings as the default):

<div align="left"><figure><img src="https://2440044887-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLYNcUBVQwSkOMG6KjZfz%2Fuploads%2FICkhhUr6ANam75wEV6dd%2Fconfigure%20connection%202.png?alt=media&#x26;token=6dbae595-f73d-484c-b30c-eb81dc934bcc" alt="" width="352"><figcaption></figcaption></figure></div>

{% hint style="info" %}
Don't forget to save your changes!
{% endhint %}

### Stage 3: Check other shapes

Check all other shapes in the process flow for a warning symbol. If there is a warning, open settings and click **save** to confirm.

{% hint style="info" %}
Other shapes should not need to be changed but sometimes you may need to confirm default details by saving the shape settings.
{% endhint %}

### Stage 4: Deploy the process flow

Once you're satisfied that all connection shapes are configured and you're ready to put the process flow live, you should deploy it. To do this, access [process flow settings](https://doc.wearepatchworks.com/product-documentation/process-flows/building-process-flows/process-flow-settings) and change the `draft` status to `deployed`:

<div align="left"><figure><img src="https://2440044887-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLYNcUBVQwSkOMG6KjZfz%2Fuploads%2FUh9KyhuwIczdyrwUQiw0%2Fdeploy%20flow.png?alt=media&#x26;token=0754be02-b369-4e81-8e55-8c3e13181b86" alt="" width="563"><figcaption></figcaption></figure></div>

{% hint style="info" %}
For more information please see [Process flow versioning](https://doc.wearepatchworks.com/product-documentation/process-flows/building-process-flows/process-flow-versioning).
{% endhint %}

### Stage 5: Enable the process flow

The final step is to enable the process flow. To do this, access [process flow settings](https://doc.wearepatchworks.com/product-documentation/process-flows/building-process-flows/process-flow-settings) and toggle the ENABLE option to ON:

<div align="left"><figure><img src="https://2440044887-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLYNcUBVQwSkOMG6KjZfz%2Fuploads%2FC8gpY3ai3Op011WDhxK9%2Fenable%20flow.png?alt=media&#x26;token=f074e97a-47e0-439b-abd2-8e079a47317f" alt="" width="563"><figcaption></figcaption></figure></div>