The following are the properties for connecting to MailChimp. The required properties are identified using the *** characters.

If a connection string property value has special characters such as semicolons, single quotes, spaces, etc., then you must quote the value using either single or double quotes.

Other properties (Proxy...) are detailed in section common properties

There are two authentication methods available for connecting to MailChimp. You can set the APIKey to the key you generate in your account settings. Instead of providing your APIKey, you can use the OAuth standard to authenticate the application.

API Key

The API key used for accessing your MailChimp account.

The API key used for accessing your MailChimp account. The API key can be found in MailChimp by going to Account -> Extras -> API Keys.

Initiate OAuth

This property sets whether the provider will initiate the process to obtain the OAuthAccessToken and OAuthServerUrl when it connects. If this property is set, the provider also automatically exchanges the refresh token for a new, valid OAuth access token. Default value is false.

OAuth Access Token

The OAuth access token secret of the authenticated account.

The OAuthAccessToken property is used to connect using OAuth. The OAuthAccessToken is retrieved from the OAuth server as part of the authentication process. It has a server-dependent timeout and can be reused between requests.

The access token is used in place of your username and password. The access token protects your credentials by keeping them on the server.

The OAuthAccessToken property is used to connect using OAuth. The OAuthAccessToken is retrieved from the OAuth server as part of the authentication process. It has a server-dependent timeout and can be reused between requests.

The access token is used in place of your username and password. The access token protects your credentials by keeping them on the server.

OAuth Client Id***

The client Id assigned when you register your application with an OAuth authorization server.

OAuth requires you to register your application. As part of the registration, you will receive a client Id, sometimes also called a consumer key, and a client secret. You must specify both the OAuthClientId andOAuthClientSecret to connect to an OAuth server.

OAuth requires you to register your application. As part of the registration, you will receive a client Id, sometimes also called a consumer key, and a client secret. You must specify both the OAuthClientId and OAuthClientSecret to connect to an OAuth server.

OAuth Client Secret***

The client secret assigned when you register your application with an OAuth authorization server.

OAuth requires you to register your application. As part of the registration you will receive a client Id and a client secret, sometimes also called a consumer secret. You must specify both the OAuthClientId and OAuthClientSecret to connect to an OAuth server.

OAuth requires you to register your application. As part of the registration you will receive a client Id and a client secret, sometimes also called a consumer secret. You must specify both the OAuthClientId and OAuthClientSecret to connect to an OAuth server.

OAuth Settings Location

The location of the settings file where OAuth values are saved when InitiateOAuth is set to true.

SSL Cert

The certificate to be accepted from the server when connecting using SSL.

If using an SSL connection, this property can be used to specify the SSL certificate to be accepted from the server. Any other certificate that is not trusted by the machine will be rejected. This can take the form of a full PEM certificate, the path to a file containing the certificate, the public key, the MD5 thumbprint, or the SHA1 thumbprint. If not specified, any valid certificate will be accepted. Use '*' to signify to accept all certificates. Do not specify the SSLCert to only accept certificates that the machine already trusts.

Timeout

The value in seconds until the timeout error is thrown, canceling the operation. Default value is 60.

If the Timeout property is set to 0, operations do not time out: They run until they complete successfully or encounter an error condition. If Timeout expires and the operation is not yet complete, the provider throws an exception.

Authenticating to the Salesforce Marketing Cloud REST API

The Salesforce Marketing Cloud REST API uses the OAuth authentication standard. To authenticate using OAuth, you will need to create an app to obtain the OAuthClientId and OAuthClientSecret connection properties.

You can follow the procedure below to register an app and obtain the OAuth client credentials, the Client Id and Client Secret:

1. Log in to your Salesforce Marketing Cloud Go to Marketing Cloud | Administration | Installed Packages.

2. Click New.

3. Give the package a name and description.

4. Save the package. Once the package is saved, you see important details about the package. See Installed Packages Definitions for more information about each field. You see the Package ID, JWT Signing Secret, and Source Account only for packages created in your account.

