> 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-fields.md).

# Custom Fields

Custom fields on objects in Pylon allow you to store additional custom data on each object. They can be filled in manually, synced from your CRM, autofilled with AI, set via. APIs or workflows, or filled via. end user submission. You can configure them in Settings > Pylon in the "[Account Fields](https://app.usepylon.com/settings/account-custom-fields)", "[Contact Fields](https://app.usepylon.com/settings/contact-custom-fields)", and "[Issue Fields](https://app.usepylon.com/settings/issue-custom-fields?tab=fields)" pages.

Custom fields can be used across the product in views, analytics, triggers, macros, and more.

## Overview

### Field Types

Pylon supports the following custom field types:

* Text
* Number
* Decimal
* Select
* Multi-select
* Boolean
* Date
* User
* Contact
* URL
* Datetime
* [Formulas](/pylon-docs/account-intelligence/fields/formulas.md)

<figure><img src="/files/5irSoNtwutMj8tqo6IJA" alt=""><figcaption><p>Example of a "Product Area" custom field</p></figcaption></figure>

***

## Usage

### Manually Fill

Custom fields can be manually filled from their individual record pages.

Issue fields: filled in via. the issue sidebar.

Account fields: filled in via. the accounts page.

Contact fields: filled in via. the contacts page.

### :sparkles: AI Autofill&#x20;

{% hint style="info" %}
AI autofilled fields can always be manually updated! Once manually updated on a record, they will not be overridden by AI in the future.
{% endhint %}

Custom fields can be autofilled using AI to reduce manual work.&#x20;

Fields with a :sparkles: by their name are fields that are fields that are being automatically filled via. AI.

For account fields specifically, learn more here [AI Fields](/pylon-docs/account-intelligence/fields/ai-fields.md).

### Sync from CRM

Account and contact custom fields can be synced directly from your CRM. Multiple times a day these values will be updated from the latest data in your CRM.&#x20;

To enable this, you should connect your CRM via the [Apps Directory](https://app.usepylon.com/apps). More details can be found in the [CRM](/pylon-docs/integrations/crm.md) articles.

### Fill via. API

Use our [PATCH /issues](/pylon-docs/developer/api/api-reference/issues.md), [PATCH /contacts](/pylon-docs/developer/api/api-reference/contacts.md), and [PATCH /accounts](/pylon-docs/developer/api/api-reference/accounts.md) API endpoints in order to set custom field values via. API.

For issues raised from the Chat Widget, our JavaScript API can set custom field values on issue submission.

### Fill via. Formulas

Use [Formulas](/pylon-docs/account-intelligence/fields/formulas.md) to automatically fill in field values uses calculations.

### Fill via. Triggers or Macros

Use the "Set custom field value" action on a trigger or macro in order to programmatically fill a custom field value.

<figure><img src="/files/LuvRbDuQFQQ8fQN9Qq14" alt=""><figcaption></figcaption></figure>

### Fill via. End User Submission

Use [Ticket Forms](/pylon-docs/support-workflows/ticket-forms.md), collect data [directly in Slack](/pylon-docs/integrations/chat/slack/collect-data.md), or allow customers to set fields via. the customer portal to populate custom field values based on user input.


---

# 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.usepylon.com/pylon-docs/platform/custom-fields.md?ask=<question>&goal=<endgoal>
```

`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.