> 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/integration-synchronization/non-jira-connectors.md).

# Non-Jira Connectors

## Building a Non-Jira Integration <a href="#building-a-non-jira-integration" id="building-a-non-jira-integration"></a>

Getint supports 17 connectors, which means there are many possible combinations you can build between them. This guide covers all of those pairings in one place. The steps you follow are the same no matter which two tools you connect, so whether you are syncing Asana with ServiceNow, Freshdesk with Freshservice, or any other combination on the platform, you can use this page as your starting point.

To keep the guide general, **App A** and **App B** stand in for the two tools you want to connect. Wherever you see them, replace them with your own applications. For example, if you are syncing Asana with ServiceNow, read **App A** as Asana and **App B** as ServiceNow.

{% hint style="info" %}
This guide applies to every non-Jira connector, so it does not include screenshots of a single tool. Each step names the exact button or menu to look for in **bold**. For details specific to your connector, the linked pages in each section cover the individual tools.
{% endhint %}

### The Full Process <a href="#the-full-process" id="the-full-process"></a>

Before you start, here are all the steps from beginning to end. Every non-Jira integration follows this same order:

1. Sign in to the Getint app.
2. Create a new integration.
3. Connect **App A**.
4. Connect **App B**.
5. Map your item types between the two tools.
6. Set up item routing (only if you selected multiple projects).
7. Map your fields.
8. Map assignees and statuses.
9. Configure comments and attachments.
10. Apply filters (optional).
11. Test the integration.

Each step below explains one point in this list, in order.

### Before You Begin <a href="#before-you-begin" id="before-you-begin"></a>

The Getint licensing model for non-Jira connectors focuses on predictable costs and scalability:

#### Standard Licensing <a href="#standard-licensing" id="standard-licensing"></a>

* This tier covers a direct integration between one **App A** instance and one **App B** instance for a fixed fee. It includes unlimited project and work item synchronization without hidden charges.

