Installing & Connecting Cloudingo
  • 31 Oct 2022
  • 15 Minutes to read
  • PDF

Installing & Connecting Cloudingo

  • PDF

Step 1. Install the Agent


Before you can get started, you must install and deploy the Cloudingo Agent inside salesforce.com. The Cloudingo Agent is required as it provides a secure and streamlined means of communication.

You can find the Cloudingo Agent in the Salesforce AppExchange.


Installing to Sandbox from AppExchange
When installing Cloudingo to a Sandbox from AppExchange, you will initially be asked to enter in your Production credentials. But, when you move past this step, you will be asked which environment you wish to install to - where you will choose your Sandbox environment.




A note about which profiles to choose during installation:
During the installation process, be sure that you choose the appropriate Salesforce profiles to grant access to. Whoever will be using Cloudingo will need access. It might be a good idea to make note ahead of time which users will be using Cloudingo (using their own Salesforce connection), and what Salesforce profiles those users are assigned to on the Salesforce side. Then, just be sure to choose the appropriate profile(s) during installation.

Step 2. Create a Cloudingo Account

Create a Cloudingo account by filling out the registration form here.


Step 3. Login to Cloudingo and Connect

You may have already connected to Salesforce during your initial trial setup. If not, login to Cloudingo and click "Connect to Salesforce" from the platform dropdown on the Cloudingo dashboard. Use the 'Login with Salesforce' option to connect the first time. Use the Cloudingo Username & Password fields if you have already been assigned a Cloudingo login by your Administrator as an additional user. 



A note about the Salesforce user connecting:

You must use a Salesforce Administrator account (or an Account using a profile with full read/write/update/delete permissions to the objects you will be working in - and all fields within those objects). These requirements are so that the queries required to pull the field values from the objects are not limited, allowing you to get the most complete record possible during merge without any data loss. 

In order for Salesforce to process the requests, the Salesforce user must also have View All and Modify All access on the objects as well. Cloudingo does not require any permissions outside of the requirements that Salesforce has for the query & merge process.


Step 4. Initial Index

During the initial indexing process, Cloudingo will search for patterns and clues that will help it to identify duplicate records. When indexing is complete, Cloudingo will run all the standard filters and show you the results. Don't worry; no changes will be made to your data at this point until you commit and save them.


Step 5. Use Prebuilt Filters or Create Your Own

Filters are like lenses that you can look through to see a bucket of records that look similar. As an example, if you wanted to see all leads that had the same email address and last name,  you could create a filter that looks at those specific lead fields.

Cloudingo comes with some standard filters that you can edit or you can just create your own. We encourage you to experiment!


That's it!

Now you're ready to create and edit more filters or start merging duplicates. Setup rules so that Cloudingo can automatically determine how records should be merge (defining the master & field selections chosen every time). Once you finish your rule configurations next, you can start automating the jobs to run on a schedule so that you can get back to work!


Troubleshooting Connection Problems

If your Cloudingo to Salesforce connection is not successful, first check to ensure that the Cloudingo agent is installed to your org. Login to Salesforce, go to Setup & search for Installed Packages. Look for the CloudingoAgent in the list. If it is not there, the agent is not installed yet. Download the app directly from the AppExchange. Our most current versions are also available on our login page as well (using a direct link to our installers).

Next, make sure that you are entering in the correct credentials. Physically try logging into Salesforce using the same username & password you are using within Cloudingo (if you are trying to establish the connection using your Salesforce credentials). Also make sure that the user in Salesforce is tied to a profile that has appropriate permissions to the objects that Cloudingo will be working with (Lead, Contact, Account, plus any custom objects you have enabled).

There are a few other reasons you may be having trouble:

Whitelisting Cloudingo Server IP Ranges

If your network requires you to list trusted IP ranges for communication, you must whitelist Cloudingo IP ranges as trusted.

  1. Go to Salesforce: Setup → Security Controls → Network Access → Trusted IP Ranges
  2. Click the “New” button
  3. Enter the following under "Trusted IP Ranges":
