Create a custom object

Last updated 1 August 2026

Companies, contacts and deals are not special. They are simply the three objects every workspace starts with, built on exactly the same machinery you use to create your own — so an object you define is a first-class citizen from the moment it exists.

1. Define the object

In Settings → Objects, create the object with a singular and a plural name — Property and Properties, Policy and Policies, Project and Projects. The plural names the list view; the singular labels individual records.

2. Add attributes

Add the fields the object needs. The available types are text, number, currency, date, checkbox, single and multi select, email, phone, URL, team member (a link to a user in your workspace), reference (a value looked up from a related record) and formula.

Mark fields required where a record genuinely makes no sense without them. Required rules are set per object, so a Property can demand an address without forcing that rule on anything else.

3. Relate it to other objects

Create relationships to connect your object to the rest of the CRM — a Property belongs to a Company, a Project has many Contacts. Relationships are what make the object part of your data model rather than an isolated list, and they are what reference fields follow to pull values across.

4. Optional: make it a pipeline

Any object can have a board. Add a select attribute, give its options stage names, and set each option's colour, whether it represents won or lost, and its probability. The object immediately gains a drag-and-drop board view grouped by that field, with weighted forecasting calculated from the amounts and probabilities.

This is why there is no separate "pipeline" feature to configure: a pipeline is a select field with stage options, so anything can have one and nothing is limited to a single pipeline.

The deal pipeline board with stages and weighted forecast

5. Start using it

There is no further setup. The moment the object exists it supports list and board views, saved views and filters, CSV import, tags, duplicate detection and merge, the activity timeline, attachments, marketing lists and campaigns, automation triggers and actions, reports and the API.

Adding a field to an object is safe and immediate — existing records simply have no value for it yet. It is far better to start with the fields you are certain about and add more as you learn what you actually track.