> For the complete documentation index, see [llms.txt](https://docs.sprinthub.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sprinthub.com/en/topics/general/contacts/leads-common-questions/contacts-token-tester.md).

# Contacts - Token Tester

The **Token Tester** is a tool available within **Contact** that allows you to validate how variables (conversion tokens) work before using them in messages, emails, documents, and automations.

The tool replaces the tokens with the actual values registered in the system, allowing you to check exactly how the content will be presented to the recipient.

{% embed url="<https://youtu.be/mjbbS2jtqds>" %}

***

### Accessing the Token Tester

To use the tool:

1. Access the record of a **Contact**.
2. Open the option **Token Tester**.
3. Select the entity you want to use as a reference for the test.
4. Enter the text containing the conversion tokens.
5. Click on **Test**.

The system will display the result with all variables replaced by their respective values.

### Available entities

In addition to the information of the **Contact**, it is possible to link the test to the following entities:

* Contact
* Invoice
* Proposal
* Recurring
* Installment Plan
* Tax Invoice
* Opportunity

When selecting one of these entities, the corresponding tokens will be filled with information from the record linked to the contact.

***

### Example

#### Entered text

```
Hello {contactfield=firstname}!

Your proposal no. {proposal=id} was approved.

The invoice amount is R$ 1,250.00.

Thank you for your contact!
```

#### Result

```
Hello João Silva!

Your proposal no. 10235 was approved.

The invoice amount is R$ 1,250.00.

Thank you for your contact!
```

***

### When to use

The Token Tester is recommended for validating content before using it in:

* WhatsApp messages;
* Emails;
* Documents;
* Automation flows;
* Campaigns;
* Automatic notifications.

In this way, it is possible to identify possible inconsistencies before the communication is sent to the customer.

***

### Best practices

* Check whether the tokens used belong to the selected entity.
* Confirm that the contact has linked records (such as Proposals, Invoices, or Opportunities), so that the values can be returned correctly.
* If any variable remains blank, check whether the information is registered in the corresponding record.
* Always run a test before publishing messages, templates, or automations.

***

### Conclusion

The **Token Tester** makes it easier to validate conversion variables, allowing you to preview the final result before sending communications. With support for the entities **Contact, Invoice, Proposal, Recurring, Installment Plan, Tax Invoice** and **Opportunity**, the tool helps create more accurate, personalized, and error-free messages.


---

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.sprinthub.com/en/topics/general/contacts/leads-common-questions/contacts-token-tester.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.