Starting IP Address
Ending IP Address
169.61.150.226
169.61.150.238

In some cases, you may also need to list the IP ranges as trusted under the user's profile ranges as well. See full help article here.

Revision History

Date Revised
Revisions
Nov. 22, 2020
Retired IPs
  • 50.22.78.2 to 50.22.78.6
  • 184.172.128.224 to 184.172.128.239
Sept. 25, 2020
Added IPs
  • 169.61.150.226 to 169.61.150.238
Dec. 12, 2017
Added IPs
  • 50.22.78.2 to 50.22.78.6
  • 184.172.128.224 to 184.172.128.239
Note: If you are unsure if whitelisting IP ranges as trusted is required in your Salesforce Org, please check with your internal Salesforce Administrator. The need for whitelisting IP ranges is based on your specific org's security settings.


Using Custom Domains

If you use a personalized custom URL for Salesforce, you can configure this in Cloudingo so that the login auto-redirects to your custom domain page automatically. This will also enable you to click links to records within the Cloudingo application (wherever they are available) and auto-redirect to the record you want to view using the custom URL.

For more information on how to configure your custom domain in Cloudingo, please visit our Help article here, and go to the 'Edit Account' section, bullet point #1 for custom domains.

Apex Classes

During the installation, you chose which profiles in Salesforce you authorized to have access to Cloudingo. Part of the permissions that get set during the install the necessary Apex Classes required for Cloudingo to communicate properly with Salesforce. Connection failures or other issues within the application can indicate that some or all of the Cloudingo classes are not enabled for the user's profile using Cloudingo.

Check your user profile in Salesforce to ensure that all Cloudingo Apex classes are enabled. 

  1. Login to Salesforce to find the user (whichever Salesforce user you are connecting Cloudingo with). 
  2. Go to Setup and search for Manage Users. 
  3. Click on Users in the Manage Users section. 
  4. Find the Cloudingo Salesforce user in your Users list, then click the link to get into the user’s details. 
  5. Once in the user’s page, you will see a link to the profile associated to that user. Click the specified profile link to get into the Profile. 
  6. Once in the profile, you will see a link at the top of the page or a section within the page for ‘Apex Classes’ (the location depends on the version of Salesforce you are using). 
  7. Click into the Apex Classes or choose Edit to get into the Apex Classes page. 
  8. Once in the Apex Classes page, on the left side you will see all available Apex Classes that are not currently enabled for the profile. On the right, you will see all Apex Classes already enabled for the profile. Search in the left side (disabled classes) for anything beginning with the word ‘Cloudingo’. If you find any disabled Cloudingo classes, click on the class to highlight it (you can multi-select if there is more than one) and use the arrow to enable the classes on the right. 
  9. Save your changes, and re-try your previous actions again to see if the problem is now resolved.

Salesforce Permission Requirements

You must use a Salesforce Administrator account (or an Account using a profile with full read/write/update/delete permissions) to the objects you will be working in, related objects, and update access to all fields within those objects. These requirements are so that the queries required to pull the field values from the objects are not limited, allowing you to get the most complete record possible during merge without any data loss. 

In order for Salesforce to process the requests, the Salesforce user must also have View All & Modify All access on the objects as well. Cloudingo does not require any permissions outside of the requirements that Salesforce has for the query & merge process. 

However, in order for the application to communicate and function with Salesforce, the connected user's profile must also have access to all of the Cloudingo Apex Classes (which are assigned during the initial installation of the Cloudingo agent). 

In Salesforce, under Setup → Manage Users, find the connected user and drill into the profile to pull up the profile details associated to that user. In the profile page, you will see a link or a section for the Apex Classes. Choose Edit to see the list of all available classes and to see what is already enabled. Make sure that any class beginning with 'Cloudingo' is enabled for that user's profile & save.


Video: Salesforce Permission Requirements



Connecting to Additional Orgs

