> For the complete documentation index, see [llms.txt](https://postman-v1.guides.gov.sg/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://postman-v1.guides.gov.sg/campaign-guide-email/email/variable-fields.md).

# 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.*

![](https://4126954886-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MAQH3DF49Lq0AJudrbF%2Fuploads%2Fgit-blob-76ddca93f792dbd790cc06faa2630ec82d8e6641%2FScreenshot%202022-08-22%20at%202.46.21%20PM.png?alt=media)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://postman-v1.guides.gov.sg/campaign-guide-email/email/variable-fields.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
