> For the complete documentation index, see [llms.txt](https://docs.stackerhq.com/stacker-astra/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stackerhq.com/stacker-astra/data-management/import-data-to-stacker-tables/stacker-tables-import-a-csv/external-ids.md).

# External IDs

Define an External ID field for each table. You can use any short text field as the External ID field. This is different than your record name or record ID field.

<figure><img src="https://canny.io/images/856679e6ca929a69644560abe64b8ceb.png" alt=""><figcaption></figcaption></figure>

This will serve as a unique identifier for the record when exporting or importing data, using a [Make.com](http://make.com/) or [Zapier](https://zapier.com/) automation to connect data to third party softwares.&#x20;

For example, when identifying a record in Hubspot to update in Stacker use the External IDs from Hubspot to update the corresponding record. This can also be used for linking records, if you had activities in Hubspot related to your contact, then you can load the Activity into Stacker and use the Hubspot Contact ID to link the records.


---

# 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.stackerhq.com/stacker-astra/data-management/import-data-to-stacker-tables/stacker-tables-import-a-csv/external-ids.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.