Quicklinks

Objects

Custom Objects are how data is modeled in Kizen. Custom objects can optionally include workflow data.

The following default fields make up a custom object:

Field NameTypeNotes
NameTextThe name of the entity
OwnerTeam SelectorA single-select of all team members in your business
Date CreatedDateTime

Objects with Workflows

When a custom object has a workflow, this introduces the concept of a record “stage”. When an object has stage information, a board view becomes available in the UI to view your records on a Kanban board according to their current stage.

The following additional default fields are enabled on objects with a workflow:

Field NameTypeNotes
ValueMoneyConditionally available, only if "Track Entity $ Value" is enabled for the object.
StageStageRequired. Default value is the first stage in the pipeline for the object.
Estimated Close DateDateTime
Actual Close DateDateTimeRead-Only in the UI. The value is set automatically when the entity is moved to a closed/won stage.
Percentage Chance to Close - LowDecimalConditionally available, if "Include % Chance to Close" is enabled for the object. Range from 0 to 1.
Percentage Chance to Close - HighDecimalConditionally available, if "Include % Chance to Close" is enabled for the object. Range from 0 to 1.
Reasons LostDropdownConditionally available, if the entity is in a "Lost" stage in the pipeline.

Contact Object

The contact object (sometimes referred to as theĀ client object) is a special object that has default fields for storing personal information for individuals.

Contact object default fields:

Field NameTypeNotes
First NameText
Last NameText
EmailEmail
Business PhonePhone
Home PhonePhone
TitlesDynamic Tag
TagsDynamic Tag
BirthdayDate
Email StatusDropdown Options are fixed and cannot be changed.
TimezoneTimezoneSpecial dropdown of fixed timezone options.
Full NameCalculated ValueThis value is calculated by concatenating the first and last name fields. Cannot be independently changed.
Date CreatedDateTimeImmutable, and set automatically.

Recommended Reading

Many of the API examples use the object identifier, rather than the object ID. Read about what the object identifier is, and why it's preferred over using object IDs directly in the API Names documentation.

API Names

Each object has an API name that is unique to the business.

Object Best Practices

Tips for working with custom object and field metadata.

Retrieving Object Metadata

To fetch the metadata for a custom object, make a GET call to /api/custom-objects/{object_identifier}. This API endpoint will return owner and access data for the object, as well as metadata about fields, relationships, and pipeline stages if applicable:

curl -X GET "https://app.go.kizen.com/api/custom-objects/{object_identifier}" \
 -H 'accept: application/json' 

Up Next

With an understanding of custom objects, check out these documents to learn more:

Permissions

Understanding user roles and permissions when interacting with the API.

Fields

Custom fields extend the default data model to store additional data.