# Using Custom Object Tokens

## Understanding the Custom Object Token

For this demonstration, a custom object of **Products**, responsible for storing products or orders related to a lead, was created. This object includes the fields: **Description**, **First name**, **Unit Value** and **Order ID**.

A lead custom object token is formed by a pair of braces, starting with `customobj=` followed by the **ID of the custom object** you want to refer to. Then, use `->` to point to the **alias of the desired field** within that object. 

**Example:** `{customobj=6->descricao}`

<figure><img src="/files/cc29c827f7eb1dee28a8e592469ce00a2cbc5abe" alt=""><figcaption><p><em>Custom object Products.</em></p></figcaption></figure>

{% 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 registered one will be considered.
{% endhint %}

## Creating a Meta Template

For this token use case, a **WhatsApp API Utility Template**.\
In the body of the template, you can insert several dynamic tokens, such as the lead's name and any values stored in custom objects.

At send time, these tokens are automatically replaced with the corresponding data saved on the Lead.

<figure><img src="/files/42ef2a0440175c9d756fd34375fa4f1f0d850c1f" alt=""><figcaption><p><em>Template creation.</em></p></figcaption></figure>

## Testing the Template Send

Below you can see two screenshots: the first shows how the message appears in the conversation, with the tokens already replaced by real values. The second displays all custom product objects linked to the lead, highlighting the most recent one — which is used when sending the message.

<figure><img src="/files/3a414ee2461c8d4be87972051ba6fc8709cbf9b9" alt=""><figcaption><p><em>Conversation with template send.</em></p></figcaption></figure>

<figure><img src="/files/9a32b8ca5555a0b6baec9a4cc932875bdeeb97dc" alt=""><figcaption><p><em>Custom Product objects.</em></p></figcaption></figure>


---

# 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://docs.sprinthub.com/en/strategies/tokens/using-custom-object-tokens.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.