Your First Integration in 60 Minutes

Last Modified on 03/25/2019 10:30 am MDT

Introduction

So you want to try out the Cloud Elements platform and see if it solves your use case?

While our platform can realize many different use cases (e.g. 2016 & 2018 Top Marketplaces), this tutorial is specifically designed to guide you, a developer or system integrator, through setting up a contact sync between different endpoint services using Cloud Elements. During this tutorial, you will learn how to:

The intent of this tutorial is to familiarize you with the components of the Cloud Elements platform through a simple data sync use case. We'll use Salesforce Sales Cloud, HubSpot Marketing, and SugarCRM as examples, but the concepts and workflows in this tutorial still apply to other use cases—if a contact sync is not your exact use case, this can still help you along your integration path!

This tutorial is also designed to be accessible people who may not have much experience with coding or APIs. You won't have to be a ninja-level programmer to follow along, but familiarity with these concepts will be helpful:

The first step in setting up our contact sync is to authorize the Salesforce Sales Cloud, HubSpot Marketing, and SugarCRM elements applications to connect to your accounts. To do so, you will authenticate with the API providers to create element instances of the Salesforce Sales Cloud, HubSpot Marketing, and SugarCRM.

First, we'll walk you through a simple authentication of an instance.

Here's a video that show how to create an element instance

Authenticating Instances

Authenticate a Salesforce Sales Cloud Instance

In this step, you will authenticate an element instance with Salesforce Sales Cloud. As part of that authentication, you will enable events so Cloud Elements can monitor any additions or changes to your list of contacts.

Below is a quick overview about how to authenticate, but you can also walk through detailed instructions for authenticating either by using the UI or via API.

Find Salesforce Sales Cloud in the Elements Catalog, hover over the card, and click Authenticate.

On the Create Instance page, enter a name for your instance (for this tutorial, use Salesforce Contacts), enable events by clicking Events Enabled, and then select webhook.

In the Objects to Monitor for Changes field, enter Contact.

So we receive event notifications, in Event Notification Callback URL enter https://api.cloud-elements.com/elements/api-v2/events/sfdc.If you would like to test webhook functionality during this integration, the Webhook Tester site provides a free bucket from which to send requests and view payloads. For more information about events, see the Events Overview.

Your setup should look like this (note the code example created as you enter data):

Click Create Instance, log in to Salesforce and allow the connection to Cloud Elements.

After you authenticate the element instance we suggest that you test it out using the API docs.

Click Test in the API docs.

Note on the left that we already selected the instance you just created, so any APIs you try execute against that instance.

Click to open GET /accounts, and then click Try it out.

Scroll down, and then click Execute. The response body includes all of the accounts in your Salesforce account.

Once you finish testing, move on to authenticate with HubSpot Marketing.

Authenticate a HubSpot Marketing Instance

In this step, you will authenticate an element instance with HubSpot Marketing, allowing . Because this example creates a one-directional sync from Salesforce to HubSpot, you do not need to configure events for HubSpot.

Navigate to the Elements Catalog and search for HubSpot Marketing.

Hover over the element card, and then click Authenticate.

As you did when authenticating the Salesforce Sales Cloud instance, you will also use Oauth 2.0 to authenticate with HubSpot Marketing.

Name your instance (for this tutorial, use HubSpot Contacts).

Click Create Instance, and then authorize Cloud Elements.

Like the Salesforce Sales Cloud instance, we suggest that you test HubSpot out using the API docs. Click Test in the API docs, open GET /contacts, click Try it out, and then click Execute. The response body includes all of the contacts in your HubSpot account.

Authenticate a SugarCRM Instance

In this step, you will authenticate an element instance with SugarCRM. Because this example creates a one-directional sync from Salesforce to SugarCRM, you do not need to configure events for SugarCRMbSpot.

Like the Salesforce Sales Cloud instance, we suggest that you test SugarCRM out using the API docs. Click Test in the API docs, open GET /contacts, click Try it out, and then click Execute. The response body includes all of the contacts in your SugarCRM account.

With the authenticated instances, you're now ready to clone the Basic Contacts VDR template in order to map /contacts object across different services.

Clone Basic Contact VDR Template

Log in to Cloud Elements and navigate to the Virtual Data Resources page.

Hover over the basic-contacts VDR template, and then click Mappings to clone the VDR, or to see the VDR's name and URL, system level fields, and mapped elements.

Navigate to the Mappings tab of the basic-contacts VDR template and click Clone.

Search for and select the elements you want to include in the VDR (for this tutorial, select Salesforce, HubSpot Marketing, SugarCRM), and then click Next. You can also click the check box next to the Element Name column header to select or de-select all listed elements.

Select the level at which the system fields should be created in the VDR (for this tutorial, select Organization), and then click Next.

Click Save. For this tutorial, do not change the name from basic-contact. In the future, we suggest modifying the name, although we will use the basic-contact name in our formula workflow.

Your new VDR now appears in the My Resources list and is ready for transformations.