> For the complete documentation index, see [llms.txt](https://university.gonexa.fr/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://university.gonexa.fr/doc/en/advanced-features/tag-extensions/clickable-url-in-text.md).

# Insert a clickable URL in text

Turn text into a clickable link in Word

{% hint style="danger" %}
**Warning**

Using these extensions requires a package version later than 2.3.\
If needed, update the package through the AppExchange or your App account.
{% endhint %}

In Word, you can associate a hyperlink with specific text by using a tag extension.

**How does it work?**

The `{!label|champ(link,Texte_affiché,Message_erreur)}` syntax turns a URL stored in a field into a **clickable hyperlink** in the Word document.

**3 parameters:**

* `link`: fixed keyword, always the same
* `Texte_affiché`: what the user sees (e.g. "Click here")
* `Message_erreur`: text displayed if the URL is invalid or empty

1. Build your tag with the assistant and add the extension as described above
2. Insert it into your Word document where you want it
3. Save, upload and test as usual

{% hint style="success" %}
**Example**

To insert a clickable link based on a text field containing a URL, displaying the text **"Cliquez ici"** ("Click here") with the error message **"Une erreur est survenue"** ("An error occurred"), the complete tag is:

```
{!Account|Champtexte__c(link,Cliquez ici,Une erreur est survenue)}
```

{% endhint %}

{% hint style="danger" %}
**Warning**

Make sure the URL in the field is valid to avoid displaying the error message
{% endhint %}


---

# 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://university.gonexa.fr/doc/en/advanced-features/tag-extensions/clickable-url-in-text.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.