> For the complete documentation index, see [llms.txt](https://doc.wearepatchworks.com/product-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.wearepatchworks.com/product-documentation/developer-hub/connector-builder/building-your-own-connector/3-authentication-methods/authentication-method-options/connector-variables.md).

# Connector variables

## Introduction

The **connector variables** tab displays any i[nstance-level, shared variables](/product-documentation/developer-hub/connector-builder/building-your-own-connector/2-connector-variables.md) that you defined in [Step 2: connector variables](/product-documentation/developer-hub/connector-builder/building-your-own-connector/2-connector-variables.md) - for example:

<div align="left"><figure><img src="/files/iGM2gUKx3r70KBlcPUO2" alt=""><figcaption></figcaption></figure></div>

## Using a connector variable in your authentication method

If you want to use any of these variables in this authentication method, click the **use** button:

<div align="left"><figure><img src="/files/WqeILR94LN60JKBIkjKm" alt=""><figcaption></figcaption></figure></div>

This copies the variable into the **auth variables** tab - for example:

<div align="left"><figure><img src="/files/dLYfCzPJbuaUVje9QjL0" alt=""><figcaption></figcaption></figure></div>

<details>

<summary><img src="/files/JOYoP4EdSu7WJ3CMdAAS" alt="" data-size="line"> Show me</summary>

![](/files/K4UUTsG4HFFo6C0EEMkt)

</details>

From here, the variable is treated like any other [auth variable](/product-documentation/developer-hub/connector-builder/building-your-own-connector/3-authentication-methods/authentication-method-options/auth-variables.md) - you will need to set options to determine if/how this variable is displayed to users, and how any values for it should be passed in  API requests for authentication.

## Removing a connector variable from auth variables

If you choose to **use** a connector variable- i.e. to copy it to the **auth variables** tab - but later change your mind - you can remove it by clicking the associated **trash icon** on the **auth variables** tab - for example:

<div align="left"><figure><img src="/files/wAf4Ymt7RamPgGRrlkHV" alt=""><figcaption></figcaption></figure></div>

This clears the connector variable from the **auth variables** tab but the original 'shared' connector variable remains available for future use.


---

# 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://doc.wearepatchworks.com/product-documentation/developer-hub/connector-builder/building-your-own-connector/3-authentication-methods/authentication-method-options/connector-variables.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.