Overview: Objects (Console)
This article provides an overview of the Objects workspace in Console.
In this article
Overview
In Console, the Objects workspace is where you can create and modify data objects. A data object is a digital container that holds specific pieces of information about something, like a customer, a company, or an interaction.
The objects you create and modify in the Objects workspace are blueprints for creating future records of customers, companies, interactions, and more.
The Objects workspace in Console is where you can create data objects. A data objects is a digital container that holds specific pieces of information about something, like a customer, a company, or an interaction.
If you click one of the objects in the Objects workspace, you’ll be presented with a page with three tabs:
Details
Fields
Triggers
Note: Interactions don’t support Triggers, so the Triggers tab isn’t included.
Read the sections below to learn more about the Details, Fields, and Triggers sections.
Details
The Details tab of an object shows basic information about the object.
See the list below for a breakdown of what each of the fields in the Object container means.
Label: The name of the object.
API Name: The backend name of the object. This is used when creating triggers or advanced integrations with the object.
Can Create Custom Fields: Indicates whether administrators can add new, custom fields to the object.
Can Create Triggers: Indicates whether administrators can create triggers to make something happen when an object is created or modified. We’ll cover this more in the Triggers section below.
Can Use In Workflows: Indicates whether workflows can interact with objects of this type.
Created At: The timestamp of when the object was created.
Updated At: The timestamp of when the object was last modified.
Created By: The user who created the object.
Updated By: The user who last modified the object.
Fields
The Fields tab of an object shows the type of information contained by the object.
Each field contains the following properties:
Label: The name of the field.
API Name: The backend name of the object. This is used when creating triggers or advanced integrations with the object.
Type: The type of data contained.
Required: Specifies whether the field must be specified in order to create an object.
Read Only: Specifies whether the field can be modified or only viewed/read.
Triggers
The Triggers tab of an object shows what triggers are configured for the object. Though, you may be wondering: What is a trigger?
A trigger is an action that takes place when a condition occurs. In other words, when an object is created, modified, or deleted, a trigger can execute a workflow to automatically do something.
An example of a trigger.
When you click on an existing trigger (or when you click the New Trigger button in the top-right corner of the screen), a panel flies out from the right of the screen. This is where you can create or modify a trigger.
Label: The name of the trigger
Type: What event causes the trigger to run. There are three options:
Create: Runs whenever an object is created.
Update: Runs whenever an object is updated.
Delete: Runs whenever an object is deleted.
Workflow: The workflow that runs when the trigger occurs.
Workflow Version: The version of the workflow that runs when the trigger occurs.
Filters: You can use the filter interface to get granular about when you want the trigger to occur.
For example, in the screenshot above the trigger executes when a company is created.
You could, however, add a filter to only run the trigger if a company in a certain state is created, notifying a team that handles a specific region.
The possibilities of triggers are virtually limitless.
Read more
Creating an object
To learn more about creating an object, see: Create an object (Console).
Note: It’s not possible to delete an object.
More about fields
To learn more about adding, modifying, or removing object fields, see the articles listed below:
More about triggers
To learn more about adding, modifying, or remove object fields, see the articles listed below: