# Employee Fields

Employee fields are the backbone of how Introist understands and works with your people data.

They store the information that drives your automations — from basic details like *name* and *start date* to custom values like *training completion date*, *buddy assigned*, or *anniversary gift preference*.

Employee fields can:

* Store both standard and custom data about employees.
* Be used as triggers, filters, or dynamic content in workflows.
* Pull values automatically from integrated systems or be updated manually.
* Be tracked for changes over time to trigger specific actions.

By organizing and managing your employee fields, you ensure that automations always run with accurate and up-to-date information.

Typical examples of employee fields:

* Text: Job Title, Department, Manager Name
* Date: Start Date, Contract End Date, Next Review Date
* Number: Salary Bracket, Performance Score
* Select: Office Location, Employment Type

### Why Employee Fields Matter

Every automated action in Introist starts with data. Well-structured employee fields mean:

* Fewer manual updates
* More accurate workflows
* Better targeting and personalization


---

# Agent Instructions: 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:

```
GET https://docs.introist.com/knowledge-base/build/data/employee-fields.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
