# Field Types  to Documint Variables

## Fields Types

{% hint style="danger" %}
Field names in Airtable are converted to snake-case in Documint. This means your variables need to be the snake-case version of the field name.  For example,  if a field in Airtable is named `Order Total`, its variable name in Documint needs to be`order_total` . Notice the space is replaced with an underscore and everything is converted to lowercase.
{% endhint %}

Airtable fields names must be converted to snake-case when being used in your template. The basic rules of snake-case are:

1. spaces are converted to underscores
2. double underscores are converted to single underscores
3. underscores at the beginning or end of the string are removed
4. some special characters are replaced with underscores
5. all upper-case characters are converted to lower-case

The easiest way to convert your field names to snake-case is by pasting the field name into the New Variable tool in the template designer.

### Mapping Data from Airtable App

Once you have setup the Airtable App and chosen the template you will be using, the table's fields will be available to copy and paste into your template.

![](https://1903534506-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTY5wPd81K7B5rjyG5tjS%2Fuploads%2FfjWhUt52huijENqzFN3V%2Fapp%20variables.png?alt=media\&token=26b783e2-d868-4df7-b7c7-3cdcd706b6f8)

1. Click on the field names to copy the field's token to your clipboard.
2. Paste it into your Documint template.
3. Generate a document (make sure the correct template is selected).

##


---

# 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.documint.me/integrations/airtable/legacy-airtable-integration/field-types-to-documint-variables.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.