You can find more information about our pricing structure here: [Getint Pricing](https://www.getint.io/pricing).

#### Network License <a href="#network-license" id="network-license"></a>

* Designed for managed service providers or large organizations, this option supports three or more instances. It allows for a specific number of connections and provides the flexibility to swap integrated tools while the license is active.

For more details on licensing, visit our [Licensing Page](https://docs.getint.io/billing-and-services/licensing).

#### Requirements to Build Your Integration <a href="#requirements-to-build-your-integration" id="requirements-to-build-your-integration"></a>

* **Deployment Options**: Getint provides two ways to host your integration: a managed [SaaS platform](https://app.live.getint.io/) or a self-hosted On-premise version. More information about Getint On-premise [here](https://docs.getint.io/getting-started-with-the-platform/deployment-options/on-premise-deployment).
* **Authentication**: Each tool requires its own credentials to establish a secure connection. You can find the steps to generate the credentials for every connector here: [Connection Guide](https://docs.getint.io/guides/quickstart/connection).
* **Service Accounts**: Because the integration attributes comments to the user who created the connection, we recommend using dedicated Service Accounts for both instances to keep a clear distinction between automated updates and individual user activity.

### Setting Up Your Non-Jira Integration <a href="#setting-up-your-non-jira-integration" id="setting-up-your-non-jira-integration"></a>

#### 1. Access the Getint App <a href="#id-1.-access-the-getint-app" id="id-1.-access-the-getint-app"></a>

* Log in at [app.live.getint.io](http://app.live.getint.io/). If you do not have an account, click **Sign up** to create one.
* Enter your details, select the apps you want to connect, and click **Create new workspace**.
* After you create the workspace, go to it to launch Getint. The Getint interface will load.

#### 2. Create an Integration <a href="#id-2.-create-an-integration" id="id-2.-create-an-integration"></a>

* Go to **Workflows** (the lightning bolt icon) and click **Create Integration**.
* From this menu, select **Continuous Sync**.

{% hint style="info" %}
**Continuous Sync** keeps both tools updated in real time as items change. If you need a one-time transfer of existing items instead, choose **Data Migration**. This guide covers Continuous Sync.
{% endhint %}

#### 3. Connect to App A <a href="#id-3.-connect-to-app-a" id="id-3.-connect-to-app-a"></a>

* Click **Connect App** and choose your first tool.
* Enter the credentials for **App A**. The exact fields depend on the tool, so follow the [Connection Guide](https://docs.getint.io/guides/quickstart/connection) for the specific values your connector needs.
* Select the project or space you want to integrate.
* Click **Connect** to establish the connection.

{% hint style="info" %}
Every connector has its own authentication method, such as a Personal Access Token, an API key, or a username and password. The [Connection Guide](https://docs.getint.io/guides/quickstart/connection) lists the exact steps for each supported tool.
{% endhint %}

#### 4. Connect to App B <a href="#id-4.-connect-to-app-b" id="id-4.-connect-to-app-b"></a>

* Click **Connect App** again and choose your second tool.
* Enter the credentials for **App B**, then click **Add** to create the connection.
* Once added, the connection becomes available for selection.

#### 5. Configure Type Mapping <a href="#id-5.-configure-type-mapping" id="id-5.-configure-type-mapping"></a>

Type mapping tells Getint which item type in **App A** matches which item type in **App B**, such as a task matching a ticket or a story matching an incident.

* **Quick Build**: Automatically align fields and data types between both applications using this feature. This is the fastest way to start and works well for most pairings.
* **Manual Mapping**: If you want full control, select **+ Add Type Mapping** to define how your types map between systems.

For more details, see [Type Mapping](https://docs.getint.io/getintio-platform/workflows/type-mapping).

{% hint style="info" %}
Choose **Quick Build** if you want Getint to set sensible defaults for you. Choose **Manual Mapping** if your tools use custom types or you need a specific pairing. You can adjust the mapping later, either way.
{% endhint %}

#### 6. Item Routing <a href="#id-6.-item-routing" id="id-6.-item-routing"></a>

If you selected multiple projects for either connection, you must define Item Routing so incoming items land in the correct project. All relevant information about defining conditions is here: [Syncing Many Projects](https://docs.getint.io/getintio-platform/syncing-many-to-many-projects#defining-conditions-in-items-routing).

{% hint style="warning" %}
If you connected a single project on each side, you can skip this step. Before you set up a many-to-many integration, confirm that both connectors you selected support syncing multiple projects, since not every tool offers this option.
{% endhint %}

#### 7. Field Mapping <a href="#id-7.-field-mapping" id="id-7.-field-mapping"></a>

* Review or manually map fields within your mapped types, such as **title**, **description**, and **assignees**.
* Make sure the synchronization flow is defined for each field, using the arrows, and select **Apply**.

For more details, see [Field Mapping](https://docs.getint.io/getintio-platform/workflows/field-mapping).

{% hint style="info" %}
The arrows control direction. A two-way arrow keeps a field in sync both ways, while a one-way arrow sends updates in a single direction only.
{% endhint %}

#### 8. Assignee Mapping <a href="#id-8.-assignee-mapping" id="id-8.-assignee-mapping"></a>

Use the **Assignee mapping** option to match assignees in **App A** with their corresponding assignees in **App B**. This step ensures that when an item syncs between the two systems, it is automatically assigned to the right person in each tool.

This mapping is especially important when usernames or email formats differ between platforms. By defining these relationships once, you prevent mismatches and avoid manual reassignment later.

For more details, visit our doc: [Assignees (users) mapping](https://docs.getint.io/getintio-platform/workflows/assignees-users-mapping).

#### 9. Status Mapping <a href="#id-9.-status-mapping" id="id-9.-status-mapping"></a>

Use the **Status mapping** option to align workflow states between **App A** and **App B**. Each platform uses its own terminology for progress, so mapping keeps updates consistent when items sync in either direction.

Status mapping lets you pair equivalent states across both systems. For example, you might map:

* **To Do** in App A to **New** in App B
* **In Progress** in App A to **Review** in App B
* **Completed** in App A to **Closed** in App B

Once these relationships are defined, any status change in one system is translated into the correct status in the other.

* You can also configure the status direction to support one-way transitions instead of two-way updates.

#### 10. How to Manage Comments and Attachments <a href="#id-10.-how-to-manage-comments-and-attachments" id="id-10.-how-to-manage-comments-and-attachments"></a>

Check the **Comments & Attachments** tab. These settings are active by default, but you can modify them to fit your specific requirements.

**Synchronization Directions**

The platform supports three logic flows for these items:

* **Bidirectional**: Updates to comments or attachments in either **App A** or **App B** will reflect in the other platform.
* **Unidirectional to App A**: Data flows exclusively from **App B** to **App A**. Changes made in **App A** will not sync back.
* **Unidirectional to App B**: Data flows exclusively from **App A** to **App B**. Changes made in **App B** will not sync back.

**Disabling Sync**

If your organization has strict data privacy policies, or if these items are not relevant to a specific integration, you can **disable** comments and attachments entirely. This prevents any data transfer for these fields while keeping other mapped fields active.

To sync files between both systems, turn on the **Synchronize attachments** option. Once enabled, you can also choose the **sync direction** for attachments.

{% hint style="warning" %}
**Inline images** are not supported for the **Description** field.
{% endhint %}

#### 11. Advanced Tab <a href="#id-11.-advanced-tab" id="id-11.-advanced-tab"></a>

* Enable **Customize create/update actions** to manage item synchronization. This allows for specific rules, such as one-way creation for the left application combined with two-way updates.

#### 12. Filtering <a href="#id-12.-filtering" id="id-12.-filtering"></a>

You can filter the synchronization to customize it for your needs and requirements. Please see the doc [Items Filtering](https://docs.getint.io/getintio-platform/workflows/items-filtering) for more details.

**UI Filtering Option**

* Click the filtering icon near the app icon in your integration. This applies to that side of the integration.
* Select whether the filtering applies to *All*, *New*, or *Synced* items.
* Note that if **New items** is selected, the filtering applies only to new items, and the already synced items will continue to sync and update. If **Synced items** is selected, only the already synced items will be updated based on that filter.
* Choose the options and add the value for the filter. You can filter more than one option for each field.
* Select **Apply** after creating the filters, and **Save** the integration.

#### 13. Test the Integration <a href="#id-13.-test-the-integration" id="id-13.-test-the-integration"></a>

* Create test items in **App A** or **App B** and observe how they synchronize.
* Confirm that the data between the two platforms is correctly synced.
* Monitor the integration status and the logs in Getint to verify that everything functions as expected.

***

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

Following this guide lets you set up an integration between any two non-Jira tools with Getint. This configuration supports data synchronization of items, fields, and workflows across your platforms, allowing teams to collaborate while keeping both tools aligned.

For further assistance, please contact us at the [Support Center](https://getint.io/help-center) or [Schedule a Demo](https://calendly.com/d/cpws-jb2-8xx/demo-call-all-team).

<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, and the optional `goal` query parameter:

```
GET https://docs.getint.io/guides/integration-synchronization/non-jira-connectors.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.