> For the complete documentation index, see [llms.txt](https://docs.usepylon.com/pylon-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.usepylon.com/pylon-docs/platform/custom-objects.md).
# Custom Objects
Represent complex data and relationships within Pylon.
### Overview
Custom objects let you define your own data types in Pylon beyond the built-in Account, Contact, and Issue objects. Each custom object type has its own records, custom fields, and is usable across the product in filters, views, AI, and more.
You can create and manage custom object definitions in [Settings > Account Data > Objects](https://app.usepylon.com/settings/account-data?tab=objects).
### Creating a Custom Object
1. Go to **Settings > Account Data > Objects**
2. Click **Create Object**
3. Fill in the object details:
* **Label** — The display name for your object type (e.g., "Project", "Subscription")
* **Description** — An optional description of what this object represents
* **Icon URL** — An optional icon to visually distinguish this object type
* **Visibility** — Choose whether this object appears in the account sidebar, issue sidebar, or both
### Syncing from CRM
Custom objects can be synced from your [CRM](/pylon-docs/integrations/crm.md), allowing you to pull CRM-specific data into Pylon automatically.
To set up a sync:
1. Go to [Settings > Integrations](https://app.usepylon.com/apps) and select your CRM
2. In the **Data Mapping** section, click **Add Object**
3. Select the CRM object you want to sync from
4. Map it to an existing Pylon custom object, or create a new one directly from the sync setup
5. Save your changes
Once configured, Pylon will automatically pull records and field values from your CRM. You can also configure bidirectional sync of fields on the object.
### Using Custom Objects
Once you have custom objects set up, they integrate across Pylon just like built-in object types, for example:
* **Custom Fields** — Add additional [Custom Fields](/pylon-docs/platform/custom-fields.md) to add properties to custom objects.
* **Filter and sort** — Use the filter bar and column sorting to find specific records in the table view. Customize which columns are visible and reorder them to fit your workflow.
* **Analytics** — Custom object data flows into your analytics and reporting, so you can build views and track metrics around your custom data.
* **Triggers** — Reference custom object fields in triggers to automate workflows based on your custom data.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.usepylon.com/pylon-docs/platform/custom-objects.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
