> 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/guides/quickstart.md).

# Quickstart

## Introduction <a href="#introduction" id="introduction"></a>

Welcome to Getint, where simplicity meets power! Our goal is to make your first integration not just possible but enjoyable in minutes, whether you're handling straightforward tasks or diving into complex cases. Forget the hassle of installing multiple apps or choosing between an intuitive UI and complex scripting. Getint combines the best of both worlds: a single, user-friendly UI for all your integration needs, with the power of scripting at your fingertips for those unique challenges. To start your free trial, follow the instructions provided in the [Getint documentation](https://docs.getint.io/getting-started-with-the-platform/starting-the-free-trial-and-accessing-the-getint-app).

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

Feel free to explore the platform and experience the benefits of Getint!

#### Why Choose Getint? <a href="#why-choose-getint" id="why-choose-getint"></a>

* **One UI to Rule Them All**: Manage all your connectors from a single interface. No separate installations, no toggling between modes.
* **Flexibility and Power**: Start with the basics, then effortlessly scale to more advanced features like custom fields, sync directions, filtering, and handling comments, all tailored to your needs.
* **Simplified Setup**: From your very first task integration to syncing attachments and status mapping, see immediate results and scale your setup as needed.
* **Quick Build and Quick Match**: Quickly map work items and multiselect field values with a simple click. Build a working integration with minor steps and jump straight to synchronization.
* **Team of experts**: If you get stuck or don’t know how to finish your integration build, we can back you up and guide you through the process, ensuring you have all the support needed to complete your integration scope.

