October 2024, R2

This document provides additional information about Claris Connect. For further information, see the Claris Help Center or visit the support resources on our website.

New features and enhancements

Claris Studio connector

Added the following trigger:

Added the following actions:

'Advanced' actions allow you to use JSON to programmatically create and update records.

Steps ran / Total steps for each flow run

In the History tab, a new Steps ran / Total steps column was added to show the number of steps that were executed in a given flow run out of the total number of steps in that flow. For example, if a flow has 10 steps but failed on step 3 during a run, the column will show 3/10 to indicate that only 3 steps were run in that flow, including the step that returned an error.

Claris product logos

Claris product logos in Claris Connect were updated to the newest versions.

HTTP utility

Reply with JSON - Now when using the Reply with JSON action, you are no longer required to enter anything in the Response data field.

Addressed issues

Intercom

The Search conversations action will no longer always return a "Query body must contain a query hash" error message.

User interface

Various minor fixes and improvements.

Claris Studio connector

Fixed a few cases where the default value for a field didn't match its description.

Documentation

Claris Connect Help

Updated the following topics:

Claris Connect Reference

Updated to add Claris Studio connector trigger and actions mentioned above.

APIs, technologies, or features to be deprecated

As Claris Connect evolves, the list of supported technologies, APIs, and features will change. As part of this evolution, certain connectors, actions, and features may be deprecated in favor of newer ones. Although deprecation does not mean the immediate removal of an item, you should migrate your flows away from deprecated technologies because these technologies may be removed in a future version of the product.