# Connection metadata

We recommend you use the `metadata` parameter to store the account's name or email. This allows users to easily distinguish their stored connections.

Always save the metadata in the connection if:

* the endpoint that can obtain the authenticated user’s information is available, and
* the information provided is able to distinguish the connection.

Saving the metadata allows for better identification on the Connections page.

We suggest saving the following information:

* Name
* Email
* User ID
* Organization, Company, Location, etc.

{% hint style="info" %}
When a string is stored as `metadata`, Make sets a limit of 512 characters.
{% endhint %}

{% tabs %}
{% tab title="Occurrence" %}

<div align="left"><figure><img src="/files/S0os1vTZ4R10zNJFykUC" alt="" width="470"><figcaption></figcaption></figure></div>

{% hint style="info" %}
The value in the brackets after the user's connection name is taken from the `metadata` parameter.
{% endhint %}
{% endtab %}

{% tab title="Source" %}

```javascript
...
"response": {
    "metadata": {
            "type": "email", //allowed values are "email" and "text"
            "value": "{{body.data.user.email}}"
        }
},
...
```

{% endtab %}
{% endtabs %}


---

# 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://developers.make.com/custom-apps-documentation/best-practices/connections/connection-metadata.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.