Connection management
This section covers how to establish and manage app connections within Quickwork to enable seamless automation across third-party applications.
What is a connection
To perform CRUD (Create, Read, Update, and Delete) operations in third-party apps through triggers or actions, you must establish an authorized or authenticated connection when creating a journey. Establishing a connection involves granting Quickwork permission to perform specific tasks in third-party apps for you.
Types of connections
All third-party apps in Quickwork's app directory support two types of connection mechanisms:
1. Authorization
This involves authorizing the supported services of the apps with a set of permissions via Google, Facebook, Microsoft sign-in. Once signed in successfully, you must allow the set of scopes intended to perform the activity in the journey on your behalf. Primarily, Quickwork supports third-party apps with OAuth 2.0 authorization. For example: Gmail, Google Sheets, Facebook Messenger.
2. Authentication
This involves validating your identity by providing valid credentials of the apps to be connected. These credentials may include a username, password, client ID, client secret, private key, public key, etc. These values are unique for each third-party app, and the steps to obtain them are provided in the Connect to window of the app you are connecting to. For example: Freshdesk, Jira, PDF Otter.
✏️ Tips and recommendations
- Ensure you have an active account with the third-party apps you intend to connect.
- 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.
- To edit the app connections in a trigger event or actions, you can go the Connections tab in the journey configuration manager.
📚 Additional resources
Journeys: Automation across apps
Triggers to initiate journeys
Configuring actions
Establishing connections
Building your first journey
Managing app connections in Quickwork
Updated 9 months ago