# Variable Fields

You may wish to personalise your emails with variable fields whose content will change depending on recipient information. Postman allows you to do this by the following steps:

1. Use double curly brackets **{{ }}** in the message template to indicate a variable field (see the screenshot below for an example). The field will be populated with the recipient's unique test result as reflected in your CSV file (see step 2).

![](https://lh5.googleusercontent.com/Z--1ojvTKY98Cko2gmyaVtgKjiSiLoJz-9tng6PnYkr7YXO-kwS2ZQ-59hCQaY5jfILe_91Z96lOh6m9g3xevYgePbxVFMXrqAJaIblXHDFrHalM8FQeg0KlvuqsjWV0BFzVNadb7lXoP29Cdcly5Yy9zA)

2\. In the same CSV file that you upload with recipient information (in step 3 of the campaign creation flow), include the corresponding variable field names and the accompanying information for each unique recipient.

* text in the variable content fields should *not* have spacings - instead, replace spacings with underscores e.g. instead of "test result", the variable field in the message template *and* your CSV file should reflect "test\_result".
* by convention, all text content in variable fields must be in *small letters.*

![](/files/dMtRZn6MzqybkAutdDnj)


---

# 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://postman-v1.guides.gov.sg/campaign-guide-email/email/variable-fields.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.
