Cloud Elements Release Notes

Cloud Elements Version 2.150

January 28, 2018

Marketo: Merge contacts endpoint

We added the POST /contacts/{contactId}/merge endpoint so you can merge two or more known lead records into a single lead record. Merging does not overwrite existing information, but adds information where none already exists. The "merge to" record identified in the path becomes the single record for the contact (lead), while Marketo deletes the "merge from" record.

Pass the leadID of the contact to merge information into as part of the request, for example POST /contacts/350/merge. Include the leadID of the contact to merge information from in the body of the request. You can include a single lead record ("leadId": "355") or multiple records in a comma-separated list ("leadIds": "355,466").

Your body should include either a singe leadId or a comma-separated list of leadIds. Optionaly include "mergeInCRM": "true" to attempt to merge the designated records in a natively-synched CRM. This is valid only for instances with are natively synched to Salesforce.

In this example we're merging the information from leadID 351 into 350.

curl -X POST "https://api.cloud-elements.com/elements/api-v2/hubs/marketing/contacts/350/merge" -H "accept: application/json" -H "Authorization: User xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx, Organization xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxc, Element xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" -H "content-type: application/json" -d "{ \"leadId\": \"351\", \"mergeInCRM\": true}"

Box: New /file/comments endpoints

We added the following comments endpoints to the /files resource:

• GET /files/comments
• POST /file/comments
• GET /file/comments/{commentId}
• PATCH /file/comments/{commentId}
• DELETE /file/comments/{commentId}

Intacct.: Added support for the Callback Notification Signature Key

When setting up events in Intacct you can now include a Callback Notification Signature Key.

Intacct.: Added expense-reports resource

When setting up events in Intacct. you can now include a Callback Notification Signature Key.

Maximizer: Added support to filter GET response fields

You can now specify the fields to include in GET responses. Supported requests include:

• GET /addressbook-entries/{id}
• GET /companies/{id}
• GET /contacts/{id}
• GET /addresses/{id}
• GET /custom-records/{id}
• GET /opportunities/{id}
• GET /tasks/{id}

Audit Log shows changes to formulas

Changes to formulas now appear in the audit logs.

Cloud Elements Version 2.149

January 23, 2018

Elements

Google Suite: New element

We added the Google Suite element that you can connect to Google and manage calendars, contacts, groups, threads, and messages. Read the docs and authenticate an instance of your own.

Evernote: Added /files endpoints

We added the following DELETE endpoints:

• DELETE /files by path
• DELETE /files/{id}

QuickBooks Online: Updated CEQL for GET /reports/{id}

We updated the QuickBooks Online element so you can filter GET /reports/{id} requests by date ranges. For example, createdDateRange='Last Week'. Supported date ranges include Today, Yesterday This Week, This Week-to-date, Last Week, Last Week-to-date, and more. See the API docs for details.

Facebook Lead Ads: Added fields parameter to GET /leads/{leadId} endpoint

Use fields to specify the list of fields to include in the response.

Google Sheets: Fixed a bug in the Cloud Elements 2.0 API docs

When using the API docs in Cloud Elements 2.0 to make a GET /spreadsheets/{id}/worksheets request, the UI would not accept a spreadsheet Id. You can now use the API docs in Cloud Elements 2.0 to make the request.

Bullhorn: fields parameter accepts comma separated list of fields including nested fields

When making GET requests, you can include a comma separated list in fields to specify what Bullhorn returns in the response. You can include nested fields using dot notation. For example, id,address.countryCode returns the id and countryCode fields where countryCode is nested within an address object.

Formulas

You can create temporary formula instances that exist for a specified amount of time. Specify the time in seconds, such as 86400 for a day or 3600 for an hour. Every hour, Cloud Elements checks for temporary formula instances that have expired and deletes them. You can create temporary formula instances only through the Cloud Elements APIs.

To create a temporary formula instance, add "formula.instance.time.to.live": <seconds> to the settings object in a POST /formulas/{id}/instances request. Here's an example where the formula instance expires after one hour:

{
  "active": true,
  "configuration": {
    "<key>": "string"
  },
  "settings": {
    "notification.email": "string",
    "notification.webhook.url": "string",
    "api": "string",
    "formula.instance.time.to.live": 3600
  },
  "createdDate": "2018-01-23T16:33:47.431Z",
  "formula": {
    "active": true,
    "id": 0
  },
  "name": "string",
  "updatedDate": "2018-01-23T16:33:47.431Z"
}