Cloze API filtering rules. Functionally similar to Zapier filter steps, for more information on this advanced, optional feature see What Are API Filters?.

Examples:

View all stage changes within the Enterprise Customer segment

{"company" : {"segment" : "Enterprise Customer"} ,"changes" : {"stage":{"after":"*"} } }

Tip Use the Cloze UI to see what custom fields and values are available for filtering against.

Cloze API filtering rules. Functionally similar to Zapier filter steps, for more information on this advanced, optional feature see What Are API Filters?.

Examples:

Trigger when a Deal is Won.

{"project" : {"segment" : "Deal"} ,"changes" : {"stage":{"after":"Won"} } }

Trigger when a custom field Forecast changes to Commit

{ "changes" : { "Forecast" : {"after":"Commit"} } }

Trigger when a the Number of Seats on a Concierge Service Deal changes.

{"project" : {"segment" : "Deal", "customFields":[{"id":"Concierge Service","value":"Yes"}]} ,"changes" : {"Number of Seats":{"after":"*"} } }

Tip Use the Cloze UI to see what custom fields and values are available for filtering against.

Adds a single keyword even if it contains spaces or punctuation marks.

Adds one or more keywords, separated by spaces or punctuation marks.

Always assign to this user.

Only assign to this user if not already assigned.

Sub-team placement, e.g. /US/West.

Identifies the source application of this Entity. Enter the fully-qualified domain name of the URL where you log into the source application. For example, if the source application is Salesforce and you log into "https://na11.salesforce.com", enter "na11.salesforce.com". For more information see What Are App Links?.

The name of the source application. Cloze places a link with this title in the created Entity.

A URL to the Entity information in the source application. Cloze will place a link to this URL in the created Entity. Choose a URL from the source application trigger if one is available. See What Are App Links? for more information.

A unique ID for the entity in the source application. Choose a field from the source application trigger so that later updates to the document contain the same ID. See What Are App Links? for more information.

Specify additional phone, address and other entries. See How To Use Cloze Additional Fields.

Fully qualified domain name e.g. salesforce.com of source application.

An identifier for the note from the source application.

The name of the person or project this note is about.

The email or social address of the person or project this note is about.

Text or HTML are supported. Set Body Type as appropriate.

The body type (text/html).

The name of the source application. Cloze places a link with this title in the created Note.

Choose a URL from the source application trigger if one is available. Cloze will place a link to this URL in the created Note.

Sometimes additional fields are needed for people in Cloze. This includes multiple references. As an advanced feature, you can utilize this field to specify additional values for the communication.

Examples

Adds a single keyword even if it contains spaces or punctuation marks.

Adds one or more keywords, separated by spaces or punctuation marks.

Sub-team placement, e.g. /US/West.

Choose one of your predefined Project or Deal Types.

An optional value associated with this project. Common uses are deal values from CRM or sales pipeline management applications; or project cost or billable value in project management applications.

The name of the source application. Cloze places a link with this title in the created Project.

Choose a URL from the source application trigger if one is available. Cloze will place a link to this URL in the created Person.

Identifies the source application of this Project. Enter the fully-qualified domain name of the URL where you log into the source application. For example, if the source application is Salesforce and you log into "https://na11.salesforce.com/...", enter "salesforce.com". See What Are App Links? for more information.

An identifier for the project from the source system. See What Are App Links? for more information.

If you have more than one set of App Links fields you want to track with the project, add them here. See What Are App Links in Cloze? and How to Use Additional Fields in Cloze for more information.

Cloze API filtering rules. Functionally similar to Zapier filter steps, for more information on this advanced, optional feature see What Are API Filters?.

Examples:

Trigger when a Customer segment person enters Active stage

{"person" : {"segment" : "Customer"} ,"changes" : {"stage":{"after":"Active"} } }

Trigger when the next step of a Potential Partner is Final Agreement

{"person" : {"segment" : "Partner", "stage" : "Potential"} ,"changes" : {"step":{"after":"Final Agreement"} } }

Trigger when a Potential Partner in Marketing becomes a Director.

{"person" : {"segment" : "Partner", "stage" : "Potential", "customFields":[{"id":"Department","value":"Marketing"}]} ,"changes" : {"Role":{"after":"Director"} } }

Tip Use the Cloze UI to see what custom fields and values are available for filtering against.

The style of the communication (is it most like an email, call, or direct (Instant Message)).

The email, phone number, social handle (twitter:address/facebook:address/linkedin:address), or custom address (custom:address) of the sender.

The address of the recipient (email, phone number, social handle, or custom address).

Skip the Inbox view and display only on the Timeline.

A unique identifier describing the thread of this message (message threading). All messages with this same threadid will be threaded together in the Cloze UI. An example of a good threadid would be a unique support ticket number.

The name of the source application; creates an "Open In " link inside the message.

A URL to the source application; creates an Open In link inside the message.

Description

Sometimes additional fields are needed for people in Cloze. This includes multiple recipients. As an advanced feature, you can utilize this field to specify additional values for the communication.

Examples

Pick an email or other identifier understood by Cloze (e.g. mike@cloze.com or calendar.google.com:123456).

An address of the person this event is about.

The name of the source application. Cloze places a link with this title in the created Person.

Choose a URL from the source application trigger if one is available. Cloze will place a link to this URL in the created Person.

Sometimes additional fields are needed for people in Cloze. This includes multiple references. As an advanced feature, you can utilize this field to specify additional values for the communication.

Examples

Birthday.

Gender.

Adds one or more keywords, separated by spaces or punctuation marks.

Sub-team placement, e.g. /US/West.

Adds a single keyword even if it contains spaces.

Always assign to this user.

Only assign to this user if not already assigned.

Shares the person information with someone on your Cloze team.

Adds the Person to one of your previously defind Cloze lists.

If updating an existing person, removes that person from the list you specify.

Identifies the source application of this Person. Enter the fully-qualified domain name of the URL where you log into the source application (for example, if your source app is MailChimp and you log into https://mailchimp.com, enter "mailchimp.com"). For more infomation, see What Are App Links?.

A unique ID for the person in the source application. Choose a field from the source application trigger so that later updates to the document contain the same ID.

The name of the source application. Cloze places a link with this title in the created Person.

Choose a URL from the source application trigger if one is available. Cloze will place a link to this URL in the created Person.

Specify additional email, phone, address and other entries. See How To Use Cloze Additional Fields.

What needs to be done.

The date and time when to do it.

Other people, if any, involved in the task.