> For the complete documentation index, see [llms.txt](https://docs.sprinthub.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sprinthub.com/en/topics/system-settings/custom-objects.md). # Custom Objects ## Introduction Custom Objects are structures defined to store various information within a contact. The same contact can contain any number of Custom Objects, which can be created through automations or manually. **Examples of possible Custom Objects:** * Feedbacks: service ID, feedback message (optional), and service rating. * Order: order ID, order name, and unit value. * Requested Exams: exam type, appointment date, laboratory. * Event Participations: event name, date, attendance confirmed, notes. * Internal Trainings: training name, workload, date, completion (yes/no). ## Creating a Custom Object definition Enter the **Settings**menu, and then into **Custom Objects**. After that, click the button **New**, to create a new definition. The value entered in the field **Name (Plural)** will be displayed as a new tab in the profile of all contacts, representing a list of linked objects.\ For a Custom Object to be available in the instance, it is necessary to check the option **Published**. If you want to allow the automatic creation of these objects through chatbots, automations, integrated webhooks, or through the contacts page itself, also enable the option **Allow dynamic creation of objects**.

Settings Menu.

Definition list.

Edit Definition screen.

## Field Settings When creating a new field for the definition of a Custom Object, it is necessary to select the **data type**, such as *Text*, *Number*, *Date*, among others — as listed in the image below. Each field can have some additional settings: * **Required:** Requires that the field be filled in when creating or editing the custom object. * **Unique Identifier:** Defines whether the field value will be exclusive to each object, working as a unique identifier (useful for cases such as order IDs, protocol codes, etc.). * **Default Value:** Value that will be filled in automatically when creating a new object, and can be changed manually if necessary. * **Alias:** Defines how the field will be referenced in other parts of the system, such as when using *tokens*. See more about custom object tokens.

List of field types.

Field editing screen.

## Filling in an Object Manually When accessing the full data of a lead, it will be possible to view the tab **Event Participations**, where the custom objects associated with it are listed. You can **relate a pre-existing custom object** to a lead — ideal, for example, in cases of fixed subscription plans, where it is enough to relate it to the lead without creating a new object from scratch.\ However, in this example, we will choose to create a new custom object. After being created, the object will automatically appear in the lead's tab **Event Participations** of the lead.\ This data can be used in **tokens** (for customizations in messages, for example) or consulted via **automations**, as needed.

Full contact data.

Filling in an object.

Registered event.

--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.sprinthub.com/en/topics/system-settings/custom-objects.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.