Omnisnia CRM Docs / Custom Objects

Custom Objects

A custom field adds a column to a record Omnisnia already has. A custom object adds a whole record type: you name it, declare its fields, and then create records against it. Use it for the things your business tracks that a CRM does not ship with — assets, subscriptions, permits, properties, service contracts.

Open Custom Objects in the Admin section of the navigation.

Plan feature. Custom objects are available on the Business plan and up. On lower tiers the navigation entry is hidden and its routes return an HTTP 402. See Plans & Usage Limits .

Define an object

The left column lists the objects you have defined and the New object form sits below it.

  1. Enter a Key (snake_case) — the stable identifier used in the API, e.g. service_contract. It does not change once created.
  2. Enter a Label — what people see, e.g. Service contract.
  3. Click Create.

The object opens in the right-hand panel with its label and key, ready for fields.

Draft one with AI

Instead of typing the key, label, and every field by hand, describe the object in the Describe an object for AI box — for example “a service contract with a customer, start and end dates, monthly value, and a renewal flag” — and click Draft with AI. The assistant fills in the key, the label, and a proposed field list, and tells you how many fields it drafted.

Nothing is saved yet. Review the key and label, change them if you want, and click Create: the object and its drafted fields are created together. The draft is a starting point, not a commitment — you can add and remove fields afterwards like any other object.

Add fields

With an object selected, use the Fields section:

  1. Field key — the identifier stored on each record.

  2. Field label — the heading shown on the form and in the record table.

  3. Type — one of:

    TypeStores
    TextFree text
    NumberA numeric value
    CurrencyA monetary amount
    DateA calendar date
    CheckboxTrue or false
    Select (one of)One value from a list you supply
    Multi-selectAny number of values from a list you supply
    Reference (relation)A pointer to another object or entity

  4. For Select and Multi-select, fill in Options with the choices, comma-separated. For Reference, the same box becomes Target (object/entity) — name what the field points at.

  5. Tick Required if a record cannot be saved without it.

  6. Click Add field.

Each field appears as a chip showing its label, its type, and an asterisk when it is required. Remove a field with the chip’s delete control.

Create and manage records

Once an object has at least one field, the New record form is generated from those field definitions — a text box for text, a picker for select, a checkbox for checkbox, a date input for date, and so on. Fill it in and click Create record.

Records are listed below the form in a table whose columns are your fields, with a record count in the heading. Edit loads a record back into the form (the button becomes Save, with Cancel to back out); the delete control removes it.

Deleting an object deletes all of its records, so you are asked to confirm first.

Through the API

Everything on this screen is also available over the REST API, split into two groups: /custom-object defines objects and their fields, and /objects/{key} reads and writes the records of the object with that key. The same plan gate applies — on a plan without custom objects both groups return 402.

← PreviousKnowledge Base