# Constant Contact authentication

> To be able to create a connection, you need to have a Constant Contact account with the following credentials:

## Prerequisites

To be able to create a connection, you need to have a Constant Contact account with the following credentials:

* a **Username**, which consists of the email address associated with your account.
* a **Password** to your account.
* a **mobile phone number** associated to your account, to set up a 2FA code.

## Add the Constant Contact connection

To create a connection to your Constant Contact instance, you need to perform the following steps:

1. Select Orchestrator from the product launcher.
2. Select a folder, and then navigate to the **Connections** tab.
3. Select **Add connection**.
4. To open the connection creation page, select the connector from the list. You can use the search bar to find the connector.
   connection** button.
5. Enter the required parameters, and then select **Connect**.

   For any secret-type field, you can select the menu next to the field and choose **Use credential asset** to reference an Orchestrator credential asset linked to an external vault instead of entering the value directly. For more information, see [Use credential assets for connections](credential-store-connections.md).
6. You are now redirected to the Constant Contact [sign in page](https://identity.constantcontact.com/). Enter your
   standard credentials and select the **Sign In** button.
7. Now you need to verify your account through SMS Authentication. Select the
   **Send code** button.
8. A verification code is sent to your mobile phone number. Enter the code you
   received and select the **Verify** button.

For more information about Constant Contact, visit the [Constant Contact Help Center](https://knowledgebase.constantcontact.com/?lang=en_US).

## Scopes and permissions

You can use the connection to enable the [Constant Contact activities](https://docs.uipath.com/activities/docs/uipath-constantcontact-constantcontact-activities) in UiPath Studio to build automations for lists, contacts, or campaign management. The various permission-based use cases
that can be achieved are as follows:

|  |  |  |
| --- | --- | --- |
| **Scope/Permission** | **Usecase** | **Activity/Event** |
| offline\\_access | The offline\\_access is a scope required to receive refresh token in the authentication request endpoint. When you redeem an authorization code in the OAuth 2.0 authorization code flow without offline\\_access scope, you will not receive a refresh token from the v1/token endpoint. | N/A |
| account\\_read | Grants your application permission to read account data. | List All Records → Account Emails  List all Records → Account User Privileges |
| account\\_update | Grants your application permission to update account data. | Insert Record → Account Emails |
| contact\\_data | Grants your application permission to read or write contact data and to read contact reports. | Create Contact  Update Contact  Get Contact  Insert Record → Contact Custom Fields  Insert Record → Contact Signup Form  List All Records → Contacts |
| campaign\\_data | Grants your application permission to read or write campaign data and to read campaign reports. | List All Records → Campaigns  Get Email Campaign  Create Email Campaign  Update Email Campaign  Schedule Email Campaign (FUTURE)  Send Test Email (FUTURE) |