> ## Documentation Index
> Fetch the complete documentation index at: https://docs.runspark.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Custom Fields

> Add custom data fields to your contacts

Custom fields let you store any data on your contacts beyond the built-in fields. Track industry-specific information, preferences, contract details — whatever your business needs.

## Built-in Fields

Every contact comes with standard fields:

| Field      | Type              |
| ---------- | ----------------- |
| First Name | Text              |
| Last Name  | Text              |
| Email      | Email             |
| Phone      | Phone             |
| Company    | Text              |
| Stage      | Pipeline stage    |
| Lead Score | Hot / Warm / Cool |
| Tags       | Multi-select      |
| Notes      | Long text         |
| Source     | Text              |

These cover the basics. Custom fields let you go further.

## Creating Custom Fields

Navigate to **Settings → Custom Fields** and click **Add Field**.

### Field Types

<AccordionGroup>
  <Accordion title="Text">
    A single line of text. Use for short values like license numbers, account IDs, or product names.

    **Example:** "Preferred Product" → "Enterprise Plan"
  </Accordion>

  <Accordion title="Long Text">
    Multi-line text for longer notes, descriptions, or context.

    **Example:** "Special Requirements" → "Needs wheelchair-accessible venue. Dietary restrictions: vegetarian, nut allergy."
  </Accordion>

  <Accordion title="Number">
    Numeric values. Use for quantities, sizes, scores, or any measurable data.

    **Example:** "Team Size" → 45
  </Accordion>

  <Accordion title="Date">
    A date value. Use for contract dates, birthdays, renewal dates, or follow-up deadlines.

    **Example:** "Contract Renewal" → "2026-09-15"
  </Accordion>

  <Accordion title="Dropdown">
    A single selection from a predefined list. Good for categories, tiers, or status values.

    **Example:** "Subscription Tier" → Options: Starter, Professional, Enterprise
  </Accordion>

  <Accordion title="Checkbox">
    A yes/no toggle. Use for binary attributes.

    **Example:** "NDA Signed" → ✅
  </Accordion>

  <Accordion title="URL">
    A web link. Use for websites, LinkedIn profiles, or external references.

    **Example:** "Website" → "[https://acme-corp.com](https://acme-corp.com)"
  </Accordion>

  <Accordion title="Email">
    An additional email field. Useful when contacts have multiple email addresses.

    **Example:** "Personal Email" → "[sarah.personal@email.com](mailto:sarah.personal@email.com)"
  </Accordion>
</AccordionGroup>

## Configuring a Custom Field

When creating a field, you'll set:

* **Field name** — the label shown in the UI and used by your agent
* **Field type** — one of the types above
* **Required** — whether the field must be filled in on every contact
* **Default value** — optional pre-filled value for new contacts
* **Options** — for dropdown fields, the list of available choices

<Tip>
  Use clear, descriptive field names. Your agent uses these names when reading and updating contacts. "Renewal Date" is much more useful than "Date 2" — both for you and your agent.
</Tip>

## Using Custom Fields

### In the Table View

Custom fields appear as columns in your Table view. You can sort and filter by custom field values just like built-in fields.

### On Contact Profiles

Custom fields show up in the contact detail panel. Edit them inline by clicking the value.

### With Your Agent

Your agent can read and write custom fields naturally:

> "Set the contract renewal date for Acme Corp to September 15th"

> "Show me all contacts where Subscription Tier is Enterprise"

> "Update the team size for Peak Fitness to 120"

When your agent processes a lead from a webhook or form, it can map incoming data to custom fields automatically. For example, if your lead form asks "How many employees do you have?", your agent can store that value in a "Team Size" custom field.

## Custom Fields in Knowledge Files

When you tell your agent about your custom fields in its knowledge files or instructions, it can use them more intelligently:

```markdown theme={null}
## Custom Fields

We track the following on every contact:
- **Subscription Tier** (Starter / Professional / Enterprise) — their current plan
- **Contract Renewal** (date) — when their contract is up for renewal
- **NDA Signed** (yes/no) — whether they've signed our NDA
- **Referral Source** (text) — who referred them to us

When processing new leads, always try to fill in the Subscription Tier 
based on what they mention in their inquiry. Default to Starter if unclear.
```

This helps your agent make smarter decisions about how to populate and use your data.

## Custom Fields in Filters and Views

Custom fields integrate with all view types:

* **Table view** — add as columns, sort and filter
* **Pipeline view** — use in card previews and filters
* **Dashboard** — reference in widget configurations (e.g., "show a pie chart of contacts by Subscription Tier")
* **Reports** — group and aggregate by custom field values

<Info>
  Custom fields are workspace-wide — every contact in your workspace has access to the same set of custom fields. You can't have different fields for different contact groups, but you can leave fields empty when they don't apply.
</Info>

## Managing Custom Fields

You can edit or delete custom fields from **Settings → Custom Fields**:

* **Renaming** a field updates it everywhere — on contacts, in views, and for your agent
* **Deleting** a field removes it and its data from all contacts. This is permanent.

<Warning>
  Deleting a custom field removes the data from every contact in your workspace. Export your data first if you need to preserve it.
</Warning>