Before diving in, prepare for your integration journey by reviewing our [preparation guide](https://docs.getint.io/getting-started-with-the-platform/prepare-for-integration) and claiming your free trial instance, available via the Atlassian Marketplace or directly through Getint SaaS or Getint OnPremise options.

***

### Setting Up Your First Integration <a href="#setting-up-your-first-integration" id="setting-up-your-first-integration"></a>

#### 1. Access the Welcome Page: <a href="#id-1.-access-the-welcome-page" id="id-1.-access-the-welcome-page"></a>

On the welcome page, you will be prompted to create a new integration. Click **Create Integration**.

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

* Select your desired integration: **Continuous Sync**, **Migration**, or **Sync GIT Repository**. You can learn about integration vs. migration [here](https://docs.getint.io/getting-started-with-the-platform/about-getint-concepts/migration-vs-integration), and learn about syncing GIT repositories [here](https://docs.getint.io/guides/integration-synchronization/git-integrations).

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

#### 2. Connect Your First Application: <a href="#id-2.-connect-your-first-application" id="id-2.-connect-your-first-application"></a>

* Select a side to connect your first app (the direction will be important later on, when defining the synchronization flow), and click **Connect App**.

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

* Choose the app you would like to integrate, and click it. Make sure to select the apps that match the installed Getint app (e.g.**,** Select Jira or Azure DevOps for the Getint Jira - Azure Integration app).

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

* In the next screen, create the connection to the intended workspace by pasting the workspace URL in the field and clicking **Next** (In this example, we are using Azure DevOps).

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

* Add the username and API token of the integration service account. Feel free to name the connection for distinction and click **Add**.

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

* In the next screen, click the drop-down to locate your newly created connection and select it.

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

* In the next screen, click the dropdown to select your workspace project, and click Connect to complete the connection.

You can tick the **Sync many projects** checkbox if you are looking to build a many-to-many integration (You can learn more about many-to-many integration [here](https://docs.getint.io/getintio-platform/syncing-many-to-many-projects)).

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

* **Repeat for the Second Application (Example, Jira)**: Follow the steps above to establish a connection with your second application.

### 3. Map Work Item Types <a href="#id-3.-map-work-item-types" id="id-3.-map-work-item-types"></a>

* Select the **Quick Build** for an easier and faster setup.

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

* In the pop-up screen, click **Build** for Getint to automatically map similar work item types and create field mappings

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

* After it loads the work item type mappings, adjust the build as needed. Remove unwanted fields or add missing field mappings, and click **Apply** once the build is up to your needs.

<figure><img src="/files/6YbLFjey373AswoMXoyU" alt=""><figcaption></figcaption></figure>

* Provide a name to your integration in the upper left corner field, and click create once you are satisfied with your build.

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

* Congratulations, your integration is now live and ready to synchronize data!

**Test Your Integration**: Create a task in Jira with a title and description. It should appear in Azure DevOps (or an app of your choice) shortly.

### 4. Adjust Your Integration as Needed <a href="#id-4.-adjust-your-integration-as-needed" id="id-4.-adjust-your-integration-as-needed"></a>

* Within your integration editor scree&#x6E;**,** you can choose to add new type mappings or edit existing ones. You can click **Add type mapping** to map new type mappings one-to-one, or you can edit pre-existing type mappings by clicking on them or clicking the **three dots** on their right-hand side.

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

* When editing your type mappings, you can either add field mappings manually or use the Match Fields function to quickly map similar fields from both sides.

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

* When manually mapping fields, select the app and the respective field you would like to map to the other side. Then, select the field from the counterpart software, and both fields will be mapped to each other.

{% embed url="<https://www.loom.com/share/de68403be27b4bbe9649eace1e38b60a>" %}

* **Status Mapping**: Customize your status mappings to fit your workflow.

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

* Map any remaining options through the highlighted dropdowns.

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

* **Comments and Attachments**: Configure your comments syncing setup.&#x20;

<figure><img src="/files/8MbpKzjWZIgJEdVLQ8ps" alt=""><figcaption></figcaption></figure>

* Enable attachment sync at the bottom of the screen. Make sure to apply your settings.

<figure><img src="/files/9Pk9rj3s4lOYjZjCBHVp" alt=""><figcaption></figcaption></figure>

* Save Your Progress: Don’t forget to save your integration changes.

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

* **Testing the integration**: Test your adjusted integration and monitor results\
  Create a new task (or mapped work item) on both sides, fill in some of the mapped fields with data, and observe how information synchronizes across.

### 5. Monitor Results <a href="#id-5.-monitor-results" id="id-5.-monitor-results"></a>

* Upon opening the reporting section, you'll be presented with a comprehensive table listing all **Performed Syncs** along with their respective statuses. This provides a quick snapshot of your integration activity.

<figure><img src="/files/9IRy9oeAIwhkkoahKeE9" alt=""><figcaption></figcaption></figure>

* **Detailed Sync Analysis**:
* **Sync ID**: For a deeper dive into a specific sync, click on its **ID** (e.g., #1484). This action opens a detailed view of the sync, offering insights into its execution.
* **Trigger Source**: By selecting **Triggered by** (e.g., 6807), you can review the task that initiated the sync. A clickable URL facilitates direct access to the triggering task, enabling easy review and analysis.
* **Sync Outcome**: Clicking on **Synced with** (e.g., JIR-54) reveals the task resulting from the sync, complete with a direct URL for quick access. This feature allows you to evaluate the sync's effectiveness and outcome clarity.

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

* **Troubleshoot**: The **Mode** section is your go-to for assessing the sync's success. A successful sync indicates everything is functioning as expected. Conversely, should you encounter any issues, this section will guide you to identify errors. Should an error be detected, revisit step 1 for troubleshooting. To facilitate resolution, copy the error details and submit a support ticket for assistance.

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

### Conclusion <a href="#conclusion" id="conclusion"></a>

By following these steps, you have established a functional integration between your workspace&#x73;**.** This setup automates the synchronization of records, workflows, and communication, bridging the gap between teams across different software.

Encounter a snag? Reach out at any stage of your integration journey. Click the chat icon, schedule a [free onboarding demo call](https://www.getint.io/schedule-a-demo#book-a-demo), or [open a support ticket.](https://getintio.atlassian.net/servicedesk/) We're here to ensure your integration success with Getint.

<figure><img src="/files/otyodSR2k1YTwh3mrnVq" alt=""><figcaption><p><a href="https://calendly.com/d/cpws-jb2-8xx/demo-call-all-team
">Start your integration journey. Schedule a free consultation with our Getint Integration Expert today!</a></p></figcaption></figure>


---

# 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:

```
GET https://docs.getint.io/guides/quickstart.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.