5. Under Components, click Add Component.

6. Select API Integration.

7. You must select Server-to-Server or Web App as integration type if the package supports enhanced functionality.

8. Assign the appropriate scope for your integration.

   • Perform server-to-server requests... is automatically selected for all API Integrations.

   • Select Perform requests on behalf of the user... if this package contains a Marketing Cloud app.

   • Select the Marketing Cloud scope for your API calls. Assign only the scope your package needs.

9. Save the component.

10. Under the component details, you can find the Client ID and Client Secret.

After setting the following connection properties, you are ready to connect:

• InitiateOAuth: Set this to GETANDREFRESH. You can use InitiateOAuth to avoid repeating the OAuth exchange and manually setting the OAuthAccessToken connection property.

• OAuthClientId: Set this to the Client ID in your app settings.

• OAuthClientSecret: Set this to the Client Secret in your app settings.

• AccountId: Set this to the specific MID of the target business unit. This is not available for legacy packages.

• CallbackURL: Set this to the URL in your app settings. Note: The default value is https://127.0.0.1:33333.

When you connect the provider completes the OAuth process.

1. Exchanges the OAuthClientId and OAuthClientSecret for the OAuthAccessToken.

2. Refreshes the access token when it expires.

3. Saves OAuth values in OAuthSettingsLocation to be persisted across connections.

Authenticating to the Salesforce Marketing Cloud SOAP API

The Salesforce Marketing Cloud SOAP API can connect using either your login credentials, or Using OAuth Authentication.

To connect to data using basic (login credentials) authentication, set the following:

• User: The Salesforce Marketing Cloud user account used to authenticate.

• Password: The password used to authenticate the user.

to your login credentials, or to the credentials for a sandbox user if you are connecting to a sandbox account.

Connecting to the Salesforce Marketing Cloud APIs

Once you have authenticated to either the SOAP or REST API, you are ready to connect to data.

You may optionally refine data access using the following properties:

• UseSandbox: Set this to true to use a Salesforce Marketing Cloud sandbox account.

• Instance: The instance of the Salesforce Marketing Cloud API used. The default Instance is s7 of the Web Services API; however, you can use this property to specify a different instance.

Authenticating to HubSpot

There are two authentication methods available for connecting to HubSpot data source: PrivateAppToken-based and OAuth Authentication.

Some tables in the HubspotV3 schema may not work with the OAuth mechanism. This API limitation restricts their usage only to the PrivateAppToken-based authentication. Specifically, each table in the data-model section will mention the supported authentication mechanism.

Private App Token

To connect using a Hubspot Private App Token, set the AuthScheme property to PrivateAppToken and OAuthAccessToken to the value of your application's access token, and you are ready to connect.

You can generate a HubSpot Private App Token by following the steps below:

1. In your HubSpot account, click the settings icon in the main navigation bar.

2. In the left sidebar menu, navigate to Integrations > Private Apps.

3. Click Create private app.

4. On the Basic Info tab, configure the details of your application (name, logo, and description).

5. On the Scopes tab, select Read or Write for each scope you want your private application to be able to access. This determines the data the driver has access to retrieve. Refer to the OAuthRequiredScopes and OAuthOptionalScopes properties for recommended scopes to select.

6. After you are done configuring your application, click create app in the top right.

7. Review the info about your application's access token, click Continue creating, and then Show token.

8. You can now set the retrieved token in the OAuthAccessToken property (OAuthAccessToken is used for Private App Access Tokens and OAuth Access Tokens).

You can set the AuthScheme to PrivateAppToken to enforce this Authentication scheme.

OAuth

AuthScheme must be set to OAuth in all OAuth flows. The following OAuth flows assume you have done so.

Follow the steps below to register an application and obtain the OAuth client credentials, the OAuthClientId and OAuthClientSecret:

1. Log into your HubSpot developer account.

2. On the developer account home page, click Create an app or, if starting from the Apps dashboard, click Create app.

3. On the App info tab, enter and optionally modify values that are displayed to users when they connect. These values include the public application name, application logo, and a description of the application.

