> 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

Set up custom fields to add structured data to your issues, accounts, and contacts.

Custom fields store structured data on your records. They can be filled in manually, synced from your CRM, autofilled with AI, set through APIs or workflows, or filled through customer submissions. Configure them under **Settings > Customers > Account data**, **Settings > Customers > Contact fields**, or **Settings > Support > Issue data**.

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
* Email
* Datetime
* [Formulas](/pylon-docs/account-intelligence/fields/formulas.md)

<figure><img src="https://982123570-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9hXBoCTTNw5flARlUVJf%2Fuploads%2FVnr2GWcy5jC9nbXA7325%2FCleanShot%202024-09-29%20at%2021.34.57%402x.png?alt=media&amp;token=95cb3ef9-b440-4adf-bec5-5ec04c444d58" 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.

### Who can fill a field value?

For editable account and issue fields created in Pylon, an Admin with access to the field's settings can configure **Who can fill the field value?** in the field's **Settings** tab. Choose **Anyone**, **Some members** (specific users and teams), or **Only me**. A user must also have permission to edit the record.

This setting controls who can fill values, rather than who can see the field. It isn't available for contact fields, CRM-synced fields, formulas, rollups, or web research fields. Configure customer access separately in [customer portal settings](/pylon-docs/customer-portal/styling-and-customization.md).

### Select and multi-select options

Choose **Custom**, **A to Z**, or **Z to A** to order a select field's options. With **Custom**, drag options into the order you want. The same ordering choices apply to multi-select fields.

For issue fields, you can also limit which options appear based on other field values. See [Field value visibility](/pylon-docs/platform/custom-fields/required-and-conditional-fields.md#field-value-visibility).

### :sparkles: AI Autofill

{% hint style="info" %}
AI autofilled fields can be manually updated when your record and field permissions allow it. 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.

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.

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="https://982123570-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9hXBoCTTNw5flARlUVJf%2Fuploads%2F0ij95JINoKL5eCIv7u97%2FCleanShot%202024-09-29%20at%2021.39.53%402x.png?alt=media&amp;token=a750d6f5-b865-4854-a6ca-3d7d13ed0072" 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 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-fields.md?ask=<question>&goal=<user_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.