> For the complete documentation index, see [llms.txt](https://docs.getint.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.getint.io/getintio-platform/connections/editing-connections-for-existing-integrations.md).
# Creating, Updating, and Changing Connections
## Introduction
Getint uses connections to authenticate and communicate with connected applications. Over time, you may need to replace, update, or create new connections due to changes in your environment.
Common scenarios include migrating from a personal account to a Service Account, replacing an expired API token, resolving connection-related issues, or updating connection details after changes to the destination application's URL.
This article explains how to change the connection used by an existing integration, update an existing connection's credentials, and create new connections when needed.
### Requirements
Before changing a connection:
* The new connection must point to the same instance.
* The new connection must have access to the same projects, fields, and items currently synchronized by the integration.
* The replacement account should have permissions equivalent to the original account.
{% hint style="warning" %}
The Change Connection feature is not intended for switching to a different instance or project. Using a connection that points to a different instance may cause synchronization issues and unexpected behavior.
{% endhint %}
***
### Creating New Connections
To create new connections, you must simulate a new integration.
1. Go to **Workflows** > **Integrations**, and click **Create Integration**
2. Select either Continuous Sync or Data Migration, select the app to which you must create a new connection to open the Connect App screen, and click **Create New Connection**.
3. Add the URL of the same workspace as your previous connection, name the connection as you want, add the new credentials, and click Add.
You can now update your previous integration with your newly created connection.
***
### Updating Existing Connections
If you need to update the credentials or configuration of a connection rather than replace it, you can edit the connection directly from the Connections section.
1. Navigate to **Workflows** > **Connections**
2. Locate the connection you want to update, click the **three dots** under the **actions column**, and click **Edit**.
3. Move to the next screen, then edit the **Email** and **API token** of the connection with the new credentials. Click **Update** when you are done.
Future synchronization runs will use the updated connection settings.
{% hint style="warning" %}
You can’t update an existing connection with the credentials of a **Service Account**.\
To use a Service Account on a connection, you must create a connection from scratch.
{% endhint %}
### Changing a Connection
1. Open the integration you want to modify.
2. Select the application connection you want to replace. The connection settings panel will open.
3. Click **Change Connection**.
4. Select the new connection from the available list.
5. Once selected, click Change Connection, close the tab, and save the integration.
The integration will begin using the newly selected connection for future synchronization runs.
***
### Common Use Cases
#### Migrating to a Service Account
* Many organizations initially configure integrations using a personal account and later transition to a dedicated Service Account.\
\
The Change Connection feature allows you to replace the original connection without recreating the integration.
#### Replacing an Expired Token
* If the credentials associated with the connection expire, create a new connection using the updated token and switch the integration to the new connection.
***
### Troubleshooting
#### Synchronization Errors After Changing the Connection
Verify that the new account:
* Can access all synchronized projects.
* Has permission to read and update items.
* Has visibility into all mapped fields.
#### Items Stop Synchronizing After the Change
Verify that the selected connection points are to the same instance used by the integration.
Using a connection from a different instance or project is not supported and may prevent synchronization from functioning correctly.
#### I Need to Modify Connection Settings Instead
The Change Connection feature is intended for replacing an existing connection.
If you need to modify connection details directly, navigate to the **Connections** section under **Workflows** and update the connection there.
{% hint style="warning" %}
Verify that the new account has access to all projects, fields, and items already synchronized by the integration.
Missing permissions may result in synchronization failures after the connection is replaced.
{% endhint %}
***
### Conclusion
The Change Connection feature provides a quick way to replace the credentials used by an existing integration without rebuilding it from scratch. When used correctly, it can simplify account migrations, token replacements, and connection-related troubleshooting while preserving your existing integration configuration.
If you require additional assistance, don't hesitate to get in touch with our support team at our [Help Center.](https://getint.io/help-center)
---
# 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.getint.io/getintio-platform/connections/editing-connections-for-existing-integrations.md?ask=&goal=
```
`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.