> For the complete documentation index, see [llms.txt](https://docs.introist.com/knowledge-base/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.introist.com/knowledge-base/build/data-sources/data-mapping.md).

# Data Mapping

Data mapping connects fields from your external data source (such as an HRIS) to the matching employee fields in Introist.

This ensures that the right information flows into your automations — keeping them accurate, consistent, and up to date.

***

### Why Mapping Matters

When data source fields are correctly mapped:

* Employee information is kept in sync between systems.
* Automations always have the latest and correct data to work with.
* You avoid manual updates and reduce the risk of mismatches.

Without proper mapping, fields in Introist may remain empty or outdated, affecting workflow triggers and personalization.

***

### Typical Examples

| first\_name | First Name              |
| ----------- | ----------------------- |
| hire\_date  | Start Date              |
| manager\_id | Manager (Employee link) |
| email       | Email                   |


---

# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.introist.com/knowledge-base/build/data-sources/data-mapping.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.