> For the complete documentation index, see [llms.txt](https://help.getglinks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.getglinks.com/introduction/variable-go-links.md).

# Variable go links

Variable go links in Glinks allow you to create dynamic links by specifying a wildcard (denoted by `{*}`). This lets users replace the wildcard with custom values, making the links more flexible and tailored to specific needs.

**Example: Zendesk Tickets**

<figure><img src="/files/Kb38mBZIwnLvz0DpQ1V9" alt=""><figcaption></figcaption></figure>

Zendesk is a popular custom support software. Each customer support request gets logged as a ticket. You can create a variable go link for accessing Zendesk tickets:

* **Go Link**: `go/t`
* **Destination URL**: `https://dictanotehelp.zendesk.com/agent/tickets/{*}`

Now, when you want to access a specific ticket, simply append the ticket ID to the go link. For example:

* `go/t/1234` opens `https://dictanotehelp.zendesk.com/agent/tickets/1234`

This setup allows quick access to any ticket by just changing the variable part of the URL. Some more examples:

**Example: JIRA Tickets**

Variable go links are also useful for JIRA ticket tracking. For example:

* **Go Link**: `go/jira`
* **Destination URL**: `https://mycompany.atlassian.net/browse/{*}`

To open a JIRA ticket for a specific issue:

* `go/jira/PROJ-567` opens `https://mycompany.atlassian.net/browse/PROJ-567`

This method saves time and ensures consistency when navigating project issues.

**Example: GitHub Issues**

You can also create variable go links for tracking GitHub issues:

* **Go Link**: `go/gh`
* **Destination URL**: `https://github.com/myrepo/myproject/issues/{*}`

When you need to access a specific issue:

* `go/gh/987` opens `https://github.com/myrepo/myproject/issues/987`


---

# 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://help.getglinks.com/introduction/variable-go-links.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.