> For the complete documentation index, see [llms.txt](https://docs.distro.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.distro.so/data-and-integrations/field-catalog.md).

# Field catalog

The Field catalog gives your workspace a consistent set of person and company fields for workflows, rulebooks, booking questions, and records.

**Open Field catalog.** Select the person or company fields you need.

## Review or add a field

Standard fields are available across the workspace. Use **New field** for a custom value.

Choose a stable key, clear label, and appropriate type. For a selection field, configure its allowed choices.

Use the same meaning consistently. A numeric headcount field and a company-size range are different values and should not be compared as if they were identical.

## Map source values

Review **Filled by** for a field and configure the relevant source mappings. Sources can include CRM records, form capture, website activity, CSV uploads, and booking links.

Mapping a CRM property into the catalog makes the value available for the configured data model. Writing to the CRM still requires an explicit supported workflow action or sync configuration.

## Set source priority

Open **Source priority** to configure the catalog order. **Actions**, the manual override source, stays first. A field can have an individual priority override; otherwise it follows the catalog order.

In the current stored-data model, manual and CRM-labelled values can be retained separately. Other non-CRM inputs can share the ordinary stored property rather than retaining a complete separate value and history for every source.

Use the actual stored fields and run input to verify a conflict. Do not assume changing priority can recover a prior form or enrichment value that was overwritten in the shared property. Source priority does not guarantee full historical provenance for every non-CRM source.

## Use fields in routing

In a workflow's data picker, choose the relevant **Lead** or company field. In a rulebook, declare it under **Inputs** before using it in a condition.

Booking questions can map answers into the appropriate person field.

Missing values still need a deliberate path. Source priority does not guarantee every lead has the value.

## Inspect records

Use **View records** to review the people or companies behind the fields, where Records is enabled for your workspace.

For an unexpected workflow value, check the original source, mapping, source priority, and the run's retained inputs.

See [Use data in steps](/workflows/use-data.md) and [Fit score](/routing/fit-score.md).

For practical record work, see [Browse records](/records/browse.md), [CSV import](/records/import-csv.md) and [Push to CRM](/records/push-to-crm.md).


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.distro.so/data-and-integrations/field-catalog.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 `build a script that syncs our docs to a CMS` 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.