How to use custom token names in Airtable

If you’d like to use a token name in your template that is different from the field name in Airtable, or you get a transliteration error, this article is for you.

We’ve updated our Airtable extension to support non-Unicode characters. Field names are now automatically converted to Latin for use as tokens.

While most languages are supported, some may not transliterate correctly. If a field name can’t be transliterated, you’ll see an icon next to the token:

Plumsail Documents could not create a token based on your field name.

To resolve this, add a #DocumentToken=TOKEN_NAME parameter to the field description to use a custom token name in the template. For example:

#DocumentToken=Type results in {{Type}} token name instead of {{유형}}

This syntax assigns the {{Type}} token to the field, allowing you to access the data in the 유형 field using {{Type}} in the template. ‘Type’ is just an example—use any token name you like.

The {{Type}} token now pulls data from the 유형 field