--- updatedAt: 2026-02-06T08:14:20.000Z agentTools: projectIndex: https://docs.quickwork.co/llms.txt --- # Establishing connections This section explains the processes of setting up both authorized and authenticated connections. ## :white\_check\_mark: Pre-requisites * Access to Quickwork. * Basic understanding of [Quickwork terminologies](https://quickwork-docs.readme.io/docs/key-concepts) and familiarity with the Quickwork's GUI. * An active account with the third-party apps you intend to connect, such as Google Sheets and [Freshdesk](https://www.freshworks.com/freshdesk/signup/) in this instance. ## Establishing a new authorized connection To establish a new authorized connection, for example, with Google Sheets as a trigger, follow these steps: 1. Navigate to the **Apps** drop-down menu and select **Google Sheets** under the **New Trigger** field. 2. Choose **New row** from the **Triggers** drop-down menu. 3. To create a new authorized connection, click on **+ Create new connection**.

4. While a default connection name will appear, you may enter any name you prefer. Click the **Link an account** button.

5. Select a Gmail account you wish to use for creating the connection.

6. You will be directed to a connection window where Quickwork Automation will require permission to access your Google account's information. Click the **Allow** button to grant access.

Your connection is now successfully created, enabling Quickwork to perform tasks in this account on your behalf. Each connection must have a unique name. Duplicate names for connections of the same app are not permitted. For better organization and clarity, it's advisable to choose names specific to the project or customer involved. ## Establishing a new authenticated connection For establishing a new authenticated connection, consider the following example using PDF Otter as an action: 1. Select **Freshdesk** under the **Simple Action** field and choose **Create ticket** from the **Actions** drop-down menu. 2. Click on **+ Create new connection** and **Link account**.

2. The **Connect to** **Freshdesk** window appears. i. Specify the **Connection Name**, if required. ii. The Freshdesk app requires the **Helpdesk name** and **Your API Key** to establish the connection. The steps to obtain the API key are provided below the fields in the connection window. iii. Follow these steps carefully to obtain the required credentials, which will allow the connection to be established successfully.

## Using an existing connection Newly created connections are subsequently treated as existing connections for other Journeys throughout the account. Here’s how it works: 1. When creating new Journeys with a previously connected app, a drop-down menu will display a list of existing connections for that app, such as Google Sheets. 2. From the drop-down menu, you can easily select the desired connection to use for your current Journey.

* The connection drop-down list displays all active connections for that particular app across the account. * Only one authorized connection can be created or selected for an app within a single Journey. * If a connection is already established, you can modify it or create a new one through the [Connections tab](https://quickwork-docs.readme.io/docs/understanding-the-journey-connections-tab) while configuring your Journey in the Journey configuration manager. * All established connections are saved in the [Connections page](https://quickwork-docs.readme.io/docs/managing-app-connections-in-quickwork) of your Quickwork account. Here, users can centrally view app connections, further details like connection status, and access specific Journeys utilizing those connections. * Users can delete the connection in **Connections** page. Deleting connections will remove the integration between Quickwork and the app, making it unavailable in the Journey connection list and deactivating its use in all related Journeys. Before deleting a connection, make sure to check its dependencies in the **Dependencies** tab of the respective Journey to ensure it isn’t being used in other Journeys. ## :question: Troubleshooting * Issues with connection authorization: This involves challenges such as failure to connect due to incorrect permission settings or a declined access by the third-party app. Ensure all authorization steps are correctly followed and that you have the necessary permissions to grant Quickwork access. * Errors in entering API keys: Mistakes can occur when entering API keys required for authenticated connections. Verify the accuracy of the API keys and ensure they are entered without any spaces or typographical errors. ## :pencil2: Tips and recommendations * To connect to an app, you can either search for the desired app at Quickwork Support or refer to the hint text in the **Connect to** window. * If you want to remove connections from appearing in the drop-down list within the Journey configuration window, you can do so by deleting the connection in the centrally managed [Connections](https://quickwork-docs.readme.io/docs/managing-app-connections-in-quickwork) page. ## :books: Additional resources [Journeys: Automation across apps](https://quickwork-docs.readme.io/docs/structure-of-a-journey)\ [Triggers to initiate Journeys](https://quickwork-docs.readme.io/docs/triggers)\ [Configuring actions](https://quickwork-docs.readme.io/docs/actions)\ [Building your first Journey](https://quickwork-docs.readme.io/docs/building-your-first-journey)\ [Managing app connections in Quickwork](https://quickwork-docs.readme.io/docs/managing-app-connections-in-quickwork)\ Journey management with [history](https://quickwork-docs.readme.io/docs/viewing-the-journey-history-tab), [connections](https://quickwork-docs.readme.io/docs/understanding-the-journey-connections-tab), [versions](https://quickwork-docs.readme.io/docs/version-control), [dependencies](https://docs.quickwork.co/docs/dependencies), and [settings](https://quickwork-docs.readme.io/docs/sharing-a-journey)