Maybe you installed and connected Cloudingo initially to Production and realize you need to connect to Sandbox to run extra tests, or you installed Cloudingo to a Sandbox and now need to connect to Production. Good news! All of Cloudingo's licenses allow for one Production and one Sandbox connection to be connected simultaneously within the same Cloudingo Account. 

Need more than one Production and/or one Sandbox Connected?
If you need more than one Sandbox or more than one Production org connected, additional org connections can be added as necessary by contacting your Account Representative. Instructions for adding any additional connections will follow the same instructions provided below.


Step 1

Login to the Salesforce environment that you wish to connect & install the Cloudingo agent. You can install directly from Salesforce AppExchange, or you can go directly to our latest install using a link from our cloudingo.com login page. Beneath the login box, there will be links provided. 

Click 'PROD' to install directly to your Production org. Click 'SANDBOX' to install directly to your Sandbox org. 

Installing to Sandbox from AppExchange
When installing Cloudingo to a Sandbox from AppExchange, you will initially be asked to enter in your Production credentials. But, when you move past this step, you will be asked which environment you wish to install to - where you will choose your Sandbox environment.

Wait until the installation is complete before proceeding to the next step.


Step 2

Login to Cloudingo the way you normally do, then click the platform menu (top left) to choose to 'Add Another Salesforce Account'.

You will receive a warning reminding you to install the Cloudingo agent. If you have already done so, click 'Next' to move on to the connection details page.


When prompted, in the Display Name box, give the new connection a name to describe the environment that you are connecting to (such as Sandbox UAT, Production 2, Test). 

Then, use the 'Login with Salesforce' option to enter in your Salesforce credentials for the environment you wish to connect to (make sure you enter the credentials for the new environment you are connecting and not the credentials for the environment already connected).

If the connection is successful, the new connection should begin the indexing process and the dashboard will appear as normal once the indexing process completes. The indexing process can take a while if you are connecting to a large org. 

If the connection fails, please refer back to our connection troubleshooting steps described earlier in this article and retry the connection after correcting any problems. 

Once the new environment is connected, you will be able to toggle between the two environments using the checkbox options in the platform menu (top left).

You can also click the 'Make default account' link to default the environment you wish to automatically load when logging into Cloudingo in the future, so that the desired Account is defaulted.



Broken Connections

Occasionally, you may find yourself in a situation where things in Cloudingo stop running or you login to Cloudingo and see a problem on your dashboard. When a connection to Salesforce is broken, you will see a message on the dashboard that the Cloudingo agent needs to be installed (this is because the connection is failing and Cloudingo can no longer communicate to the Cloudingo agent installed in your org). You will also see an 'Invalid Account Credentials' error alert in the platform menu under the platform connection's Status. But, it is installed, and has been for some time! What gives?

There are a number of reasons this can happen. The most common reason is that there was some general type of connection failure to Salesforce at some point and re-authentication is required. Another reason could be that the connected user (the user whose credentials were being used to connect Cloudingo to Salesforce) has been deactivated on the Salesforce side or the Salesforce permissions required to operate Cloudingo have been changed on the Salesforce side. In some rare circumstances, accidental deletion of the Cloudingo agent from Salesforce could also be the culprit. But, whatever the case, you need to get back up and running! Here is what to do.

