> 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/strategies/tokens/using-custom-object-tokens.md).
# Using Custom Object Tokens
How to add custom object tokens to WhatsApp API templates.
## Understanding the Custom Object Token
For this demonstration, a custom object was created for **Products**, responsible for storing the products or orders related to a lead. This object includes the fields: **Description**, **First name**, **Unit Value** and **Order ID**.
A lead custom object token is made up of a pair of braces, starting with `customobj=` followed by the **custom object ID** to which you want to refer. Then, use `->` to point to the **desired field alias** within that object.
**Example:** `{customobj=6->description}`
Products custom object.
{% hint style="info" %}
The values used by the tokens always correspond to the most recently saved custom object. In other words, if there are multiple objects, the last recorded one will be considered.
{% endhint %}
## Creating a Meta Template
For this token use case, a **WhatsApp API Utility Template**.\
In the template body, it is possible to insert various dynamic tokens, such as the lead's name and any values stored in custom objects.
At the time of sending, these tokens are automatically replaced with the corresponding data saved in the Lead.
Template creation.
## Testing Template Sending
Below, you can see two screenshots: the first shows how the message appears in the conversation, already with the tokens replaced by the real values. The second displays all custom product objects linked to the lead, highlighting the most recent one — which is the one used when sending the message.
Conversation with template sending.
Product custom objects.
---
# 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/strategies/tokens/using-custom-object-tokens.md?ask=&goal=
```
`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.
