# Updating a connector

## Introduction

The **manage connectors** page is used to view and manage all connectors that you've installed or built. From here, you can make changes to any of your connectors. 

It's important to understand the difference between updating a **prebuilt Patchworks connector** (which you [installed via the marketplace](https://doc.wearepatchworks.com/product-documentation/connectors-and-instances/working-with-connectors/installing-a-connector)) and updating a **custom connector** that was built by your organisation, using the [connector builder](https://doc.wearepatchworks.com/product-documentation/developer-hub/connector-builder).

### Prebuilt connectors

Prebuilt connectors are managed by Patchworks. If the associated third-party system requires a general update, Patchworks will make this change and issue a new version of the connector in the [marketplace](https://doc.wearepatchworks.com/product-documentation/marketplace/the-patchworks-marketplace).

Having installed a prebuilt connector, you can go on to update its settings if needed - for example, you might want to add an extra endpoint. If you do modify a prebuilt connector, you'll notice that it is updated to show version information, and who made the change:

<figure><img src="https://2440044887-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLYNcUBVQwSkOMG6KjZfz%2Fuploads%2F9OjuM7oZrlIFeCX5F3If%2Fmodify%20connector%20b.png?alt=media&#x26;token=a562827f-76c2-4d85-b953-75c3441490bf" alt=""><figcaption></figcaption></figure>

If Patchworks issues an update for a modified connector, you can choose whether to `overwrite` your existing connector (including any customisations that you've made) or to `install` the updated version alongside your existing one.  &#x20;

{% hint style="danger" %}
Choosing to overwrite an existing connector will `overwrite` any customisations that may have been made to the existing connector by members of your team. If in doubt, don't overwrite!
{% endhint %}

### Custom connectors

Custom connectors are built with the [Patchworks connector builder](https://doc.wearepatchworks.com/product-documentation/developer-hub/connector-builder) and are managed by whoever builds them - Patchworks will never issue general updates for custom connectors.

## The steps

**Step 1**\
Log in to the [Patchworks dashboard](https://app.wearepatchworks.com/login) and select **process flows** <mark style="color:red;">></mark> **connectors & instances** to access the **manage connectors** page.

**Step 2**\
If a connector has a pending update, you'll see an **update available** button - click this. 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%2FEVe49RFFFXSgyg1pVEpR%2Fupdate%20connector%201.png?alt=media&#x26;token=93e2b9d9-5aeb-4620-a218-fbef8f29db69" alt="" width="563"><figcaption></figcaption></figure></div>

{% hint style="info" %}
If this option is not shown, the connector is up to date.
{% endhint %}

**Step 3**\
If Patchworks detects that your existing version of this connector has been modified, you are prompted to decide if you want to **overwrite** the current version (therefore overwriting any modifications that you've made) or **install** a new version - for example: &#x20;

<div align="left"><figure><img src="https://2440044887-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLYNcUBVQwSkOMG6KjZfz%2Fuploads%2FkVCSlwOYy07AdEwD9Ewk%2Fupdate%20connector%202.png?alt=media&#x26;token=0277d803-4082-4cc3-a025-2dc95fa22947" alt="" width="563"><figcaption></figcaption></figure></div>

**Step 4**\
Select your preferred update option: &#x20;

<div align="left"><figure><img src="https://2440044887-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLYNcUBVQwSkOMG6KjZfz%2Fuploads%2FXsb93KugkfTiWzNYWooh%2Fupdate%20connector%203.png?alt=media&#x26;token=c0e3023b-08d1-40a7-9a69-f7327d937a45" alt="" width="563"><figcaption></figcaption></figure></div>

<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"> What happens if I OVERWRITE an existing connector?</summary>

* If you or your team have modified your connector in any way, these changes will be lost.
* Existing instances do NOT need to be re-authenticated.
* If this connector is used in process flows, these flows will continue to run with existing instances.

</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"> What happens if I INSTALL alongside an existing connector?</summary>

* A new connector is installed alongside your existing (out-of-date) version.
* Your existing (out-of-date) version does not change.
* If this connector is used in process flows, these continue to run with the existing (out-of-date) connector. This may result in warnings or errors and results may not be as desired.&#x20;
* To apply the new connector in process flows, you must add and authenticate new instances, then re-configure process flow connector shapes to use these.

</details>

**Step 5**\
The update is completed. If you choose to install a new version of a customised connector, you will see that you now have two instances of that connector in your **manage connectors** list: &#x20;

<div align="left"><figure><img src="https://2440044887-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLYNcUBVQwSkOMG6KjZfz%2Fuploads%2F0vjgJQ8vKuGrAlnSwts9%2Fupdate%20connector%204.png?alt=media&#x26;token=24eeaab8-8359-4d42-96f5-bc7f8db4eb10" alt="" width="563"><figcaption></figcaption></figure></div>

You can now apply your modifications to the new version, then create new instances and update connection shapes with these in affected process flows.