4. On the Auth tab, copy the client ID and client secret. You will use these later for the OAuthClientId and OAuthClientSecret properties.

5. Set CallbackURL to http://localhost:33333 or a trusted URL where users are redirected to after they authorize your application.

6. Under Scopes, select Standard > oauth, any additional scopes as needed for your application's functionality, and the data you want to retrieve (see the OAuthRequiredScopes and OAuthOptionalScopes properties for the default scopes requested by the driver).

Note that the requested scopes (OAuthRequiredScopes) must match the scopes specified in your application's settings.

After setting the following, you are ready to connect, Set the following connection properties to obtain the OAuthAccessToken:

• InitiateOAuth: Set this to GETANDREFRESH. You can use InitiateOAuth to avoid repeating the OAuth exchange and manually setting the OAuthAccessToken.

• OAuthClientId (custom applications only): Set this to the client Id assigned when you registered your application.

• OAuthClientSecret (custom applications only): Set this to the client secret assigned when you registered your application.

• CallbackURL (custom application only): Set this to the redirect URI defined when you registered your application.

When you connect, the provider opens HubSpot's OAuth endpoint in your default browser. Log in and grant permissions to the application. The provider then completes the OAuth process:

1. The provider obtains an access token from HubSpot and uses it to request data.

2. Extracts the access token from the callback URL and authenticates requests.

3. Saves OAuth values in the location specified in OAuthSettingsLocation. These values persist across connections.

The provider refreshes the access token automatically when it expires.

1 Authenticating to Oracle Eloqua

1.1 Connect via Login

To connect via Login, set AuthScheme to Basic. The standard method of authentication to Oracle Eloqua is via the login method. The Login method requires you to set Company and to set User, and Password to the credentials you use to log in. This method uses HTTP Basic authentication over SSL.

1.2 Connect via OAuth

To connect via OAuth, set AuthScheme to OAuth.

You can follow the procedure below to obtain the client credentials, the client Id (app Id) and client secret:

1. Log in to Oracle Eloqua.

2. Click Settings -> AppCloud Developer (under Platform Extensions) -> Create New App.

3. Enter a name, icon, and description for the app to be displayed to users when they connect to Oracle Eloqua. The OAuthClientId and OAuthClientSecret will be displayed.

4. If you are creating a desktop application, set the CallbackURL to http://localhost:3000, or another port of your choice.

Eloqua requires that the Callback URL begins with https://. You must specify a port.

1.2.1 Get an OAuth Access Token

After setting the following, you are ready to connect:

• OAuthClientId: Set this to the Client Id in your app settings.

• OAuthClientSecret: Set this to the Client Secret in your app settings.

• CallbackURL: Set this to the Redirect URL in your app settings.

• InitiateOAuth: Set this to GETANDREFRESH. You can use InitiateOAuth to avoid repeating the OAuth exchange and manually setting the OAuthAccessToken.

When you connect the provider opens the OAuth endpoint in your default browser. Log in and grant permissions to the application. The provider then completes the OAuth process:

1. Extracts the access token from the callback URL and authenticates requests.

2. Saves OAuth values in OAuthSettingsLocation to be persisted across connections.

1.2.2 The Password GrantType

When setting the OAuthGrantType to password, an OAuth flow may be triggered that passes user credentials. In this case, there will be no browser window to authorize. Instead, the following connection properties will need to be set:

• User - Set this to the user name.

• User - Set this to the password.

• Company - Set the company for the user.

• OAuthClientId: Set this to the Client Id in your app settings.

• OAuthClientSecret: Set this to the Client Secret in your app settings.

• OAuthGrantType: Set this to password.

• InitiateOAuth: Set this to GETANDREFRESH. You can use InitiateOAuth to avoid repeating the OAuth exchange and manually setting the OAuthAccessToken.

2 Connection properties

The following are the connection properties for Oracle Eloqua. Not all properties are required. Enter only property values pertaining to your installation. Several properties will be automatically initialized with the appRules defaults.

