Do you store my data?

No, Cloud Elements is a complete pass through. Files are also never saved. We encrypt and stream all files through to the endpoint.

How do transformations work?

We built a transformation engine to transform your JSON data from one format to another. For example, you can transform data from the standard Salesforce format to the format that HubSpot would expect.

First you create an Object Definition using the POST /organizations/objects/definitions API or in our tool, Element Mapper. This Object Definition will exist across your entire organization and can be applied to any Instance of any Element.

Next, go into each endpoint whose data you want to transform and map their data to your Object Definition.

To utilize this transformation you need to use the /{objectName} APIs. The {objectName} will be replaced by the name of your Object Definition. Then any data flowing through that API, to or from the endpoint, will be transformed.

If you have a very complex transformation or are trying to transform field values, you can include your own custom JavaScript.

How much latency can I expect using Cloud Elements?

We have gone to great lengths to ensure that we are passing your calls through as quickly as possible. On average we will only add about 100 to 200 milliseconds to your API calls

However, we will always be at the mercy of the endpoint we are calling. Some SOAP based APIs may take longer than a REST API.

How does authentication work? (To Cloud Elements and the Endpoint)

Authentication to any of Cloud Elements’ APIs will use the same format. You will include one Header with a User Secret and an Organization Secret for platform APIs. For a call to an instance you will need to include an Element Token.

For example, for a call to GET /accounts, the Authorization header will look like this:

Authorization: User <user secret>, Organization <organization secret>

A call to an instance GET /hubs/crm/accounts in Salesforce will look like this:

Authorization: User <user secret>, Organization <organization secret>, Element <element token>

Authorization to any endpoint will be handled when you create an Element Instance. If an endpoint is Basic Authentication or SOAP, like NetSuite or Pipedrive, we will save your UserName and Password for future requests. You will receive an Element Token for that instance that you will send in the Authentication header.

For OAuth2 Elements, such as Box and Google Drive, you will go through the OAuth2 flow to log in at the provider. We will keep that connection alive for you forever. After the instance is created, just save the Element Token and we will handle refreshing the Access-Tokens for you.

What is an Instance?

An Instance is one authenticated user for any Element. When you authenticate to Box you will enter the email and password associated with your account. Every call you make through that instance will use your account in Box. You will need to create a different instance for each user or customer that is connecting to any Element.

Sample Requests

Postman Collections

How to use the collections:
  1. Click on the collection you want to download. You will be able to save it as a text file (.txt).
  2. In Postman, select import collection.
  3. Upload the file.

Create OAuth instance

Screen Shot 2015-06-22 at 2.11.41 PM

Object Definitions and Transformations

Screen Shot 2015-06-23 at 9.05.37 AM

Manage Users and Accounts

Screen Shot 2015-06-24 at 12.53.03 PM
Release Notes

Need some help?

  • Check out our developer documentation for more information on Endpoint setup, creating instances, sample code.
  • Can’t find what you are looking for? Submit a support request at the ‘Help’ button.