> ## Documentation Index
> Fetch the complete documentation index at: https://developers.redo.com/llms.txt
> Use this file to discover all available pages before exploring further.

# EmailTemplateVariable

> One template variable for subject, preview text, and authored strings. Use `{{ name }}`.

<ResponseField name="dataType" type="String!" required>
  Schema data type, including Maybe/Multiple prefixes, e.g. `Maybe Text`.
</ResponseField>

<ResponseField name="description" type="String!" required>
  What the value holds at send time.
</ResponseField>

<ResponseField name="displayName" type="String!" required>
  Merchant-facing label.
</ResponseField>

<ResponseField name="insertable" type="Boolean!" required>
  True when the email/SMS insert-variable picker would show this name. Hidden and structured fields still resolve if authored.
</ResponseField>

<ResponseField name="integrationGated" type="Boolean!" required>
  True when send-time resolution depends on a connected integration. The name is still listed; a missing integration yields an empty value.
</ResponseField>

<ResponseField name="key" type="String!" required>
  CamelCase schema key this name came from, e.g. `customerFirstName`.
</ResponseField>

<ResponseField name="name" type="String!" required>
  Snake\_case identifier, e.g. `customer_first_name`. Write `{{ name }}`.
</ResponseField>

<ResponseField name="source" type={<a href="/docs/api-reference/v3/reference/marketing/email-template-variable-source">EmailTemplateVariableSource!</a>} required>
  Whether this name comes from the trigger, renderer, or store.
</ResponseField>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.