Production Environments

  • First, login to Salesforce and double check that the Cloudingo agent is still installed (under Setup >> Installed Packages). If you see it installed, this is great. Move on to the next step. If the Cloudingo agent is not installed, you will need to download & install it before you try reconnecting.
  • If the you are not the connected user and the main/connected user has in fact been deactivated in Salesforce, you will need to properly identify who should take over the Cloudingo connection and/or Admin responsibilities, and reconnect Cloudingo using the new user connection details (see next bullet point).
    • If the deactivated user is also set as the only (or the main) Cloudingo user, and you do not have a login to Cloudingo and/or need to have the Cloudingo username switched over to someone else, you will need to contact our Support Team for assistance. In your case details, please provide details on who the previous user was and who the new user taking over will be. We may ask you to grant Support access to your org as necessary to verify identity for security reasons.
  • If you are the connected user (or if you have a login to Cloudingo and will be reconnecting Cloudingo to Salesforce instead of the previously connected user), login to Cloudingo and attempt to re-authenticate the Salesforce credentials.
    You will need to login to Cloudingo using the Cloudingo username & password (you will not be able to use the 'Login with Salesforce' option yet since the connection is failing). The Cloudingo username will be your email address, and the password will be whatever you set during the activation process. If you do not remember your Cloudingo password, you can go to our main cloudingo.com login page and click the link for forgotten passwords there. When prompted, enter your email and instructions for recovering your password will be emailed to you directly and then login to Cloudingo once you have the password reset.

    Once logged into Cloudingo, click the platform menu (top left) and choose the 'Edit Salesforce Account' link beneath the Production connection that is failing. Click 'Edit Account' to get into the connection details page. Then, use the 'Login with Salesforce' option to re-enter your Salesforce credentials.

    If the connection is successful, the new connection should begin the indexing process and the dashboard will appear as normal once the indexing process completes. The indexing process can take a while if you are connecting to a large org.

    If the connection fails, please refer back to our connection troubleshooting steps described earlier in this article and retry the connection after correcting any problems. Even if you were connected successfully before the connection started to fail, you will need to step through these troubleshooting steps to ensure that nothing has changed on the Salesforce side.

    Production environments are not interchangeable. You cannot reconnect to a Production environment that has a different Org ID than the one you connected to with your initial license. If you need to switch Production environments, or if you need to add an additional connection to a different Production environment, you will need to contact your Account Representative for more information. 


Sandboxes

Sandboxes are also subjected to broken Salesforce connections for the same reasons we mention in the 'Broken Connections' details above (Salesforce user has been deactivated, Salesforce permission changes, general random Salesforce disconnect issues). However, Sandboxes will also lose their connections in Cloudingo whenever the Sandbox is refreshed. This is because Salesforce changes the internal Org ID anytime a Sandbox is refreshed, which Cloudingo uses in the connection details. When a connection to Salesforce is broken, you will see a message on the dashboard that the Cloudingo agent needs to be installed (this is because the connection is failing and Cloudingo can no longer communicate to the Cloudingo agent installed in your org). You will also see an 'Invalid Account Credentials' error alert in the platform menu under the Sandbox connection's Status.

Sandboxes can always be reconnected at any time by clicking the platform menu (top left) and using the 'Edit Salesforce Account' link that appears beneath your Sandbox connection. 

Click 'Edit Account' to get into the connection details page. 

Once in the connection details page, use the 'Login with Salesforce' option to enter in your Sandbox credentials again to reconnect. 

If the connection is successful, the new connection should begin the indexing process and the dashboard will appear as normal once the indexing process completes. The indexing process can take a while if you are connecting to a large org. 

If the connection fails, please refer back to our connection troubleshooting steps described earlier in this article and retry the connection after correcting any problems.

Sandboxes are interchangeable and can be swapped out with other Sandboxes as well, as long as the main portion of the Salesforce username/domain is the same. For example, if your prior Sandbox username ended in @xyz.com.uat and the new Sandbox username ends @xyz.com.full, you can enter in your new credentials without any issues and reconnect to the new Sandbox. If the main portion of the username/domain is not the same as your prior Sandbox (example; the new Sandbox does not contain the @xyz.com portion of the domain in the username), please contact our Support Team for assistance.

Warning
If you switch Sandbox connections from one Sandbox to another, filters & rules will be retained. However, please be aware that if filters & rules configured in the prior Sandbox used fields that are not available in your new Sandbox, you may encounter filter or rule errors when recalculating or processing. To avoid issues, please ensure that your environments contain the same fields (schema) in both environments, or edit any filters/rules in Cloudingo that were configured using fields that are not available in the new environment.

Was this article helpful?

What's Next