> For the complete documentation index, see [llms.txt](https://docs.pascom.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pascom.net/en/integrations/connector/variables-assignment.md).

# Variables Assignment

Learn how to assign source variables in the Connector.

## Modify Variable Assignment

In the Connector profile you can adjust the assignment of the source variables to your needs in the tab **Variables**. The naming for the used variables must be the same for the column **Source**, of course with the name from the **Source**. This way the connector knows where to import external data.

As an example, let's say we want to save the users Job title within the PASCOM phone book notes field. Under the **Variables** tab, enter the following line by pressing **Add**:

| Variable | Source                |
| -------- | --------------------- |
| job      | `return $row['job'];` |

By **double clicking** on the variable, you can edit it as shown below.

![Neue Variable](https://2713225-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVIw0BpSv358R2Pr2HflD%2Fuploads%2Fgit-blob-e9b50fe3449498af6ba9bdf97641e02aaa6169ea%2Fnew_variable.en.png?alt=media)

Through this line the connector stores the content of the source data field "job" in the variable of the same name "job". This variable must now be assigned to the note PASCOM phonebook field under the **structure** tab.

How the assignment of variables in the **connector-structure** works, we explain [here](/en/integrations/connector/variables-structure.md).


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.pascom.net/en/integrations/connector/variables-assignment.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 `build a script that syncs our docs to a CMS` 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.