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

# Fields & mappings

Use **Settings → CRM → Fields** to find available CRM fields. Review the mapping locations below to see where Distro uses them. Workspace admins can search the saved field catalog and choose the provider and object to inspect.

## Refresh the field list

Field information refreshes automatically when needed. If the page reports a refresh in progress, use **Reload fields** to check for the updated catalog. Search by label or API name, and use **Show** to include active, retired, or all fields.

Refresh supports HubSpot Contacts and Companies, and Salesforce Contacts and Leads. Salesforce Account fields can be browsed from connection setup, but are not included in this refresh.

Saved fields from a disconnected provider may remain visible. They are identified as cached fields; reconnect that provider before refreshing them or relying on its delivery.

## Review where values go

| Mapping                                              | Where to edit it                                                                                          |
| ---------------------------------------------------- | --------------------------------------------------------------------------------------------------------- |
| Standard booking Email, Name, and Phone destinations | **CRM → Booking links**, or the link's **CRM sync → Custom settings**.                                    |
| A booking question's answer                          | Add or edit the question in the owning personal or group link.                                            |
| The question used for a Phone answer                 | **Phone answer source** in the owning link's CRM settings.                                                |
| Enriched person or company data                      | **Enrichment mappings** in this CRM area.                                                                 |
| Website form fields                                  | The connected [form mapping](/routing-forms/overview.md).                                                 |
| Outbound handoff fields                              | The [Outbound Form](/routing/outbound-routing/forms.md), followed by publishing and adopting its version. |

Edit a mapping in the settings that own it. Seeing a field in the catalog does not enable a CRM action. Review the link or router that uses it.

## If a destination is unavailable

Check the field catalog’s refresh status and the connected CRM user's access to the correct object. Booking-question mappings support writable text-compatible fields. A field can appear in the catalog without being a valid destination for every answer.

Removed or unavailable fields keep their saved mapping so you can see what needs attention. Choose an available destination for future bookings, or turn the link's [CRM sync](/booking-links/crm-sync.md) Off while correcting it.

An existing delivery keeps its captured mapping. Changing a question's destination does not rewrite that booking's delivery; review its [activity details](/crm/activity.md) before retrying.


---

# 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://help.distro.so/crm/fields-and-mappings.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.