Connecting to Bing Ads

You need to register a Bing Ads account, get a developer token, and authenticate using OAuth to connect to the Bing Ads APIs.

Register a Bing Ads Account

Complete the following steps to sign up for a Bing Ads account and obtain the CustomerId and (optional) AccountId:

1. Sign up for a Bing Ads account in the or at the for a sandbox account.

2. Select Settings > Accounts and Billing and select a single account. The AccountId and CustomerId (cid) are displayed on the account's page and in the page's URL.

Get a Developer Token

To use the Bing Ads APIs, you must have a DeveloperToken in addition to the CustomerId. You must have the Super Admin role in Bing Ads to create a developer token, though you do not need special permissions to use the token.

1. Log in at the as a Microsoft Account user with the Bing Ads Super Admin role.

2. Click Request Token and take note of your developer token. You will set it in the DeveloperToken connection property.

Authenticate via OAuth Authentication

The Bing Ads APIs use the OAuth 2 standard.

1. If you have not done so already, sign up for a Bing Ads account in the or at the for a sandbox account.

2. Go to the ( for sandbox accounts), and login with your Microsoft Account credentials when prompted.

3. Under Azure Active Directory --> App registrations, click New registration.

4. Provide the application name and select an appropriate Supported account type. Not selecting to allow personal Microsoft accounts will prevent users with personal accounts from authenticating.

5. Set the Redirect URI to the page in your Web application where you would like users to be redirected with the OAuthVerifier

6. Register your application and take note of your Application (client) Id. You will use it as the OAuthClientId value in the OAuth grant flow.

7. In the Certificates & secrets section, click New client secret to generate a client secret and take note of the resulting value. You will use it as the OAuthClientSecret value.

Both the REST and SOAP APIs are supported and can be chosen using the Schema property.

1 Connecting to the Marketo REST API

Before you can connect to the Marketo REST API, you will need to create a custom service.

1.1 Creating a Custom Service

To create a custom service, follow the procedure below:

1. Navigate to the admin area of your Marketo application.

2. Click Users & Roles in the Security section.

3. Select the Roles tab and click New Role to create a new Role.

4. Enter a Role Name and select the permissions for the Role. The Access API permissions are specific to the REST API.

5. Now that an API Role is created, select the Users tab and click Invite New User.

6. Enter the new user information and select the role that was just created with API access. The API Only option can be selected to denote the user as an API Only user.

7. Now that a new user has been created, a new service will need to be created. Click the LaunchPoint option (Admin -> Integration -> LaunchPoint).

8. Click New Service.

9. Select the Custom service type and enter a display name and description.

10. Select the user you created.

1.2 Obtaining OAuth Credentials

To obtain the OAuthClientId and OAuthClientSecret, navigate to the LaunchPoint option on the Admin area.

Click the View Details link for the desired service. A window containing the authentication credentials is displayed.

1.3 Authenticating to the REST API

Once you have created a custom service and obtained your OAuth credentials, set the following to connect to data:

• Schema: Set this to REST.

• OAuthClientId: The OAuth Client ID associated with your custom service.

• OAuthClientSecret: The OAuth Client Secret associated with your custom service.

• RESTEndpoint: The URL of the REST Web service endpoint. This can be found on your Marketo Admin area on the Integration -> Web Services option in the REST API section.

The Identity Endpoint will not be needed.

2 Connecting to the Marketo SOAP API

To connect to the SOAP API, you will need to provide valid Marketo credentials. Specify the following to connect to data:

• Schema: Set this to SOAP.

• UserId: The client access ID is found within your Marketo admin SOAP API panel under Integration.

• EncryptionKey: The Marketo SOAP API Encryption Key. This key is generated on the Admin page of the Marketo website.

• SOAPEndpoint: The URL of the SOAP Web service endpoint, provided by Marketo on the Admin page of the Marketo website.

The following are the connection properties for Marketo. Not all properties are required. Enter only property values pertaining to your installation. Several properties will be automatically initialized with the appRules defaults.