> For the complete documentation index, see [llms.txt](https://docs.getint.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.getint.io/getting-started-with-the-platform/about-getint-concepts/what-is-a-connection.md).
# What is a Connection?
### What is a Connection?
In the context of Getint, a "Connection" is a crucial element that forms the basis of our integration process. It refers to the established link between Getint and a specific collaboration software tool, such as Jira, Azure DevOps, ServiceNow, Asana, among others. Here's a detailed breakdown of what a Connection entails and how it's set up:
#### Authentication and Accessibility:
* A Connection is successfully established when Getint is authenticated and can access a given collaboration software tool.
* This authentication is the bridge that enables seamless communication and data exchange between Getint and the external tool.
#### Establishing a Connection:
* To create this link, you need the instance URL of the tool you want to connect with. The instance URL is the web address where the application is hosted or can be accessed.
* Additionally, a service account user is required. This involves the email/login associated with the account and either a password or a token for authentication.
* The service account should ideally have the necessary permissions to perform the intended actions within the tool (like creating, updating, and managing tasks or issues).
#### Functioning as the Service Account User:
* Once connected successfully, Getint operates as this service account user.
* All actions performed by Getint, such as creating or updating tasks and issues, will be executed under this user's identity.
* This approach ensures that all changes and activities carried out by Getint are properly logged and traceable within the collaboration tool.
In summary, a Connection in Getint is the authenticated and functional link between Getint and an external collaboration tool, enabled through specific access credentials. This connection is fundamental to the integration process, allowing Getint to perform a range of actions as an authorized user of the external tool.
---
# 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://docs.getint.io/getting-started-with-the-platform/about-getint-concepts/what-is-a-connection.md?ask=&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.
