# Welcome to the Getint Documentation Hub
Greetings and a warm welcome to the official documentation page of Getint.io – where every ticket indeed finds its rightful place.
**About Getint:** Getint emerges as a state-of-the-art platform designed to seamlessly integrate and synchronize a wide array of tools including Jira, ServiceNow, Salesforce, Monday.com, ClickUp, Asana, Trello, GitHub, GitLab, Wrike, Zendesk, Azure DevOps, Airtable, Hubspot, Freshdesk, Freshservice with more integrations on the horizon. Whether it's connecting one app to another or orchestrating multi-app integrations, Getint facilitates diverse connectivity scenarios like:
* Single Jira to ServiceNow, or multiple ServiceNows
* Jira to Jira
* Jira to Asana, and simultaneously to GitLab, and beyond.
**Our Foundation:** Founded in 2019 by a team rich in integration expertise, Getint.io was born out of a desire to revolutionize the integration landscape. With extensive experience in the Atlassian Ecosystem and beyond, we observed a gap in the market for modern, agile, and efficiently designed integration solutions. Our journey is driven by three core observations:
* **Innovation Over Legacy**: Confronted with outdated solutions suffering from legacy code issues, we committed to developing a fresh, agile, and high-performing platform leveraging our profound industry experience.
* **Fair Pricing Model**: We challenge the status quo with a pricing structure that ensures the best value for money. This commitment is exemplified by our offer of free migration for users of platforms like ConnectAll, Workato, Unito, Backbone, Exalate, and TFS4JIRA.
* **Focus on Admins and Customization**: While appreciating solutions that prioritize business user-friendliness, our vision was to create a tool that empowers admins with extensive customization options, detailed reporting, and comprehensive logs for deep insights into integration activities. Available as both SaaS and on-premise, Getint is versatile to meet the diverse needs of businesses and legal departments alike.
* **Exceptional Customer Service**: At Getint, customer service is not just a department; it's at the heart of everything we do. We pride ourselves on offering personalized support directly from our team, ensuring that every interaction is meaningful and genuinely focused on solving your challenges.
**Embark on Your Integration Journey with Confidence:** With Getint, embark on a journey of seamless integration and data synchronization crafted to support the most intricate workflows and business requirements. Explore our documentation to get started, discover best practices, and unlock the full potential of your tools with Getint.
Welcome aboard, where your integration success is our mission.
Read more:
* [Case studies](https://www.getint.io/case-studies)
* [Blog posts](https://www.getint.io/blog)
* [Atlassian Marketplace](https://marketplace.atlassian.com/vendors/1218845/getint-integrations-jira-azure-devops-servicenow-salesforce-asana-monday-com-clickup-and-others)
# About Getint / Concepts
### How Getint Helps Your Team
Getint is a platform that connects two or more systems and keeps data aligned between them. It can move information once during a migration or keep it synchronized continuously through an integration.
The platform is designed for enterprise environments, but it stays simple enough for administrators and project teams to configure without writing code.
### Key Concepts You Should Know
#### Integration
An integration keeps data synchronized between two systems. Changes made in one tool appear in the other based on your mapping and sync rules.
#### Migration
A migration moves data from one system to another. It is typically used during tool consolidation or platform changes.
#### Connection
A connection links Getint to an external system. Each connection includes authentication details and configuration settings.
#### Mapping
A mapping defines how fields, statuses, comments, attachments, and other elements relate between the two systems.
#### Run Cycle
A run cycle is the process where Getint checks for changes and updates the connected systems.
#### Conflict Resolution
If both systems change the same item, Getint will apply the latest changes.
### Migration and Integration at a Glance
A simple comparison helps clarify the difference.
| Concept | Purpose | When to Use It |
| ----------- | ---------------------- | ---------------------------------------------- |
| Migration | Move data once | Tool consolidation, platform changes |
| Integration | Sync data continuously | Cross‑team collaboration, multi‑tool workflows |
{% hint style="success" %}
For a deeper explanation, see the dedicated page on [Migration and Integration](https://docs.getint.io/getting-started-with-the-platform/about-getint-concepts/migration-vs-integration).
{% endhint %}
Understanding these core concepts will help you plan your first project and get the most out of the platform. If you need guidance or want help reviewing your setup, you can contact our support team for assistance.
# How Getint Works (How it Syncs the Data)
### Set Up Getint for the First Time
1. **Connect to Applications**: Users begin by connecting Getint to the desired apps (e.g., Jira, ServiceNow, Asana, Azure DevOps). This requires Service Accounts, preferably with admin permissions.
2. **Establishing Connection**: To connect, provide the instance URL and credentials of the Service Account (including instance URL, username, password/token).
3. **Mapping Types and Fields**: The next step involves type mapping (e.g., Task in Jira to Task in Azure DevOps) and field mapping (e.g., Summary in Jira to Title in ServiceNow), including options for comments and attachments integration.
4. **Status Mapping**: Finally, map the statuses between the systems to ensure accurate status reflection across platforms.
#### Platform Operations
**Deployment Flexibility**
* **Jira Native Application**: Getint integrates directly with Jira, requiring no additional installations for other apps you're integrating with Jira.
* **Getint SaaS**: For those preferring a cloud-based solution, Getint offers a Software as a Service (SaaS) model.
* **Getint OnPremise**: Ideal for businesses prioritizing data security, this option works entirely behind the firewall, ensuring maximum data protection.
**Straightforward Pricing**
* We believe in simplicity and transparency. Our pricing is based on the number of connections established (e.g., one Jira instance to one Azure DevOps instance).
* No hidden fees for the number of projects, tasks, rules, templates, or similar metrics.
**REST API Utilization**
* Getint leverages the REST API to communicate with applications like Jira, ServiceNow, etc.
* Through the REST API, we efficiently fetch data that needs to be synchronized between different platforms.
**Synchronization Logic**
Every specified interval, Getint performs the following steps for each integration:
* **Data Fetching**: Send REST API requests to both apps (A and B) to fetch relevant data for synchronization.
* **Sync Check & Update**:
* For each item returned from both apps, we first check if it has been synced in previous runs.
* If it has a counterpart, we determine which item was modified later. The more recent one is used as the trigger to update its counterpart.
* If an item has no counterpart, a new item is created in the corresponding app.
This systematic approach ensures that data across your integrated platforms remains up-to-date and consistent, supporting your workflows and improving productivity.
{% hint style="warning" %}
During a continuous sync, Getint will only sync an item when a field within the work item is modified. Getint does not act retrospectively, so there needs to be an action that triggers a reaction on the tool. Without that change, tickets won't sync.
If you need to move items that already exist and have no triggering change, use the migration process instead. Refer to our migration guides for that specific scenario.
{% endhint %}
# How Integrations are Executed by Getint
## Integration Execution: The Basics
In Getint, each integration runs sequentially, meaning one integration execution must finish before the next one can start. This concept is crucial to understand as it directly impacts the frequency of integration runs.
For instance, Jira Cloud users can only set a run interval of a minimum of 3 minutes, and Data Center customers have run intervals of a minimum of 60-120 seconds (mostly 120 seconds). However, On-Premise users can have run intervals of >= 0 seconds.
When users set an interval for integration (such as every 15 seconds), it’s important to understand that this doesn’t guarantee the integration will occur exactly every 15 seconds. The actual frequency of execution depends on various factors, including the total number of integrations and the duration each integration requires to complete.
### The Impact of Multiple Integrations
If a user has a large number of integrations, it can significantly impact the sync time of changes. For instance, if an item is set to be synced by an integration that is 10th in a queue, and each preceding integration takes 15 minutes (due to the large amount of data they sync), the user may experience a 2-3 hour delay between the change and its propagation.
In a scenario where there are 50 integrations, a 60-second interval won’t be effective because each integration needs to be completed before the next one can start. Therefore, the interval time does not always dictate the frequency of integration runs.
### Boost your Performance with Getint On-Premise
For customers seeking improved performance and parallel integration execution, Getint’s On-Premise solution stands out as a robust choice. This solution allows customers to run multiple threads and assign integrations to them, thereby significantly enhancing performance. Also, On-Premise operates entirely behind your firewall, providing a secure environment aligned with your company requirements.
The benefits of using our On-Premise solution include, but aren’t excluded to:
* Modifying run intervals to your system needs
* Supports multithreading and multi-tenancy
* Saving your data is configurable, which differs from Cloud users who can only retain their data for a maximum of 1 month
* Freedom to perform your own server maintenance and software updates
### Optimizing Integration Settings
To optimize the performance of Getint, users should consider the number of integrations they have and the interval they set for each integration. If there are more than a certain number of integrations, users might need to adjust the intervals to ensure efficient data syncing.
Understanding these nuances can help users make the most of Getint’s powerful integration capabilities and ensure smooth and timely data syncing across platforms. Remember, the key is to find the right balance between the number of integrations and the intervals set for each one.
{% hint style="info" %}
If you have any questions or need assistance with your integration, don’t hesitate to contact our [Support Center.](https://getint.io/help-center)
{% endhint %}
# Migration vs Integration
Getint offers two fundamental functionalities: data migration and continuous sync. Understanding the difference between these two is key to optimizing your use of the platform.
{% hint style="warning" %}
Migration is a premium feature that is limited during the trial version. For detailed pricing information based on the volume of tasks, visit [Getint Pricing](https://www.getint.io/pricing) and click on **Migration.**
{% endhint %}
### Data Migration
#### Definition and Use Case
Data migration in Getint refers to the process of moving historical data—the information that existed before you started using Getint. This is crucial when transitioning from one tool to another, ensuring that all records are preserved. Typical use cases involve migrating data from one platform to another, such as:
* Jira to Azure DevOps
* Asana to Jira
* ClickUp to Monday.com
#### Project Nature
Migration projects are generally one-time operations designed to move a large volume of data within a limited timeframe. This process ensures that historical data is seamlessly transferred to the new system, maintaining the continuity of your workflows.
### Continuous Sync
#### Definition and Use Case
Data integration connects newly created or recently updated items—tasks, service requests, bugs, etc.—in real-time or near real-time. This ongoing process begins the moment you start using Getint, keeping your systems synchronized as new data is generated.
#### Project Nature
Integrations are typically long-term, ongoing projects. They involve syncing smaller batches of data regularly, often daily. Integration is essential for maintaining continuous data flow between different platforms as updates and new items are created.
### Combining Migration and Integration
Some projects require both: initially migrating historical items and then continuously syncing new updates or creations. This approach ensures a comprehensive transition to a new system, followed by consistent and up-to-date synchronization moving forward.
### Pricing Models
* **Migrations:** The cost is based on the **volume of tasks** to be migrated.
* **Integrations:** For integrations involving Jira, pricing is based on the number of Jira users, and billed via the [**Atlassian Marketplace**](https://marketplace.atlassian.com/vendors/1218845/getint-integrations-jira-azure-devops-servicenow-salesforce-asana-monday-clickup-gitlab-and-others). Non-Jira integrations are billed through us directly, and they are available in three different plans:
* **Unlimited $1,800/year - Supported Tools:** ClickUp, Monday, Asana, GitLab, GitHub, Wrike, Hubspot, Zendesk.
* **Professional $4,800/year - Supported Tools:** ServiceNow, Salesforce, Azure DevOps.
* **Enterprise - Custom Pricing:** An unlimited number of tools are supported.
### Setup Process
The setup for both migration and integration is nearly identical in Getint. For migrations, additional steps include enabling the migration feature, specifying the direction (source and target systems), and defining the time range for the issues to be migrated.
# Onboarding
Welcome to the Onboarding page of Getint – your comprehensive guide to getting started and making the most out of our platform.
### **Navigating the Getint Onboarding Experience**
Embarking on your journey with Getint is an exciting step towards enhancing your team's collaboration and workflow efficiency. Our onboarding process is designed to help you swiftly familiarize yourself with Getint’s capabilities, reducing the time and effort required for internal training.
### **What is Getint's Customer Onboarding?**
Getint's customer onboarding is a specialized service aimed at providing a smooth introduction to our platform. This service is tailored to meet the needs of various customer tiers, based on their specific plans. During onboarding, you'll be paired with a dedicated Customer Success Manager who will guide you through the nuances of Getint, from basic functionalities to more complex customization and workflow consultations.
The scope of your onboarding will depend on several factors, including your selected plan, the applications you're integrating, and the overall breadth of your integration project.
### **Key Topics in Getint Onboarding Sessions**
Once you subscribe to Getint, keep an eye on your email for an onboarding invitation. This invite will allow you to schedule a session at a convenient time. If you're struggling to find a suitable slot, don’t hesitate to contact us directly – we're committed to accommodating clients across different time zones.
Onboarding sessions are conducted via platforms like Google Meet or Zoom, facilitating an interactive experience with screen-sharing capabilities.
Your session will be tailored to your specific requirements, covering topics essential for maximizing your use of Getint. A typical onboarding agenda includes:
* Understanding and aligning with your business goals.
* Deep diving into your existing workflow.
* Offering advice on workflow development, especially if you're in the initial stages.
* Providing insights on customizing your flows optimally.
* Introducing you to Getint's latest features and functionalities.
### **Preparing for Your Onboarding**
To get the most out of your onboarding session, here are a few preparatory steps:
* Ensure all relevant tools are connected on the Getint integrations page. Some tools, like Jira, may require additional setup steps prior to integration.
* Set up a few test projects and synchronize them. This exercise will help you formulate specific questions and understand how Getint aligns with your actual workflow.
The Getint onboarding experience is more than just a tutorial – it's a customized journey that equips you and your team with the knowledge and skills to make the most of what Getint has to offer. We look forward to assisting you in streamlining your workflows and achieving your business objectives with Getint.
# One-directional / Bi-directional Integration
### Understanding Integration Types with Getint
In Getint, we offer two primary types of data synchronization between integrated tools: one-directional and bi-directional integration. Understanding these concepts is key to effectively managing data and maintaining smooth synchronization between your workflows.
### One-Directional Integration
In a one-directional integration, data flows in a single direction from a source system to a target system. This means any changes made in the source system will be reflected in the target system, but not vice versa. For example, updates in a Jira project can be automatically reflected in a connected ServiceNow instance, but changes in ServiceNow won’t impact the Jira project. This type of integration is useful for scenarios where data consistency is needed from one primary system to another without reciprocal updates.
### Bi-Directional Integration
Bi-directional integration allows data to flow in both directions – from the source to the target and from the target back to the source. In this setup, changes made in either system are synchronized with the other. For example, updates made in a Jira project and a connected Azure DevOps project are reflected in each other. This approach is ideal for environments where ongoing collaboration and real-time data parity between systems are crucial.
### Flexibility with Getint
A unique feature of Getint is the ability for users to easily switch between one-directional and bi-directional integration at the field level. This means you can customize how each field (such as summary, priority, labels, or custom fields) is synchronized between systems. For instance, you might choose bi-directional synchronization for the “priority” field but one-directional for the “summary” field. This level of control allows users to tailor the integration to their specific workflow and data management needs, ensuring optimal efficiency and data integrity.
### Conclusion
Getint’s flexible integration approach empowers users to configure their data synchronization precisely as needed, whether it be one-directional or bi-directional, or even mixed within the same integration setup. This provides a highly customizable and efficient data integration solution.
Our amazing team at Getint is always here to support you throughout your integration journey. We specialize in providing the best possible customer experience. If you have any questions about this integration or need help with the setup process, feel free to open a ticket with us at our [Help Center](https://getint.io/help-center) or [Schedule a Demo](https://calendly.com/d/cpws-jb2-8xx/demo-call-all-team).
# What are Runs?
In the Getint platform, a "Run" is a critical operation in the synchronization process between connected tools. Here’s an extended explanation, including the recording and logging of each Run.
### Initiating Synchronization:
A Run occurs when Getint sends API requests to connected collaboration tools. These requests aim to gather data on all newly created items and their respective fields, as well as any recent updates, as defined in the integration setup.
### How Run Intervals Affect Your Integration
Integrations execute sequentially, meaning each one must finish before the next can begin. This sequence is essential for understanding how often integrations can run.
For example, Jira Cloud users can set a minimum run interval of 3 minutes, while Data Center customers have a range between 60 to 120 seconds (primarily 120 seconds). However, On-Premise users can set run intervals starting from 0 seconds.
When setting an interval for integration (like every 15 seconds), remember that this doesn't guarantee the integration will occur exactly at that interval. The actual frequency depends on various factors, such as the total number of integrations and the time each one takes to complete.
### Detection and Integration of Changes:
Getint actively searches for new items or changes in existing items during a Run. Detected changes are then integrated, ensuring data across the tools remains synchronized and current.
### Handling Concurrent Changes:
Getint effectively merges data when changes occur simultaneously in the same field across integrated tools. This merging mechanism is crucial for preserving all updates and preventing data loss.
### Recording and Logging of Runs:
Every Run is meticulously recorded and logged within Getint. This means that users have the ability to review and analyze the actions taken during each Run.
The logs provide valuable insights into the outcomes of each synchronization process. They are an essential tool for users to easily identify and understand any errors or discrepancies that may occur.
### Ensuring Data Integrity and Continuity:
Regular Runs are essential for maintaining data integrity and continuity across different platforms. They ensure that all integrated systems reflect the latest and most accurate data.
In summary, a Run in Getint is not only a process of querying and integrating data but also involves a comprehensive recording and logging mechanism. This feature allows users to monitor, analyze, and troubleshoot the synchronization process, ensuring transparency and control over data integration across their collaboration tools.
# 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.
# Starting the Free Trial and Accessing the Getint App
Installing and integrating applications within your Jira tool is a seamless process, provided you have the right access and permissions. This document outlines user-friendly steps for both Jira Server/Data Center and Jira Cloud, ensuring a smooth experience for all users.
### **Starting the Free Trial and Accessing the Getint App**
#### **Jira Cloud Integration**
#### **Admin User**
Access your Atlassian using the admin account, as these steps require admin access to the Jira Cloud. Navigate to the Atlassian marketplace.
* Navigate to the Atlassian Marketplace and select "Explore More Apps."
* Search for the Getint app, select "Try it Free," and let it install.
* Go to "Manage Apps" and, if the trial hasn't started, click "Start Trial."
* When the trial begins, click the "Apps" tab again and choose the Getint app you want to use.
* Once the trial begins, choose the Getint app under the "Apps" tab to initiate integration.
* Users will be routed to the Getint app and prompted to begin their integration. To get started, select integration or migration. (Click here to learn how to begin the integration.)
{% embed url="" %}
**Non-Admin Users**
Non-admin users should request app authorization from administrators
* Select the "Apps" tab, "Explore More Apps," and search for the Getint app.
* Request installation, and administrators will see the request under "Apps > View App Requests."
* After approval, administrators configure the app. Users will not be able to access or view the application.
#### **Jira Server/Data Center**
To follow these instructions, you will need administrator access to the Jira server or data center.
* Go to "Settings" under your avatar, and select "Atlassian Marketplace."
* Search for the Getint app, choose "Free Trial," and accept the installation.
* Generate the license and follow the steps that will appear. Apply the license, go to "Manage Apps," and start the trial if not already initiated.
* After trial or purchase, access the app by selecting Admin in the left menu.
* You will be transferred to the Getint app and prompted to start their integration. To get started, choose integration or migration. (Click here to learn how to begin the integration.)
{% embed url="" %}
{% hint style="info" %}
Admin access to the Jira Server/ Data Center is necessary to administer the apps and enable downloads.
{% endhint %}
### **User Access feature**
We are excited to introduce the User Management Feature, enhancing flexibility and enabling non-admin users to create and manage integrations starting from version 1.52.
*Jira Admin can handle integrations, logs, and data. They can view it and authorize access to it. The system administrator can also troubleshoot all user-created integrations in the user's management views and download logs to submit to support if necessary.*
To enable the User Management Feature option, carefully follow the instructions below:
#### **Jira Cloud**
* In your Jira Cloud instance, log in as an administrator.
* Go to Settings and select "User Management, on the right side, select "Groups." Create a group (e.g., getint-jira-azure), select "View details," and add members.
* To access the application, the user will now see the app under the tab Apps and should click on it. They should select the app, and the Getint app will open. The option to create a new integration will prompt, giving the option to create a new integration if it is the first time accessing the app.
{% embed url="" %}
*Groups created must adhere to the Getint-xx format, such as:*
* getint-jira-jira
* getint-jira-azure
* getint-jira-wrike
* getint-jira-servicenow
* getint-jira-monday
* getint-jira-notion
* getint-jira-airtable
* getint-jira-trello
* getint-jira-hubspot
* getint-jira-gitlab
* getint-jira-freshdesk
* getint-jira-zendesk
* getint-jira-clickup
* getint-jira-asana
{% hint style="warning" %}
**Important:** This naming convention is required for the integration to work correctly.\
For example, if you're connecting **Jira** with **Monday**, the group name must be:\
**`getint-jira-monday`**
{% endhint %}
{% embed url="" %}
#### **Jira Server/Data Center (DC)**
* Enter your Jira Server or Data Center instance and log in as an administrator.
* Navigate to Settings, click the gear in the upper right corner of the screen, then select "User Management." Select "Groups" and create a new group (as Jira Cloud, the format should adhere to *Getint-xx*: getint-jira-azure or Getint-integrations). Please utilize the same format for the groups mentioned above.
* Select "Add," and the newly created group will appear in the group list. Choose "Edit members" and add the username, or choose it from your user list. Select "Add selected users,".
{% embed url="" %}
{% hint style="info" %}
*Access to apps can be given to Project Admin or non-admin users*
{% endhint %}
**Accessing the app:**
**Non-administrative users**
* After being granted access, users will be able to manage the integration, create a new one, and view logs and data.
* To see the application's contents, a non-admin user must get the URL to access the Getint app for now.
**Project Admin User**
* If the user is a project administrator, they will be able to locate the app in the project settings.
* On the project page, select "Project Settings". On the menu that appears, the Getint app will now appear.
* The Getint app will launch, and creating and maintaining the integrations will be possible.
{% embed url="" %}
{% hint style="info" %}
**For all the Non-Jira Admin roles:**
* Other users' integrations are visible but cannot be managed or saved.
* Logs for these integrations are securely encrypted to protect data privacy and cannot be viewed.
{% endhint %}
# Selecting the Correct App per License
When installing an app from the [**Atlassian Marketplace**](https://marketplace.atlassian.com/vendors/1218845/getint-integrations-jira-azure-devops-servicenow-salesforce-asana-monday-clickup-gitlab-and-others), you may encounter issues if the installation is not performed using the correct app, especially when initiating the appropriate trial or license. Following the steps below will ensure a smooth installation and help avoid common errors such as licensing mismatches or failed installations.
{% hint style="warning" %}
If the correct app is not installed, you will encounter an **Invalid Jira license** error, which prevents any work items from being synchronized.
{% endhint %}
On the left, you can see that different apps are available depending on the connectors you want to integrate
### Troubleshooting the Invalid Jira License Error
After you create an integration, if the runs begin to fail, you'll see this message in the run logs. During this period, the integration will not sync any work items.
A warning icon will also appear beneath the license column to indicate an issue with your license.
{% hint style="info" %}
We’re using the Jira Airtable app as an example to build a ServiceNow integration and intentionally force a failure, but this message will appear in any app if you’re using the wrong connector or if your license has expired.
{% endhint %}
To resolve this issue, first assess what integration you would like to build:
1. If you are integrating with **Jira**, first verify if you have an active trial for your integration:
* **Jira Cloud**: Go to the **Subscriptions** section in your billing console and check if your subscription is active.
* **Jira DC**: Go to the **Manage apps** section and locate the Getint app. Click on it to view more information, where all app details will be available.
2. If your trial is active, go to the **Apps** section and select the appropriate app for your integration.
3. If you don’t have an active trial, go to the Atlassian Marketplace and search for **Getint**. All our apps will be listed there. Select the app you need for your integration (in this example, we’ll use ServiceNow).
4. Activate the trial if you still don’t have it:
5. Go back to your **Apps**, and launch the Getint app.
6. You should now be able to build your integrations as needed.
{% hint style="warning" %}
Note: If you are using our app to integrate (e.g., Jira-ServiceNow) and would now like to scale to integrate ServiceNow with DevOps, we can generate a new license key that will enable this within the Jira app.
This additional license key must be purchased separately. For more information, please contact our [Support Center](https://getint.io/help-center).
{% endhint %}
# How to Request a Trial Extension for Getint
If your trial is ending and you need extra time to fully evaluate Getint's capabilities, you can request a trial extension. The process depends on how you’re using Getint (Cloud vs. Server/Data Center) and where your instance is hosted.
### Extending Your Free Trial
#### **For Jira Cloud Users**
1. **Contact Getint Support:**
Start by reaching out to our support team through the in‑app chat or at our [Help Center](https://getint.io/help-center).
* Please include your **company name**, **contact email**, the **reason for the extension request**, and the additional time required.
* After evaluation, we’ll confirm the extension request and provide a screenshot or message you’ll need for Atlassian.
2. **Create a Ticket with Atlassian:**
* Go to the [Atlassian Support](https://support.atlassian.com/) portal, and click **Contact us**.
* Under the drop-down, select **Billing, payments, and pricing**.
* You'll be redirected to a separate page to submit your ticket. Once there, select **Product Trials**, then choose **Extend product trials**.
* Specify that you are requesting an extension for a **third-party app** (Getint), and attach the screenshot from Getint Support confirming the approval request.
3. **Wait for Atlassian's Approval:**
* Atlassian will review the request and notify you once the extension is applied.
#### For Jira Server/Data Center Users
If you are using Getint on **Jira Server or Data Center**, you can **generate one or more extended trial licenses** directly from the Atlassian Marketplace.
1. Go to **Manage apps** in Jira Administration.
2. Find the **Getint app**, remove the current license key, and click **Update**.
3. Click the **Free Trial** button to begin a new trial request.
4. On the next screen, mark the checkboxes and click **Generate License**.
5. Apply the license in Jira and enjoy another trial period (each extension adds 30 more days).
{% hint style="info" %}
Data Center licenses can usually be extended multiple times (up to 5 total extensions).
{% endhint %}
#### For Non-Jira App Users
**Direct Extension Request:**
* Using the trial version of [app.getint.io](http://app.getint.io/) or the On‑premise deployment? No problem. Contact us to request a trial extension. Our team will walk you through the steps to extend your trial so you have plenty of time to continue testing.
If you require additional assistance, don't hesitate to get in touch with our support team.
# Jira Access and User Management
Integrating applications within Jira Server/Data Center and Jira Cloud environments requires careful consideration of access permissions and system configurations. This comprehensive guide provides step-by-step instructions tailored for both environments, ensuring a seamless integration process with Getint.
### Starting the Free Trial and Accessing the Getint App
#### **Jira Cloud Integration:**
**Admin User:**
1. **Access Atlassian Marketplace:**
* Log in to your Atlassian account using admin credentials.
* Navigate to the Atlassian Marketplace and select "Explore More Apps."
2. **Search and Install Getint:**
* Search for the Getint app, select "Try it Free," and install it.
* Go to "Manage Apps" and, if the trial hasn't started, click "Start Trial."
* When the trial begins, select the Getint app under the "Apps" tab to initiate integration.
3. **Start the Integration:**
* Users will be routed to the Getint app and prompted to begin their integration. Choose "Integration" or "Migration" to get started. [(Click here to learn how to begin the integration.)](https://docs.getint.io/guides/quickstart)
{% embed url="" %}
**Non-Admin Users:**
1. **Request App Authorization:**
* Request app authorization from administrators.
* Select the "Apps" tab, "Explore More Apps," and search for the Getint app.
* Request installation and administrators will see the request under "Apps > View App Requests."
2. **Post-Approval:**
* After approval, administrators configure the app. Users will not be able to access or view the application until it is configured.
#### **Jira Server/Data Center Integration:**
**Admin User:**
1. **Access Atlassian Marketplace:**
* Log in as an administrator, go to "Settings" under your avatar, then select "Atlassian Marketplace."
2. **Search and Install Getint:**
* Search for the Getint app, choose "Free Trial," and accept the installation.
* Generate the license and follow the steps that appear. Apply the license, go to "Manage Apps," and start the trial if not already initiated.
3. **Start the Integration:**
* After trial or purchase, access the app by selecting admin in the left menu.
* You will be transferred to the Getint app and prompted to start their integration. Choose "Integration" or "Migration" to get started.
{% embed url="" %}
{% hint style="info" %}
**Note:** Admin access to the Jira Server/Data Center is necessary to administer the apps and enable downloads.
{% endhint %}
#### Verifying your trial license
1. Ensure that the steps generate a valid license. Go to Marketplace > Manage Apps and check the generated license. For Jira Server/DC and Cloud apps, these steps are applicable. For On-premise installation, the license will appear under Settings > License.
### User Access Feature
We are excited to introduce the User Management Feature, enhancing flexibility and enabling non-admin users to create and manage integrations starting from version 1.52.
#### **On-premise:**
1. **Switch the workspace:**
* Select the "Account" icon on the bottom left side and switch to Getint Administration
* Then select "Users" and tap on "Create User."
* On the screen that appears, create a user with the desired credentials.
* The user will be created, and now you need to assign the Workspace that they have access to. Select the three dots on the right and click “Edit”. Assign the workspace, select “add access,” and enable the user.
**Jira Cloud:**
1. **Enable User Management:**
* Log in as an administrator in your Jira Cloud instance.
* Go to Settings, select "User Management," then "Groups."
* Create a group (e.g., getint-jira-azure), select "View details," and add members.
2. **Accessing the App:**
* Users will now see the app under the "Apps" tab and should click on it.
* The Getint app will open, prompting users to create a new integration if it is their first time accessing the app.
{% embed url="" %}
**Groups Naming Requirements**
To ensure smooth integration and avoid any confusion, all groups must follow this naming convention: **getint-jira-xxx**.
**Mandatory Format:**
* getint-jira-jira
* getint-jira-azure
* getint-jira-wrike
* getint-jira-servicenow
* getint-jira-monday
* getint-jira-notion
* getint-jira-airtable
* getint-jira-trello
* getint-jira-hubspot
* getint-jira-gitlab
* getint-jira-freshdesk
* getint-jira-zendesk
* getint-jira-clickup
* getint-jira-asana
{% hint style="warning" %}
**Important Note:** This naming convention is a must for proper integration. For example, if your integration is between Jira and Monday, ensure the group name follows this format: **getint-jira-monday**.
{% endhint %}
**Jira Server/Data Center (DC):**
1. **Enable User Management:**
* Enter your Jira Server or Data Center instance and log in as an administrator.
* Navigate to Settings, click the gear in the upper right corner of the screen, then select "User Management."
* Select "Groups" and create a new group (e.g., getint-jira-azure).
2. **Add Members:**
* Select "Add," and the newly created group will appear in the group list.
* Choose "Edit members" and add the username, or select it from your user list. Select "Add selected users."
{% embed url="" %}
**Groups Naming Requirements**
Same as the steps for Jira Cloud, Jira Data Center Groups must follow this naming convention: **getint-jira-xxx**.
**Mandatory Format:**
* getint-jira-jira
* getint-jira-azure
* getint-jira-wrike
* getint-jira-servicenow
* getint-jira-monday
* getint-jira-notion
* getint-jira-airtable
* getint-jira-trello
* getint-jira-hubspot
* getint-jira-gitlab
* getint-jira-freshdesk
* getint-jira-zendesk
* getint-jira-clickup
* getint-jira-asana
{% hint style="warning" %}
**Important Note:** This naming convention is a must for proper integration. For example, if your integration is between Jira and ServiceNow, ensure the group name follows this format: **getint-jira-servicenow**.
{% endhint %}
**Accessing the App:**
**Non-administrative Users:**
* After being granted access, users can manage the integration, create a new one, and view logs and data.
* To see the application's contents, a non-admin user must get the URL to access the Getint app for now.
**Project Admin User:**
* If the user is a project administrator, they can locate the app in the project settings.
* On the project page, select "Project Settings." On the menu that appears, the Getint app will now appear.
* The Getint app will launch, allowing for creating and maintaining integrations.
**For all Non-Jira Admin Roles:**
* Other users' integrations are visible but cannot be managed or saved.
* Logs for these integrations are securely encrypted to protect data privacy and cannot be viewed.
This comprehensive guide ensures administrators and non-admin users can effectively navigate and utilize the Getint app within Jira Server/Data Center and Jira Cloud environments, promoting a smooth integration process. For further assistance, please get in touch with our support team at our [Help Center](https://getint.io/help-center).
# Deployment Options
Getint is engineered to cater to a diverse range of customer needs, including those with their own infrastructure (on-premise/data center), those preferring cloud-based services (SaaS), and organizations with stringent security requirements. Recognizing security as a pivotal concern for our customers and ourselves, we offer the option of on-premise deployment on the customer's own servers. This flexibility sets us apart in the market, offering tailored deployment options to meet specific needs.
**Deployment Choices:**
* **Jira Cloud - Cloud Hosted by Getint**: Our cloud-hosted solution provides a dedicated platform instance on Getint servers, with a separate database for each instance. This model is the standard for Jira Cloud applications. Jira Cloud customers looking for alternative deployment options can reach out to us at for personalized solutions.
* **Data Center – Native Application (Jira-Specific)**:
For organizations already running Jira Data Center, Getint offers a native application deployment. Unlike the standalone platform, this version is installed via the Atlassian Marketplace and resides within your existing Jira infrastructure.
* **Host (Server) Maintenance**: Managed by the customer as part of their Jira Data Center maintenance.
* **Architecture**: The app runs as a native plugin. For multi-node Jira clusters, Getint uses a cluster lock mechanism to ensure that synchronization tasks are executed on only one node at a time, preventing data duplication or conflicts.
* **Data Residency**: All configuration details, logs, and synced item information are stored within your Jira instance's database and `JIRA_HOME` directory. This ensures that no data ever leaves your internal network.
* **Security**: Operates entirely behind your firewall. Since it is a native app, it inherits the security protocols and user permissions already established in your Jira Data Center environment.
* **On-Premise - Hosted by the Customer**: To accommodate organizations with critical data security needs, such as those in the fintech and health tech sectors, we offer an On-Premise deployment option. This allows for the Getint platform to be installed on customer-owned servers, mirroring the functionality of our SaaS/Cloud model. Once installed and licensed, the platform operates independently of Getint servers, connecting only to authenticated applications set up by the client. All data, logs, passwords, and configurations are securely managed on the client's servers. This model is standard for Jira Server/Data Center applications, ensuring data security and autonomy.
**Why Choose Getint?**
Our commitment to security, coupled with the versatility of our deployment models, underscores our dedication to providing solutions that not only meet but exceed our clients' expectations. Whether you prioritize the control and security of on-premise hosting or the convenience and scalability of cloud services, Getint accommodates your specific requirements, ensuring that your data is handled with the utmost care and respect.
For more information on our deployment options or to discuss the best solution for your organization, please get in touch with us at our [Help Center](https://getint.io/help-center).
# Getint for Jira Cloud
## Getint for Jira Cloud: Deployment & Architecture Guide
### Overview
Getint for Jira Cloud operates as a SaaS (Software as a Service) application. Unlike legacy Jira Server plugins that ran natively within the Java Virtual Machine (JVM) of the host server, the Cloud version functions as an external service that interacts with your Jira instance via secure web protocols.
This deployment model ensures that the integration platform runs independently of your Jira infrastructure, preventing performance impact on your primary project management environment.
### Technical Architecture
The integration relies on a distributed architecture comprising two main components: the Atlassian Connect App and the Getint Platform.
#### The Interface (Iframe-Based Loading)
When a user accesses Getint via the Jira Apps menu, the following process occurs:
* **Request Initiation**: Jira Cloud sends a request to Getint servers to load the application interface.
* **Iframe Execution**: The Getint administration panel loads within a secure iframe inside the Jira UI. This panel is hosted externally on Getint's infrastructure.
* **User Functionality**: From this panel, administrators configure integrations, map fields, and view synchronization reports.
#### Data Synchronization (REST API)
Actual data processing and synchronization occur via the Jira Cloud REST API:
* **External Execution**: The sync engine runs on Getint’s servers, not within Jira.
* **API Requests**: Getint sends authenticated HTTP requests to Jira to read issue data, write updates, upload attachments, or post comments.
* **Storage**: Configuration data (mappings, settings) and synchronization logs are stored on the Getint infrastructure.
### Deployment & Configuration
#### Installation (Direct via Atlassian Marketplace)
In 2025, the standard installation flow starts directly at the external marketplace rather than searching from within the Jira instance.
1. Navigate to [marketplace.atlassian.com](https://marketplace.atlassian.com) in your browser.
2. Search for **Getint** and select the application from the search results.
3. Click the **Try it free** button in the top right corner.
4. If prompted, log in with your Atlassian credentials.
5. Select the Jira Cloud site where you want to install the app from the dropdown menu.
6. Click **Start free trial** to confirm. The app will be installed on your selected instance, and you will be redirected to the success page.
#### User Group Setup
For Jira instances with restrictive permissions, you must follow a specific group naming convention.
* Required Format: `getint-jira-[target-tool]`
* Examples:
* `getint-jira-azure` (for Jira to Azure DevOps)
* `getint-jira-servicenow` (for Jira to ServiceNow)
#### Authentication Requirements
Because the application runs externally, it requires explicit authorization to access your Jira data. Getint uses API Token authentication rather than user passwords, adhering to Atlassian's security standards.
Required Credentials:
* User Email: The email address of the Jira account used for the integration (we recommend a dedicated service account).
* API Token: An Atlassian API Token generated from [id.atlassian.com](https://id.atlassian.com/manage-profile/security/api-tokens).
*Note: The Jira account used for the connection must have the necessary permissions (Browse Projects, Create Issues, Edit Issues) for all projects you intend to synchronize.*
### Security & Data Residency
* Infrastructure: The Getint platform is hosted on AWS (Amazon Web Services).
* Data Handling: While configuration and logs are stored on Getint servers to facilitate the service, the application connects directly to your Jira instance to process ticket data.
* Compliance: The application operates under the Atlassian Cloud Fortified program standards.
### Comparison: Cloud vs. Data Center
| **Deployment** | **Jira Cloud (SaaS)** | **Jira Data Center (Native)** |
| -------------- | ---------------------- | ----------------------------- |
| Hosting | Hosted by Getint (AWS) | Hosted on Customer Server |
| Connectivity | REST API (HTTP) | Native Java API |
| Maintenance | Managed by Getint | Managed by Customer |
| Updates | Automatic | Manual Update Required |
### Deployment Best Practices
* **Dedicated Integration User**: We recommend creating a "Service User" in Jira Cloud for the integration. This ensures that sync activities are not tied to a specific employee's account and provides a clear audit trail in the issue history (e.g., "Updated by Getint Sync").
* **Filter Early**: Use Getint's JQL-based filtering to only sync the tickets you need. This reduces unwanted syncs and optimizes performance.
* **Log Retention**: Customize your log retention settings in the Getint dashboard to align with your organization’s internal data privacy policies.
*For organizations with restricted cloud access, Getint also offers an On-Premise deployment option that can be installed on private servers behind your firewall.*
# Getint for Jira Data Center
## Getint for Jira Data Center & Server: Architecture & Deployment Guide
### Overview
Getint for Jira Data Center and Server is a native application built using the Atlassian Plugins SDK (P2 framework). Unlike the Cloud version, which is a SaaS service, the Data Center version resides entirely within your infrastructure. This deployment type is designed for high-availability environments and organizations with strict data residency requirements.
### 1. Technical Architecture
The application runs as a native plugin within the Jira Java Virtual Machine (JVM).
* **Clustered Environments**: For Jira Data Center instances with multiple nodes, Getint uses a cluster lock mechanism. This ensures that synchronization tasks are executed on only one node at a time, preventing data conflicts or duplicate syncs.
* **Scheduling**: The app initiates a background scheduled job to handle data integration. While users define the sync interval in the settings, the actual execution is managed by the Jira internal scheduler.
* **Internal Communication**: The app communicates with Jira via the Jira Java API and the Internal REST API.
### 2. Data Storage & Security
This deployment model is "Firewall-Friendly" and does not require outbound access to external Getint servers.
* **Local Storage**: All configuration details, mapping logic, and synchronization metadata are stored within your own Jira Database (in dedicated Getint tables).
* **File Storage**: Synchronization logs and temporary files are stored in the `JIRA_HOME/log/getint` directory (or the root `JIRA_HOME` If no log folder exists.)
* **Zero External Connectivity**: When deployed in a standalone on-premise capacity, the platform operates independently of `getint.io` servers. No ticket data ever leaves your internal network.
{% hint style="info" %}
We know Data Center admins have to be careful about storage bloat. If you ever decide to uninstall the app, feel free to clear out any leftover Getint database tables and log files. It’s completely safe to delete them, and it’s actually a great way to keep your instance optimized and clutter-free.
{% endhint %}
### 3. Installation & Licensing
Following the 2025 standard, installation is managed directly via the Atlassian Marketplace.
1. Navigate to the [Atlassian Marketplace](https://marketplace.atlassian.com).
2. Search for Getint and select the version compatible with Data Center.
3. Click Get it now or Try it free.
4. Log in to your Jira instance as a System Administrator.
5. Navigate to Administration (Gear Icon) > Manage Apps.
6. Upload the `.jar` or `.obr` file if you downloaded it manually, or confirm the installation from the Marketplace prompt.
7. License Verification: Access the license settings within the Getint menu to apply your Marketplace license key.
### 4. User Access & Permissions
To manage integrations, users must be granted specific access through Jira Groups.
* Admin Access: System Administrators see the "Getint" menu by default.
* Delegated Access: To allow non-admin users to manage specific integrations, create a group following the naming convention: `getint-jira-[target-tool]` (e.g., `getint-jira-azure-devops`).
* Service Account: We recommend using a dedicated "Service User" to establish the connection. This provides a clear audit trail in issue histories (e.g., "Updated by Getint Integration").
### 5. Key Comparison: Data Center vs. Cloud
| **Feature** | **Data Center (Native)** | **Jira Cloud (SaaS)** |
| --------------- | ---------------------------- | --------------------- |
| Hosting | Customer Infrastructure | Getint (AWS) |
| Data Storage | Local Database & JIRA\_HOME | Getint Infrastructure |
| Cluster Support | Native Cluster Lock | Multi-tenant SaaS |
| Maintenance | Managed by Customer | Managed by Getint |
| External Access | Not Required (Firewall safe) | Required (SaaS model) |
For organizations ready to begin their integration, you can initiate a 30-day free trial directly through the **Atlassian Marketplace** to evaluate the platform in your sandbox or production environment. If your deployment involves complex high-availability configurations or specific security requirements, you can schedule a technical consultation with a Getint specialist. For more information, feel free to contact us at our [Help Center](https://getint.io/help-center).
# Getint Jira Server / Jira Data Center App (Native)
### Overview
Getint for Jira Server and Jira Data Center is installed directly in Jira as a native Atlassian application.
The application runs within your Jira environment and stores its configuration in the Jira database. Synchronization jobs are executed by Jira and do not require a separate Getint-managed service.
This deployment model is commonly used by organizations that require:
* Local infrastructure control
* Internal network connectivity
* Data residency requirements
* Restricted outbound access
* Jira Data Center deployments
* Self-managed environments
### Installation from Atlassian Marketplace
1. Open **Administration** → **Manage Apps**.
2. Select **Find new apps**.
3. Search for the required Getint application.
4. Install the application.
5. Apply the license if required.
After installation, the Getint administration section becomes available in Jira.
### Licensing
Getint licenses are managed through Atlassian Marketplace licensing.
To verify the current license:
1. Navigate to **Administration** → **Manage Apps**.
2. Locate the installed Getint application.
3. Review the license status.
If the license expires, synchronization jobs may stop running depending on the licensing model.
### Configuration Storage
Getint stores integration configuration and synchronization metadata in the Jira database.
No separate database is required.
The application creates dedicated tables for:
* Connections
* Integrations
* Synchronization records
* Processing status
* Execution history
* Error tracking
* System configuration
The exact table names may vary between application versions.
### Scheduled Jobs
Getint uses Jira scheduled services to execute synchronization tasks.
These jobs are responsible for:
* Running integrations
* Processing synchronization queues
* Cleaning up historical data
* Updating synchronization status
### Logs
Getint creates dedicated log files for troubleshooting and operational monitoring.
#### Log Location
The application stores logs in:
```
JIRA_HOME/log/getint
```
If the Jira environment does not contain a log directory, Getint creates:
```
JIRA_HOME/getint
```
#### Log Contents
Logs may contain:
* Synchronization activity
* API requests and responses
* Processing statistics
* Error details
* Diagnostic information
Support may request log files during troubleshooting.
### Data Retention
Synchronization activity generates database records and log entries over time.
Administrators can configure retention periods to control storage growth.
{% hint style="warning" %}
Logs are retained for 14 days by default. You can adjust the retention period to a shorter or longer duration based on your organization's requirements.
{% endhint %}
#### Cleanup Process
A background cleanup job periodically removes:
* Historical synchronization records
* Old execution logs
* Expired processing data
Retention settings can be configured from the Getint administration section.
### Performance Considerations
Synchronization performance depends on several factors:
* Jira server resources
* Database performance
* Integration complexity
* Number of synchronized records
* API limitations of connected systems
For larger deployments, monitor:
* CPU utilization
* Memory consumption
* Database growth
* Synchronization duration
### Testing
Before deploying integrations in production, validate the configuration in a testing environment.
Recommended validation activities include:
* Connection testing
* Authentication verification
* Field mapping validation
* Synchronization rule testing
* Permission verification
Testing helps identify configuration issues before production use.
### Upgrade Process
Application upgrades follow the standard Atlassian Marketplace process.
Before upgrading:
1. Review release notes.
2. Create a Jira backup.
3. Verify compatibility with your Jira version.
4. Test the upgrade in a non-production environment when possible.
### Uninstallation
Removing the application stops all Getint synchronization jobs.
Administrators should review:
* Existing integrations
* Historical synchronization data
* Log files
* Database records
Depending on organizational requirements, additional cleanup may be performed after uninstallation.
For deployment planning, security reviews, or support questions, contact the [Getint team](https://getint.io/help-center).
# Getint for Jira Data Center / Jira Server - Architecture
Jira Server / DC apps are basically installed on the target Jira Server / DC and loaded up within a Jira system, which makes them accessible for the Jira end users. Those Jira Server / DC apps are written mainly in Java with support of Atlassian plugins framework.
Because, as stated on Architecture page, getint.io is a standalone, separate platform, there is still a need to have an instance of getint.io platform installed somewhere. It can be either hosted still by getint.io or installed (as on-premise) on customers owned Linux/Windows servers.
Below diagram, shows simplified architecture of how getint.io cooperates with Jira Server, when getint.io is installed as **On-Premise** software.
Components overview
* Getint.io Jira App - its a one of our apps available on Atlassian Marketplace. When its clicked from *Mange Apps* menu, Jira Server / DC will try to load up (Request 1) an iframe with a source from the getint.io platform. \
Except administration panel (UI), Jira app is used also for License verification purposes.
* Request 1 - it's a request sent by Jira Cloud in order to load up content within an iframe. That iframe will contain an administration panel of the app where all integrations can be managed as well as whole reporting and other system informations can be accessed. When request is successfully authenticated, UI is loaded up
* All the configurations and reporting data is stored **on the owned by customers servers**
* Request 2 - getint.io platform to perform data integration is using standard Jira REST Api. Because all of the requests to Jira REST Api must be authenticated, during integration setup user is asked to provide user credentials (username and password)
{% hint style="info" %}
As can be noticed on the above diagram, with a on-premise deployment mode, getint.io platform and Jira apps are not trying to connect with any servers, including getint.io servers. **That means it is possible to work totally behind firewall.**
{% endhint %}
# Getint On-Premise
To meet the data security requirements of different organizations (like fintech, and health tech companies with very sensitive data), we offer the On-Premise deployment version.
This is practically the same version as the one created in the SaaS/Cloud model, but possible to be installed directly on customers' servers.
{% hint style="info" %}
The On-Premise version of getint.io allows you to be the **owner and administrator** of the processed data during the integration/synchronization.
With that deployment mode, you can have Getint working **fully behind the firewall**. No requests will be performed, except for the apps you are integrating with.
{% endhint %}
## Comparison
| Feature | On-Premise | SaaS (Cloud) | Data Center |
| --------------------------------------------------------- | ------------------------- | -------------------------- | -------------------------- |
| Integration run interval | >= 0s | min 180 seg (3 mins) | min 120 seg (2 mins) |
| Multithreading | Supported | - | Unsupported |
| Multi-tenancy | Supported | One customer - One tenant | Unsupported |
| Software update | Performed by the Customer | Applied by Getint | Performed by the Customer |
| Host (Server) maintenance | Customer | Getint.io | Customer |
| Data retention | Configurable | Fixed. Max 1 month | Configurable |
| Health monitoring | Customer responsibility | Handled by Getint | Customer responsibility |
|
Max number of items to sync per integration run
| Unlimited | Connector based (max 1000) | Connector based (max 1000) |
|
Max number of items to sync per migration run
| Unlimited | 10000 | 10000 |
If you have further questions about our pricing, please visit [Getint.io](https://www.getint.io/) or contact us at our [Support Centre](https://getint.io/help-center). Our integration experts are always happy to help.
# Architecture
Getint.io platform is designed to work as a clustered system with multiple tenants under each cluster. So its possible to create multiple clusters and point forward incoming requests to specific cluster basing on their e.g. subdomains (like ).
**With such approach, its possible to**
* run multiple clusters integrating different apps / software of organisation
* separate and perform integrations of particular partners on dedicated clusters
* within a cluster, setup integrations on separate tenants (e.g. put more resource intensive or business critical integrations on separate tenants)
* have getint.io platform running **Fully Behind Firewall**
{% hint style="info" %}
On-Premise version of getint.io allows you to be the **owner and administrator** of the processed data during the integration / synchronization.
With that deployment mode, you can have getint.io working **Fully Behind Firewall**. No requests, except to the apps you are integrating will be performed.
{% endhint %}
Below you can find cluster high level architecture diagram
Overview
* **Incoming HTTP Requests** is containing information about a cluster and tenant to which it wants to reach. That info can be attached to requests under different technics but for not only subdomain approach is supported. So each tenant within each cluster is having different subdomain e.g. tenant1.getint.mycompany.com
* **Load balancer** is directing the request to the proper cluster
* **Spring Web Application** is the main heart of the cluster. It is receiving incoming requests, authenticates them, extract info about tenant and performs business logics to return a data
* **React UI** is a chosen framework for building modern UI. Its packaged and included within Spring Web Application and server when user visits administration panel
* **Tenant N Thread** as said before, clusters supports *multi-tenancy*. For every tenant separate integration thread is created which is responsible for performing data synchronization according to configured integrations by tenant users
* **PostgreSQL** is a RDBMS of our default choice. Years of experience with that db system make us sure its the best choice we could as a heart of a platform data storage. One of the biggest advantages we found was different supported ways of data replication and most importantly, possibility to store non-relations data
* **Tenant Schema** is created for each tenant within a database to which that cluster is connected. Each tenant has the access **only** to its schema.
# Installation
For those looking for enhanced performance, superior workflow management, efficient operations, and robust data security, On-Premise emerges as an exceptional solution. You’re in control of your data during any changes or updates, and it all happens within your custom server. This ensures that there are no other requests, except for the applications you are integrating. Thus, On-Premise offers a compelling blend of power and privacy.
### How to Install On-Premise
This detailed guide will cover all the necessary steps to install [getint.io](http://getint.io/) in your dedicated network.
#### Installation requirements
* Ubuntu / Debian / Redhat / Windows server / Docker - Server requirements
* **Root user** access
* Your Getint binary and License files. If you do not have them, please get in touch with us at [**support@getint.io**](mailto:support@getint.io)
#### Server requirements
| Minimum | Recommended |
| --------- | ----------- |
| 2GB Ram | 4GB Ram |
| 1 vCPU | 2 vCPU |
| 60 GB HDD | 60 GB SSD |
#### Installation steps
1. **Open your terminal and sign in to the machine as a root user.**
* Use the SSH command and replace `youripaddress` with the hostname or IP address of the server:
| ssh root\@youripaddress |
| ----------------------- |
2. **Enter your password:**
* You’ll be prompted to enter your password for the specified username
3. **Download Getint files:**
* Getint will provide these. Use the command `wget` + the link to the files to download the installation package
* Use the command `ls -al` to see the files in the current directory, and ensure the zip files are located there
4. **Extract the files**
* Use the `unzip` command to extract Getint files in the directory. For instance, it should be like this: `unzip getint-1.58.zip`
* Run `apt install unzip` to download an unzip tool if you don’t have one
5. **Switch to the Getint directory**
* After the installation, switch the directory to the new Getint folder by running `cd getint`
* Now enter `cd synchronizer` to open the Getint installation folder
6. **Make sure you have the necessary tools to run Getint**
* Install Java if it isn’t available on your machine. Enter the command `apt install default-jre` and press **Y** then **Enter** when prompted. Press **ctrl + c** to return to the directory.
* Make sure Java is now installed with the command `java --version`
{% hint style="warning" %}
Please note that we support Java versions 8 through 17.
{% endhint %}
7. **Running Getint**
* Use the command `./manager.sh start` to launch Getint. Press **ctrl + c** to close the logs and return to the directory
* Check if Getint is up and running in the background by using the command `ps -aux | grep getint`
8. **Accessing Getint**
* These are the credentials you can use to log into Getint via your browser:
* Username: admin
* Password: admin
* Open the browser and type the URL which is the machine’s IP address. Alternatively, if you have any domain name assigned to the machine on which Getint is installed, you can type that domain name
* Other commands you can use to manage your instance:
* `./manager.sh stop` stops the integration, so you won’t be able to access it until you start it again
* `./manager.sh restart` restarts the integration in case you have made some changes to the directory
Getint will start on port 80 by default. If port 80 is already in use, change it with the command `vim getint.env`
After switching ports, use the command `cat getint.env` to see the current port in use.
#### Video tutorial
Here’s a video tutorial that demonstrates how to install the On-Premise version.
{% embed url="" %}
### **Docker - Docker-compose installation**
The initial steps are similar to installing Getint on your dedicated machine, but they have remarkable differences in how the app is installed and fully executed. Ultimately, it will depend on your server requirements.
As Docker is a separate tool, please ensure it is installed on your machine before running Getint. Otherwise, Getint won’t start, and your terminal will pop up an error.
1. **Open your terminal and sign in to the machine as a root user.**
* Use the SSH command and replace `youripaddress` with the hostname or IP address of the server:
| ssh root\@youripaddress |
| ----------------------- |
2. **Enter your password:**
* You’ll be prompted to enter your password for the specified username
3. **Download Getint files:**
* Getint will provide these. Use the command `wget` + the link to the files to download the installation package
* Use the command `ls -al` to see the files in the current directory, and ensure the zip files are located there
4. **Extract the files**
* Run `apt install unzip` to download an unzip tool if you don’t have one
* Use the `unzip` command to extract Getint files in the directory. For instance, it should be like this: `unzip getint-1.58.zip`
5. **Switch to the Getint directory**
* After the installation, switch the directory to the new Getint folder by running `cd getint`
* Now enter `cd synchronizer` to open the Getint installation folder
* Use the command `cd docker`, and then `cd scripts`
6. **Installing docker if it isn't installed on your machine**
* The installation path will depend on the tool you’re using. For example, we’re using Ubuntu 20, and the installation package is available here: [Install Docker Engine on Ubuntu](https://docs.docker.com/engine/install/ubuntu/). However, if you’re using a different distribution, click on **Docker Engine**, then click on **Install**, and locate your distribution under this page. After the installation, use the command `docker version` to ensure the tool is installed
7. **Installing docker-compose on your machine**
* It is also necessary to have docker-compose as our installation will consist of the PostgreSQL database, Nginx, and the Getint app. After the installation, use the command `docker-compose version` to ensure the tool is installed
* Docker-compose standalone is available here: [Install Compose standalone](https://docs.docker.com/compose/install/standalone/)
8. **Running Getint**
* While in the scripts folder, enter the command `sh start.sh` to launch Getint
* Ensure Getint is running in the background by using the command `docker container ls`
9. **Accessing Getint**
* These are the credentials you can use to log into Getint via your browser:
* Username: admin
* Password: admin
* Open the browser and type the URL which is the machine’s IP address. Alternatively, if you have any domain name assigned to the machine on which Getint is installed, you can type that domain name
* Other commands you can use to manage your instance:
* `sh stop.sh`
* `sh restart.sh`
Getint will start on port 80 by default. If port 80 is already in use, change it with the command `vim ../docker-compose.yaml`
After switching ports, use the command `docker container ls` to see the current port in use.
#### **Video tutorial**
Here’s a video tutorial on how to Install Getint in a docker.
{% embed url="" %}
{% hint style="info" %}
Our amazing team at Getint is always here to support you throughout your integration journey. We specialize in providing the best possible customer experience. If you have any questions about the setup process, please open a ticket with us at our [Help Center](https://getint.io/help-center) or [Schedule a Demo](https://calendly.com/d/cpws-jb2-8xx/demo-call-all-team).
{% endhint %}
# How to Install Getint On-Premise in Windows Server
This guide provides a step-by-step process for setting up PostgreSQL, Java, and Getint on Windows Server. It covers the installation and configuration of PostgreSQL, downloading and preparing the trial version of our app, and running the application. With these instructions, you can smoothly set up and integrate Getint into your workflow.
{% hint style="warning" %}
This guide is only intended for Getint version v1.70 and above. Please ensure your Getint version is updated to this version before proceeding.
{% endhint %}
### Installing Getint in Windows Server
#### 1. Install PostgreSQL
* Follow all the steps located on the **PostgreSQL** website [here.](https://www.postgresql.org/docs/current/installation.html) All the software packages situated on this website are essential to PostgreSQL's correct function, which would equal the proper installation of Getint.
#### 2. Install JAVA JDK
* Download and install from Oracle's official site: [Java JDK.](https://www.oracle.com/java/technologies/downloads/?er=221886)
{% hint style="info" %}
At Getint, we support Java versions 8 through 17.
{% endhint %}
#### 3. Download and Unzip Getint
* Download the **Getint .zip package** from the provided source.
* Unzip the **downloaded file** to a location of your choice on the Windows Server. For example, you can unzip it to C:\Users\Administrator\Downloads\getint-1.68.
* The [Getint](http://getint.io) team will provide the URL to download the trial version. Please visit our [support portal](https://getint.io/help-center) and open a ticket if you need to download the latest version of Getint for your Windows Server.
#### 4. Open Command Prompt and Navigate to the Synchronizer Folder
* Open a terminal (Command Prompt) on the Windows Server.
* Navigate to the unzipped folder by using the cd command. For example:
#### 5. Start Getint
* **Execute** the `call manager.bat start` command to start Getint:
* Getint will start on **port 80** by default.
* **To change the port**, open the manager.bat file and modify the port number by changing the line set PORT=80 to, for example, set PORT=8080. Then, **restart Getint** if it's already running.
* **To change the database** (you may use our database during the trial period), you can modify the datasource variables also defined in the manager.bat:
```
set SPRING_DATASOURCE_USER=sa
set SPRING_DATASOURCE_PASSWORD=
set SPRING_DATASOURCE_DRIVER=org.h2.Driver
set SPRING_DATASOURCE_URL=jdbc:h2:~/getintio-db;DB_CLOSE_DELAY=-1;INIT=CREATE SCHEMA IF NOT EXISTS public
```
* For example, to connect to the Postgres database, you can provide the following values:
```
set SPRING_DATASOURCE_USER=postgres
set SPRING_DATASOURCE_PASSWORD=postgres
set SPRING_DATASOURCE_URL=jdbc:postgresql://localhost:5432/getint
set SPRING_DATASOURCE_DRIVER=org.postgresql.Driver
```
{% hint style="info" %}
Running the .bat file in this manner will execute its commands in the foreground. This means the process will continue to run as long as the console remains open. Closing the console will stop the process, causing the [Getint.io](http://getint.io) .jar file to stop running. You must set the .bat file as a Windows Service to ensure it runs permanently.
{% endhint %}
#### 6. Open Your Browser and Access Getint
* **Open a web browser** on the same machine where Getint is running. Open your browser and type the URL, which is your machine's IP address. Alternatively, if you have a domain name assigned to the machine on which **Getint** is installed, you can type that domain name. If you have used a port other than 80, remember to include it in the address (i.e., the URL would be `http://10.0.0.32:8089`).
* **Type the machine's URL:**
* Replace PORT with the port number configured in the `getint.env` file (default is 80).
* **The Getint UI should load.**
#### 7. Log In
* Use the following default credentials to sign in:
* Username: admin
* Password: admin
#### 8. Running Getint in the Background Using the Task Scheduler
To allow Getint to launch on startup, you can create a **Basic task** and add it to the **Task Scheduler** as shown below.
* Open the Task Scheduler, and click **Create Basic Task.**
* Name your task to identify it easily if you need to make changes later.
* Select the trigger for your task, also known as when you want the task to start. Select **when the computer starts,** so the run.bat file launches during each startup.
* Select **start a program.**
* Use the Getint path to configure the task.
{% hint style="info" %}
If you need any further help or if you are experiencing issues with your installation, feel free to open a support ticket at our [Support Portal.](https://getint.io/help-center)
{% endhint %}
# On-Premise/Standalone Guide
### Changing Getint license
* Navigate to SYSTEM
* Click on LICENSE tab
* Click EDIT button
* Paste received license from support team
* Click SUBMIT button
New license should be applied and already used by GetInt
### Running GetInt on different HTTP port / HTTPS
GetInt application is Java web application that as all other web apps, can be run on different HTTP ports. HTTP port 80 is a default port.
**How to change port?**
You can simply change it in getint.env file, value for PORT variable, e.g. change it to 8080 port.
```
PORT=8080
```
After a change restart of application will be needed.
**Setting up HTTPS with SSL certificate**
At the moment, easiest way of doing this is to use some proxy server like NGINX which will handle SSL certificates and proxy traffic to GetInt application.
For NGINX, here is a configuration file that when included into NGINX main configuration, will listen at 443 port and for traffic to \. It is loading SSL cert and key. Such traffic will be internally proxied to GetInt application running on \ port.
\ and \ is sth that you have to specify according to your GetInt deployment. \ is domain name which you open when you want to access GetInt and \ is a port defined in getint.env file.
```
server {
listen 443;
server_name ;
ssl_certificate /opt/getint/certs/fullchain.pem;
ssl_certificate_key /opt/getint/certs/privkey.pem;
ssl on;
ssl_session_cache builtin:1000 shared:SSL:10m;
ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
ssl_ciphers HIGH:!aNULL:!eNULL:!EXPORT:!CAMELLIA:!DES:!MD5:!PSK:!RC4;
ssl_prefer_server_ciphers on;
location / {
proxy_pass http://localhost:;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_read_timeout 90;
proxy_redirect http://127.0.0.1: $host;
}
}
```
### Updating version
At the moment updates are handled manually.
There is experimental feature for performing updates in almost fully automatic way but its not yet ready to use in production.
**Manual way**
* Download and unpack new version of GetInt
* From unpacked directory, copy getint.jar file from synchronizer/libs dir and copy to \/synchronizer/libs directory
* Restart application
{% embed url="" %}
# Updating On-Premise
### How to update Getint On-Premise deployed on Linux
1. **Open your terminal and sign in to the machine as a root user.**
* Use the SSH command and replace `youripaddress` with the hostname or IP address of the server:
| ssh root\@youripaddress |
| ----------------------- |
2. **Enter your password:**
* You’ll be prompted to enter your password for the specified username
3. **Open your Getint folder**
* Enter`cd getint` to switch to the Getint directory
* Now enter `cd synchronizer` to open the Getint installation folder
4. **Download Getint files:**
* Getint will provide these. Use the command `wget` + the link to the files to download the installation package. For example, `wget `
* Use the command `ls -al` to see the files in the current directory, and ensure the zip files are located there
5. **Updating Getint**
* Run the command `./upgrade.sh` + the zip file. For example, the full command should be `./upgrade.sh getint-1.62.zip`
* Wait for the files to install and use **ctrl + c** to close the logs and return to the directory
* Alternatively, if you didn’t download the installation package, you can use this command to upgrade your version directly without downloading Getint files separately `./upgrade.sh` + the link to the files.
6. **Access Getint and ensure the version was updated**
* These are the credentials you can use to log into Getint via your browser in case you didn’t change them when installing Getint for the first time:
* Username: admin
* Password: admin
* Open the browser and type the URL which is the machine’s IP address. Alternatively, if you have any domain name assigned to the machine on which Getint is installed, you can type that domain name
* Within Getint, look for the **“?”** icon in the bottom left corner of your screen, and click on it. This will show your current software version. Please verify that your version was upgraded successfully
{% hint style="info" %}
Please test your integration to confirm that it is working without errors. Additionally, if you previously experienced any issues with Getint, check whether they have been resolved after the update. If not, please reach out to our support team at , and we’ll assist you accordingly.
{% endhint %}
#### Video tutorial
{% embed url="" %}
# Cluster High Availability
Availability, in the other words uptime of any software can be implemented in several different ways. It's up to company decisions, policies and best practices which process should be implemented.
## Monitoring
## Availability
Getint.io Cluster application is a combination of different components, mainly Java Application, PostgreSQL database, NGINX balancer. All being built with different frameworks and running independently from each other. All can run on a one or multiple machines, it all depends on a deployment architecture you select.
All of above, can become a point of failure, but after all, business directly depends on a Cluster application and this is what we will focus in first place to monitor and ensure highest possible uptime.
We decided to prepare for you a short guide taking you step by step on how to setup basic and efficient low level monitoring over a Cluster application processes with **Monit** and how to start them up in case of failure.
**Install Monit**
```
sudo apt-get update && sudo apt-get upgrade
sudo apt install monit
sudo monit
```
**Configure**
```
sudo systemctl status monit
# you should see info saying monit is running
sudo vim /etc/monit/monitrc
# - change interval to 60 seconds:
# - uncomment set httpd lines if you want to access monit web ui
```
/etc/monit/monitrc file would look like this
```
set daemon 60 # check services at 2-minute intervals
with start delay 240 # optional: delay the first check by 4-minutes (by
set log /var/log/monit.log
set idfile /var/lib/monit/id
set statefile /var/lib/monit/state
set eventqueue
basedir /var/lib/monit/events # set the base directory where events will be stored
slots 100 # optionally limit the queue size
set httpd port 2812 and
use address # only accept connection from localhost
allow localhost # allow localhost to connect to the server and
allow admin:monit # require user 'admin' with password 'monit'
include /etc/monit/conf.d/*
include /etc/monit/conf-enabled/*
```
Reload Monit
```
sudo systemctl restart monit
sudo systemctl enable monit
```
..
# How to Enable Multi-Threading in Getint
### Enabling Multi-Threading in Getint
Getint supports a multi-threading configuration, allowing integrations to run in parallel. In an **on-premise deployment**, multiple threads can be assigned per tenant based on a predefined setting.
#### Configuring Multi-Threading for On-Premise Deployments
To enable multi-threading, define a **custom property** specifying the number of threads allocated to each tenant. Follow these steps:
1. Navigate to **Custom Properties** ( ).
2. Add a property named SYNC\_THREADS\_NUMBER and set its value to a number greater than 1 (e.g., 3 to create three threads).
3. Restart the Getint service for changes to take effect:
```
./manager.sh restart
```
#### Verifying Multi-Threading Setup
After restarting, go to **Reporting → Sync Jobs** in the Getint UI. The configured number of integration threads should be visible. For example, if SYNC\_THREADS\_NUMBER=3, the UI should display **Thread #0, Thread #1, and Thread #2**.
#### Assigning Integrations to Threads
By default, all integrations run on **Thread #0**. To distribute integrations across multiple threads:
1. Open the integration details page.
2. Navigate to **Settings**.
3. Specify the **Thread ID** to execute that integration.
For example, if **3 threads** were created, valid Thread IDs are: 0, 1, 2.
#### Managing Thread Reductions
If the number of threads is reduced in the future, integrations assigned to non-existing threads must be manually reassigned. For example:
* If **Thread #4** was previously assigned to an integration but the number of threads is reduced to **3**, then **Thread #4 no longer exists**.
* In such cases, update the integration’s settings to use a valid Thread ID (0, 1, or 2).
#### Conclusion
Setting up multi-threading in your on-premise Getint environment can help improve performance and keep integrations running more efficiently. By adjusting a few settings and defining the number of threads, you can allow multiple jobs to run in parallel and support each tenant's setup.
Just remember to keep an eye on thread assignments if you ever decide to change the number of threads. If integrations are still linked to old thread IDs that no longer exist, they’ll need to be updated to make sure everything keeps running smoothly.
# Preparing for the Integration
### **Setting Up Service Accounts**
Before initiating an integration with Getint, one critical step is to prepare and set up Service Accounts in the systems you plan to integrate. Service Accounts act as the bridge through which Getint accesses and synchronizes data between different platforms. Here’s a guide on how to effectively prepare these accounts:
#### Choose the Right Account Type:
* Opt for dedicated Service Accounts rather than personal user accounts. Service Accounts are designed to facilitate automated processes and integrations, ensuring uninterrupted service and more controlled access.
* Comments are added as the user you chose to create the connection. Therefore, we recommend using a dedicated Service Account for this purpose. While there is no technical possibility of adding comments as the original authors, you can still map the assignees. However, issues, incidents, and tasks will be created, and comments will be attributed to the user who established the connection.
{% hint style="info" %}
Example of a comment that was synced with Getint: **`[Author: Radek, Created on: 2024-08-12T12:53:21.711+0000] [Origin: DEMO-346, Comment ID: 26888].`**
Although comments are still attributed to the integration account, the footer includes additional details such as the original author, creation date, the task that triggered the comment, and the comment ID. It’s an industry standard to add comments as one, the default user, but Getint adds the information about the original commenter and the original date of the comment in the footer, which is not an industry standard.
{% endhint %}
### How to Create a Jira Service Account
Atlassian now provides native Service Accounts that are ideal for integrations like Getint. These accounts do not consume a standard user license and are purpose-built for API interactions.
#### Why use a Service Account?
* **Security**: Avoid sharing personal login credentials.
* **Continuity**: Integrations won't break when individual passwords change or when users are deactivated.
* **Audit Trails**: Easily distinguish between actions performed by company users and those performed by Getint.
* **Permission Control**: Only grant the specific access required for the integration.
#### Creating a Service Account
To begin, you need to define the account within your Atlassian Organization.
1. Log in to **admin.atlassian.com**.
2. Select your **Organization** from the list.
3. Navigate to **Directory** > **Service accounts**.
4. Click **Create service account**.
5. Enter a **Name** (for example, `Getint-Sync-Bot`) and an optional **Description**.
6. Select the **user** role for the service account in Jira.
7. Click **Create**.
#### Generate Authentication Credentials
Service accounts cannot log in via a browser UI. You must use an **API Token** with classic or granular scopes.
{% hint style="warning" %}
**OAuth 2.0** isn't supported yet.
{% endhint %}
**Creating an API Token**
1. Go to **Directory** > **Service accounts** and select your account.
2. Click **More actions** (•••) > **Create credentials**.
3. Select **API token** and click **Next**.
4. **Name your token**: Use something descriptive like `Production-Sync-Token`.
5. **Set Scopes**: To know the necessary permissions to connect with Getint, please click [here](https://docs.getint.io/guides/quickstart/connection#forge-apps-onpremise-scoped-tokens).
6. **Set Expiration**: Choose a duration (1–365 days) that aligns with your security policy.
7. **Copy & Save**: Copy the token immediately. You will not be able to see it again.
Your service account is now ready for use with Getint.
#### Document and Maintain:
* Keep a record of the Service Accounts you've created for integration purposes. Document their purpose, associated systems, and any relevant details.
* Regularly review and maintain these accounts. Update credentials periodically and ensure they’re in line with your organization's security policies.
#### Test the Accounts:
* Before finalizing the integration setup, test the Service Accounts to ensure they have the appropriate level of access and can perform all intended functions successfully.
If you're setting up a service account to synchronize Jira with tools like Azure DevOps, ServiceNow, Asana, and so on, check out our [Integration Guides](https://docs.getint.io/guides/integration-synchronization) or reach out to our [Getint support team](https://getint.io/help-center).
# Jira Service Accounts
Before connecting Jira to another tool with Getint, set up a dedicated **Service Account** for the integration. A Service Account is the account Getint uses to read and write data in Jira on your behalf. Using one keeps your integration stable, secure, and easy to audit.
Atlassian provides native Service Accounts that are well-suited to integrations like Getint. These accounts do not consume a standard user license and are purpose-built for API interactions.
***
### Why Use a Service Account?
* **Security**: Avoid sharing personal login credentials.
* **Continuity**: Integrations won't break when individual passwords change or when a user is deactivated.
* **Audit trails**: Easily tell apart actions performed by your team and actions performed by Getint.
* **Permission control**: Grant only the specific access the integration needs.
{% hint style="info" %}
When Getint syncs a comment, it posts under the account that created the connection, not the original author. Posting as the original author is not technically possible, so we recommend using a dedicated Service Account as the connection owner.
To preserve context, Getint adds the original author, creation date, source task, and comment ID to the comment footer.
{% endhint %}
### Creating a Jira Service Account
First, define the account within your Atlassian Organization.
1. Log in to **admin.atlassian.com**.
2. Select your **Organization** from the list.
3. Go to **Directory** > **Service accounts**.
4. Click **Create service account**.
5. Enter a **Name** (for example, `Getint-Sync-Bot`) and an optional **Description**.
6. Select the **user** role for the service account in Jira.
7. Click **Create**.
***
### Generating Authentication Credentials
Service accounts cannot log in through a browser UI, so you authenticate with an **API Token** that has classic or granular scopes.
{% hint style="warning" %}
**OAuth 2.0** is not supported yet.
{% endhint %}
To create an API token:
1. Go to **Directory** > **Service accounts** and select your account.
2. Click **More actions** (•••) > **Create credentials**.
3. Select **API token** and click **Next**.
4. **Name your token**, for example `Production-Sync-Token`.
5. **Set scopes**: See the [required Getint permissions](https://docs.getint.io/guides/quickstart/connection#forge-apps-onpremise-scoped-tokens) for the scopes you need.
6. **Set expiration**: Choose a duration (1 to 365 days) that fits your security policy.
7. **Copy and save** the token immediately. You will not be able to see it again.
Your service account is now ready to use with Getint.
***
### Grant Project and Space Access With a Sufficient Role
Creating the account is not enough on its own. The Service Account must be **added to each Jira Project** (and Space, for Jira Service Management) you intend to sync, and assigned a role with sufficient permissions to perform the sync.
This matters because of how Getint operates: **Getint impersonates the account selected for the integration and can only do what that account is allowed to do.** If the Service Account cannot see a project, transition an issue, edit a field, or add a comment, then the integration cannot either. Missing access is one of the most common causes of failed or partial syncs.
{% hint style="warning" %}
Atlassian Service Accounts are harder to troubleshoot, since we can't log in to them directly. Unlike a regular user account, there's no way to sign in and confirm exactly what the account can and can't access.
{% endhint %}
When assigning the role, make sure the account can:
* **View** the project or space and its issues.
* **Create and edit** issues, incidents, requests, or tasks of the relevant types.
* **Transition** issues through the statuses your mapping uses.
* **Edit the fields** you are syncing, including any required or custom fields.
* **Add comments and attachments**, if those are part of your integration.
{% hint style="warning" %}
Grant access for **every** project or space involved in the integration, including both sides of a sync where Jira is the destination. An account with valid credentials but no access to the target project will still fail to sync.
{% endhint %}
### Modifying a Connection That Uses a Service Account
Once a connection is built on a Service Account, you **cannot freely change it**. Specifically, you can only:
* **Add or replace the access token** for the existing account (for example, when a token expires), or
* **Modify the connection permissions** (the scopes and access granted to that account).
You **cannot** repoint a Service Account connection to a different account, instance, or project through editing. Doing so would break the link between already-synced items and cause data sync errors.
{% hint style="warning" %}
Do not use connection editing to switch to a different instance or project. The new target may be incompatible with items already synced, which causes sync issues.
{% endhint %}
If you are transitioning from a personal account to a Service Account or replacing an expired token, use the **Change Connection** feature in the integration editor. When you do, confirm the new account holds the **same access** to the fields and issues already synchronized, or the integration may encounter sync errors. For finer adjustments, edit the connection from the **Connections** setting in **Workflows**. See [Editing Connections for Existing Integrations](https://docs.getint.io/getintio-platform/connections/editing-connections-for-existing-integrations) for details.
***
### Document and Maintain
* Keep a record of the Service Accounts you create for integrations, including their purpose, the systems they connect to, and any relevant details.
* Review the accounts regularly. Rotate credentials periodically and keep them aligned with your organization's security policies.
***
### Test the Account
Before finalizing the integration, test the Service Account to confirm it has the right level of access and can perform every intended action. Create a test issue, move it through a couple of statuses, and add a comment to verify the account's permissions hold up end-to-end.
If you are connecting Jira with tools like Azure DevOps, ServiceNow, or Asana, see our [Integration Guides](https://docs.getint.io/guides/integration-synchronization) or contact the [Getint support team](https://getint.io/help-center).
# One-to-One, One-to-Many, and Many-to-Many integration
Getint's integration configurations, ranging from one-to-one to many-to-many, are designed to cater to a wide array of synchronization needs.
### One-to-One Integration:
* Involves connecting one instance of a tool (like Jira) with one instance of another tool (like Azure DevOps).
* Pricing: This is covered under a single license of Getint, which includes one instance to one instance integration.
* Ideal for direct, straightforward synchronization between two systems.
### One-to-Many Integration:
* This setup connects a single instance of a tool with multiple instances of different tools.
* Pricing: Each additional connection (beyond the first instance-to-instance link) requires an additional Getint license.
* Suitable for scenarios where a central system (like Jira) integrates with various platforms (e.g., Azure DevOps, Asana, GitLab).
### Many-to-Many Integration:
* Involves multiple independent integrations between various tools or different instances of the same tool.
* Pricing: Each pair of instances (e.g., one ServiceNow instance to one Jira instance) in a many-to-many setup requires its own Getint license.
* Perfect for complex organizational structures needing interconnected systems across various departments or teams.
### Pricing Model and Licenses:
* Getint’s pricing model is straightforward: each license covers one instance-to-instance connection.
* For more intricate setups like one-to-many or many-to-many integrations, each additional connection necessitates an extra license.
* This model ensures that organizations only pay for what they need, allowing for scalability and flexibility in their integration solutions.
By understanding these configurations and the associated pricing model, organizations can plan their integrations with Getint effectively, ensuring they choose the most cost-effective and suitable setup for their specific needs. Whether it's simple direct integrations or complex networks of systems, Getint provides a tailored solution for seamless data synchronization.
# Simplifying Workflow Sync with Getint: Jira
Integrating project management workflows—especially with Jira and other systems—requires careful status and transition mappings for consistency across platforms. This alignment can get complex, so a solid strategy is key.
Most mappings use a simple one-to-one approach (e.g., **To Do** in one system matches **To Do** in another) for streamlined flows. But some scenarios need flexible one-to-many mappings, where one source status links to multiple target statuses to fit diverse workflows.
### Status Mapping with Getint
In Getint, status mappings support both one-to-one and one-to-many approaches for integrating Jira with other systems. This flexibility ensures seamless alignment, whether between Jira instances or with other tools.
Getint offers visual overviews of these mappings, providing a clear view of your workflows and making it ideal for complex Jira integrations.
{% hint style="info" %}
**Note**: Getint makes it easy to map statuses for both one-to-one and one-to-many scenarios. However, if your integration requirements are more complex and involve detailed transition setups, additional customization may be necessary. Our extensive documentation and dedicated [support](https://getint.io/help-center) team are available to assist you in optimizing your workflow transitions.
{% endhint %}
The correct synchronization of a real workflow with restrictions can feel like a puzzle. We want transitions to flow freely, but even with the right transitions, weird warnings might pop up in the logs.
### Understanding the Integration Challenge of Synchronizing Transitions Between Restricted Workflows
Status mappings set the overall relationship, but syncing transitions between restricted workflows is the real challenge—technically, transitions can't always mirror perfectly due to Jira's workflow limits, as each status change follows strict validation rules to keep the path correct; during sync, differences in transition rules between systems cause errors, so we impersonate the integration user to perform actions based on permissions while respecting the workflow setup.
Image from Atlassian Support
#### Addressing Workflow Restrictions in Status Transitions
While status mappings define the primary relationships, synchronizing transitions within restricted workflows can present challenges. Jira workflows often enforce strict transition rules and validation processes, meaning transitions cannot always be perfectly mirrored across systems. Discrepancies in transition rules may lead to errors during synchronization, which can impact integration stability.
{% hint style="danger" %}
If your Jira workflow restricts necessary transitions, you may encounter an error like this: `[WARN ] 2024-10-25T06:16:32.401Z - [a673999b6-30-177094-1] Change to status [name='Test'] was not possible. It looks like the workflow does not contain the required transition to that status.`
If this occurs, please review and adjust your Jira transition settings or contact our support team for further assistance.
{% endhint %}
#### Strategies for Effective Workflow Integration:
1. **Mirror Workflow Structure**: Replicating the original workflow structure, including identical status names and paths, ensures workflow consistency across integrations involving Jira, whether it's Jira to Jira, Jira to ServiceNow, or other project management tools. This replication minimizes the likelihood of errors due to discrepancies in workflow configuration, ensuring smooth and reliable synchronization across all platforms.
2. **Master Account Permissions**: Initiate synchronization from an account with Master Admin privileges. This approach ensures the synchronization process has the necessary permissions to adjust workflows appropriately.
3. **Enable All-to-All Transitions**: Provide the flexibility to change the workflow as needed by adopting a workflow model that allows transitions from one state to another.
#### Enhancing Workflow Flexibility with User-Specific Permissions
An important flexibility aspect comes into play when managing user permissions within a workflow. It's feasible to design a workflow that appears less restricted for certain users while maintaining restrictions for others. This approach caters to the need for both synchronization flexibility and control.
**Steps to Customize Workflows with User-Specific Permissions**
1. **Access Workflow Management in Jira:**
* Select the gear icon next to your profile picture on the top right corner of the screen.
* Select **Issues** to configure the workflows.
* Go to Workflows, then modify or make a copy of your workflow that you would like to change.
2. **Add New Status and Transition:**
* Add a new status and create a transition that allows moving from any status. You can name it **Rest user transition** and connect it to the restricted status.
* Save the changes.
3. **Configure Conditions:**
* Select **Conditions** and add a condition such as **User is in Any Group**.
* Add the groups that are allowed to change these statuses.
4. **Publish and Test:**
* Publish the draft and test the workflow to ensure the new permissions work as expected.
{% embed url="" %}
#### Assessing Project Needs and Customizing Workflows
1. **Review Project Requirements:**
* Identify key stages and transitions needed for the task or issue lifecycle.
2. **Create or Edit Workflows:**
* Add a new workflow or edit an existing one to customize statuses and transitions.
3. **Define Statuses and Transition Rules:**
* Configure statuses like **To Do**, **In Progress**, and **Completed**, and specify transitions for each status.
4. **Implement Transition Screens:**
* Attach screens to transitions to gather necessary information during status changes.
5. **Testing and Feedback:**
* Test the new workflow extensively and collect feedback to refine the setup.
6. **Make Transitions Exclusive:**
* Tailor-specific transitions to be accessible only by certain users or groups.
### Conclusion
Getint integrates workflows across Jira instances to improve operations and team collaboration.
Key steps include status mappings, customizing workflows for user permissions, and a systematic process: plan, test, and refine iteratively. This ensures efficient, flexible project management tailored to your needs.
These strategies solve sync challenges, improving outcomes and creating a more agile environment.
# Understanding the Difference Between Platforms you Integrate
Integrating different tools using Getint involves navigating various technical nuances. Understanding these subtleties ensures effective data synchronization and functionality across systems.
### Field Naming Variations:
* Different tools often use different terminologies for similar fields. It’s crucial to identify these variations and establish a mapping (e.g., Jira's "Summary" to Azure DevOps, "Description").
### Tool-Specific Fields and Custom Field Creation:
* Some fields are unique to specific tools (e.g., "Assignment Group" in ServiceNow, "Area Path" in Azure DevOps).
* Technical Note: To integrate these unique fields, you may need to create corresponding custom fields in the other system to store this data. This ensures that all relevant information is captured and synced accurately.
### Inline Image Support Inconsistencies:
* Different tools have varying capabilities for embedding images within items. This should be considered when setting up integrations to ensure compatibility.
### Out-of-the-Box vs. Custom Fields:
* Tools like Jira offer numerous pre-defined fields, while others, like Monday.com, may start with fewer and require customizations for additional fields.
### Mandatory Fields Variance:
* The presence and enforcement of mandatory fields differ across systems, affecting how data is entered and synchronized.
### Item Type Diversity:
* The range of item types varies significantly among tools, influencing how data is categorized and managed during integration.
### Hierarchy and Structure Complexity:
* The level of hierarchical complexity in tools can vary, impacting how sub-items are managed and synchronized.
### API Documentation and Usability:
* The quality and detail of API documentation can greatly affect the ease of the integration setup and customization.
### Read-Only Field Integration:
* Some fields in certain tools are read-only and can be integrated in only one direction.
* Technical Note: To enable bi-directional integration for such fields, a corresponding writable custom field may need to be created in the other system. This allows for two-way data flow while respecting the read-only nature of the original field.
### Custom Field Support:
* The extent and flexibility of custom field support can vary, affecting how specific data points are handled during integration.
### Integration Limitations and Custom Solutions:
* Each tool has its unique limitations regarding integration. Identifying these early can help in determining the need for workarounds or custom development.
### Workflow Mechanisms and Compatibility:
* The complexity and nature of workflow configurations differ across tools, which should be considered for maintaining process integrity during integration.
In summary, technical preparation and a deep understanding of each tool’s capabilities and limitations are key to a successful integration process with Getint. Custom field creation, proper mapping, and accommodating read-only fields are just some of the technical strategies that can be employed to ensure seamless integration across diverse systems.
### Integration of Collaboration Tools: Detailed Technical Perspective
Integrating various collaboration tools using Getint requires a deep understanding of each platform's unique features and limitations. Here's an expert-level breakdown focusing on common collaboration tools and their differences:
#### Jira and Azure DevOps:
* Jira's "Epic Link" correlates to Azure DevOps' "Parent Work Item."
* 'Sprint' in Jira aligns with 'Iteration Path' in Azure DevOps.
#### ServiceNow and Salesforce:
* ServiceNow's "Assignment Group" can be mapped to a custom field in Salesforce, as Salesforce doesn't have a direct equivalent.
* "Incident State" in ServiceNow differs from "Case Status" in Salesforce in terms of the lifecycle of a ticket.
#### Asana and ClickUp:
* Asana's "Sections" are similar to ClickUp's "Lists" within projects.
* 'Tags' in Asana can be equated to 'Labels' in ClickUp for categorization.
#### Monday.com and GitLab:
* Monday.com's "Pulse" is conceptually similar to GitLab's "Issue."
* Custom status columns in Monday.com need to be mapped to GitLab's "Issue Status."
#### GitHub and Wrike:
* GitHub's "Issues" can be mapped to "Tasks" in Wrike.
* "Milestones" in GitHub have a different implementation compared to Wrike's "Folders/Projects."
#### HubSpot and Trello:
* HubSpot's "Deals" can be somewhat paralleled to Trello's "Cards" in a sales pipeline board.
* "Contact" in Hubspot versus "Member" in Trello reflects the CRM versus project management focus.
#### Zendesk and Jira Service Management:
* "Ticket" in Zendesk corresponds to "Issue" in Jira Service Management.
* Zendesk's "Views" for ticket organization are different from Jira Service Management's "Queues."
#### Read-Only and Custom Fields:
* Tools like Jira and Azure DevOps allow extensive custom fields, which might need to be created in other systems like Monday.com or Trello for a complete sync.
* For read-only fields in systems like Salesforce (e.g., "Created Date"), corresponding writable fields may be necessary in the integrated tool to facilitate bi-directional data flow.
In each case, understanding the specific functionalities and limitations of these tools is crucial. This knowledge informs the creation of custom fields and the mapping process to ensure accurate data synchronization. It's also important to consider the hierarchical structures, workflow mechanisms, and API capabilities of each tool for a successful integration.
# Connectors
# Airtable
## Getint: Simplifying Airtable Integration and Data Synchronization
Getint facilitates seamless integration between multiple platforms, enabling synchronization across tools like Airtable, Jira, Asana, and Azure DevOps. It supports both SaaS and On-Premise deployment, offering adaptability to suit diverse business requirements.
### Key Topics Covered:
* [Installing and Configuring the Application](#installing-and-configuring-getint-for-airtable)
* [Supported Airtable Fields](#supported-airtable-fields)
* [Key Considerations](#key-considerations)
* [Contacting Support - Case Studies](#contacting-our-support-team)
By synchronizing data across instances and platforms, Getint empowers users to efficiently track and manage tasks while integrating Airtable with other project management tools.
### Installing and Configuring Getint for Airtable
Getint simplifies connecting and migrating data between systems. Below are the steps to get started:
**Step 1: Access Getint**
* **Want to integrate Jira with Airtable?** Just download the app from the Atlassian Marketplace. It’s quick and easy! You can find it here: [Airtable Integration for Jira.](https://marketplace.atlassian.com/apps/1231789/airtable-integration-for-jira-airtable-connector?hosting=cloud\&tab=overview)
* Other tools: Select between [Getint On-Premise or SaaS options.](https://app.getint.io/app/auth/sign-up)
**Step 2: Set Up a Connection with Airtable**
* Ensure you have the correct access permissions. Here you will find all the steps to generate an access token in Airtable: [Generating an Airtable Token.](https://docs.getint.io/guides/quickstart/connection#airtable)
* Choose Airtable as the app, create a new connection, and enter your Airtable access token.
**Step 3: Connect to Another Tool**
* Choose the platform you want to integrate with Airtable, such as Jira.
**Step 4: Map Types and Fields**
* Match Airtable issue types, such as Tasks, with their equivalents in the other tool.
* Leverage the Quick Build feature for automatic mapping, or adjust mappings manually to fit your needs.
If you need help with setup or run into any challenges, our support team is always here to assist.
For additional guidance on using Getint with Airtable, refer to:
* [Quickstart Guides](https://docs.getint.io/guides/quickstart)
* [Jira Airtable Integration Guide](https://docs.getint.io/guides/integration-synchronization/jira-airtable-integration)
* [Migration Guides](https://docs.getint.io/guides/migration)
### Supported Airtable Fields
Getint allows you to map fields between different platforms, and here's a list of our currently supported:
{% hint style="info" %}
#### **How Field Mappings Work:**
**One-Way Mapping:**
* When you update fields in one of the synced apps, those changes will appear in the other app. However, updates made in the other app won’t affect the first app because the fields are read-only.
**Two-Way Mapping:**
* Updates to synced fields will be reflected in both apps. If you modify a field in one app, the change will automatically sync to the other app as well.
**Tip:**
While technically it's not possible to directly modify read-only fields, we offer a solution to achieve bidirectional integration or migrate these fields using custom fields. Setting up this solution requires specific steps, but it is indeed possible. You can find more detailed information in this [article.](https://docs.getint.io/getting-started-with-the-platform/prepare-for-integration/understanding-the-difference-between-platforms-you-integrate)
{% endhint %}
| **Airtable Field** | **One Way** | **Both Ways** |
| ---------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Attachments | | |
| Comments | ✔️ | ✔️ |
|
Custom Fields
Long Text - Rich Text Field -Single Line Text - Single Select
| ✔️ | ✔️ |
| ID | ✔️ | |
| Item Type | ✔️ | |
| Last modified time | ✔️ | ✔️ |
| Name | ✔️ | ✔️ |
| Notes | ✔️ | ✔️ |
| Record API URL | ✔️ | |
| Status | ✔️ | ✔️ |
| URL | ✔️ | |
{% hint style="danger" %}
**Important Note:** While we make every effort to ensure the accuracy of this list, please be aware that supported fields may differ in the original product.
{% endhint %}
### Key Considerations
At Getint, we are committed to continuously updating our supported features, fields, and compatible apps. However, please keep the following key points in mind:
* **Attachments** aren't supported.
* **Change History**: Getint cannot integrate the history of changes.
* **Comments**: Comments added by Getint will appear under the user account you choose during connection setup. Consider creating a dedicated Service Account for integration to maintain consistency. The original author’s name will appear in the comment footer, but the comment will be assigned to the connecting account. Also, comments and attachments transferred from Airtable to Jira will be set to public or private (they will be public by default). You can configure Jira to mark all comments from Airtable as private automatically. However, enabling both public and private visibility options is impossible.
* **Rich text** formatting is supported for text fields.
### Contacting Our Support Team
Our dedicated Support Team is here to assist with your integration and migration needs. Whether you have questions or seek deeper insights into our solution, you’re welcome to schedule a [demo call](https://www.getint.io/schedule-demo-call) with us.
#### Case Studies
Discover how Getint enhances tool integration for businesses of all sizes. Our [Case Studies](https://www.getint.io/case-studies) highlight real-world solutions designed to empower teams and organizations.
{% hint style="info" %}
**Looking for a solution we don’t currently support?** Reach out to our [support team](https://getint.io/help-center); we’d be happy to help you explore a customized solution tailored to your needs.
{% endhint %}
# Asana
## Getint: Simplifying Asana Integration and Data Synchronization
Getint is expertly designed to integrate and synchronize an extensive range of tools. It accommodates a variety of connectivity scenarios, such as Asana - Jira, Asana - Asana, Asana - Monday, Asana - Azure DevOps, and more. With its availability as both a Software-as-a-Service (SaaS) and On-Premise solution, Getint offers the versatility to meet the unique requirements of various businesses.
### Key Topics Covered:
* [How to Set Up the App](#what-does-this-article-cover)
* [Supported Fields in Asana](#setting-up-getint-for-asana)
* [Limitations and Considerations to Make](#limitations-to-be-considered)
* [Contacting Our Support Team - Case Studies](#contacting-our-support-team)
Getint enables seamless data synchronization within the same platform, different platforms/different instances. It supports Asana across different projects. This allows users to efficiently track and manage Asana tasks and subtasks in diverse environments as well as integrate Asana with other platforms.
### Setting Up Getint for Asana
Getint simplifies data integration and migration. With easy setup steps, you can connect your systems, such as Asana, map types (i.e. Task - Task), and fields (i.e. Assignee - Assignee). Whether you're looking to sync data continuously or perform a one-time migration, Getint has got you covered. Our dedicated support team is always ready to assist you with any challenges you may encounter during setup or operation.
For more detailed guides on how to set up your Asana integration, please make sure to check the following:
* [Starting with Getint - Quickstart Guides](https://docs.getint.io/guides/quickstart)
* [Integration Guides](https://docs.getint.io/guides/integration-synchronization)
* [Migration Guides](https://docs.getint.io/guides/migration)
* [Understanding Getint - Workflows](https://docs.getint.io/getintio-platform/workflows)
Here's a simplified version of how to integrate Asana with other tools (you can find a detailed overview [**here**](https://docs.getint.io/guides/integration-synchronization/jira-asana-integration)):
1. **Access Getint:**
* If you’re using Jira, go to "Apps," "Find new apps," and get the app from the Atlassian Marketplace.
* If you want to integrate Asana with any other, non-Jira application, opt for the [Getint On-Premise or Getint SaaS](https://app.getint.io/).
2. **Token Generation for Asana:** Visit your Asana Settings. Go to the "Apps" section and launch the developer console. Now, click "Create new token" in the developer console under "Personal access token." This will serve as the password to create your connection.
3. **Establish a Connection with Asana:** Ensure you're logged in as a user with the correct permissions. Click "Select App" and choose Asana. Select "Create New" to establish a new connection with your Asana instance. Name your connection, and add the URL of your Asana instance (without "/" at the end). Provide the login credentials.
4. **Choose and Connect the Second App:** Choose and connect another tool you'd like to integrate with Asana—either another Asana instance, DevOps, Jira, or any other tool that we support.
5. **Map Types and Fields:** Link Asana types (Task, Subtasks) to synchronize with other tools. You can use the "Quick Build" feature, which allows you to map available fields automatically, or you can set them manually.
Getint's support team is committed to ensuring a smooth and efficient integration experience customized to your unique needs. If you encounter any challenges during setup or require assistance with missing functionalities, our dedicated support team is readily available to provide guidance and help.
### Supported Fields in Asana
Getint allows you to map fields between different platforms, and here's a list of our currently supported:
{% hint style="info" %}
### **How Field Mappings Work:**
**One-Way Mapping:**
* When you update fields in one of the synced apps, those changes will appear in the other app. However, updates made in the other app won’t affect the first app because the fields are read-only.
**Two-Way Mapping:**
* Updates to synced fields will be reflected in both apps. If you modify a field in one app, the change will automatically sync to the other app as well.
**Tip:**
While technically it's not possible to directly modify read-only fields, we offer a solution to achieve bidirectional integration or migrate these fields using custom fields. Setting up this solution requires specific steps, but it is indeed possible. You can find more detailed information in this [article.](https://docs.getint.io/getting-started-with-the-platform/prepare-for-integration/understanding-the-difference-between-platforms-you-integrate)
{% endhint %}
| **Asana Field** | **One Way** | **Both Ways** |
| ----------------------------------------------------------------------------------------------- | ----------- | ------------- |
| Assignee | ✔️ | ✔️ |
| Attachments | ✔️ | ✔️ |
| Created | ✔️ | |
| Comments | ✔️ | ✔️ |
| Completed | ✔️ | ✔️ |
|
Custom fields
Single-select - Date - Text - Number - Formula - ID
| ✔️ | ✔️ |
| Description (Notes) | ✔️ | ✔️ |
| Estimated time | ✔️ | ✔️ |
| ID | ✔️ | |
| Priority | ✔️ | ✔️ |
| Reporter | ✔️ | ✔️ |
| Section | ✔️ | ✔️ |
| Start date | ✔️ | ✔️ |
| Status | ✔️ | ✔️ |
| Subtasks | ✔️ | ✔️ |
| Tags | ✔️ | ✔️ |
| Title (Name) | ✔️ | ✔️ |
| URL | ✔️ | |
{% hint style="danger" %}
**Important Note:**\
We strive to maintain the accuracy of this list, but please be aware that supported fields may vary in the original product.
{% endhint %}
### Limitations to be Considered
At Getint, we’re constantly updating our supported features, fields, and compatible apps. However, there are a few limitations you should be aware of:
* When a new issue is created in Asana by Getint, it will always be one type of issue, whether that's a Task or a Subtask. You can set the default item type using a rule or manually change it in Asana after it's created.
* Comments will be added as the user you choose to create the connection. Therefore, it is advised to create a dedicated Service Account to build your integration. The original author will appear in the comment footer; however, it will still be assigned to the account that established the connection.
* The history of changes can't be integrated.
### Contacting Our Support Team
Our Support Team at Getint is eager to assist with your integration and migration needs and answer any other questions you may have. If you're seeking assistance or a deeper understanding of our solution, we invite you to schedule a demo call [here](https://www.getint.io/schedule-demo-call).
#### Case Studies
Large and small businesses have experienced the benefits of using Getint for their data integration needs. This has provided them with various solutions tailored to their teams and organizations. We invite you to explore some of our [Case Studies](https://www.getint.io/case-studies), which are true accounts of how Getint continually enhances and improves the tool integration process.
{% hint style="info" %}
**Are you looking for a specific solution that we don’t currently support?** Please get in touch with our [support team](https://getint.io/help-center), and we can assist you in developing a customized solution for your particular case.
{% endhint %}
# Azure DevOps
## Getint: Simplifying Azure DevOps Integration and Data Synchronization
Getint is expertly designed to integrate and synchronize an extensive range of tools. It accommodates a variety of connectivity scenarios, such as Azure DevOps - Jira, Azure DevOps - Asana, Azure DevOps - Monday, Azure DevOps - ServiceNow, and more. With its availability as both a Software-as-a-Service (SaaS) and On-Premise solution, Getint offers the versatility to meet the unique requirements of various businesses.
### What Does this Article Cover?
* [How to Set Up the App](#setting-up-getint-for-azure-devops)
* [Supported Fields in Azure DevOps](#supported-fields-in-azure-devops)
* [Limitations and Considerations to Make](#limitations-to-be-considered)
* [Contacting our Support Team - Case Studies](#contacting-our-support-team)
**Getint** facilitates smooth data synchronization across various platforms and instances. It specifically supports **Azure,** allowing users to monitor and manage tasks in diverse environments effectively. Additionally, it enables seamless integration with other platforms.
### Setting Up Getint for Azure DevOps
Getint simplifies data integration and migration. With easy setup steps, you can connect your systems, such as Azure DevOps, map types (i.e. Epic - Epic), and fields (i.e. Assignee - Assigned to). Whether you're looking to sync data continuously or perform a one-time migration, Getint has got you covered. Our dedicated support team is always ready to assist you with any challenges you may encounter during setup or operation.
For more detailed guides on how to set up your Azure integration, please make sure to check the following:
* [Starting with Getint - Quickstart Guides](https://docs.getint.io/guides/quickstart)
* [Integration Guides](https://docs.getint.io/guides/integration-synchronization)
* [Migration Guides](https://docs.getint.io/guides/migration)
* [Understanding Getint - Workflows](https://docs.getint.io/getintio-platform/workflows)
Here's a simplified version of how to integrate Azure with other tools (you can find a detailed overview [**here**](https://docs.getint.io/guides/integration-synchronization/jira-azure-devops-integration)):
1. **Access Getint:** If you’re using Jira, navigate to the "Apps" section, search for new apps, and acquire the app from the [Atlassian Marketplace](https://marketplace.atlassian.com/apps/1223931/azure-devops-integration-for-jira-azure-devops-connector?hosting=cloud\&tab=overview). Alternatively, if you need to integrate Azure DevOps with a non-Jira application, consider choosing either [Getint On-Premise or Getint SaaS](https://www.getint.io/contact).
2. **Token Generation for Azure DevOps:** Click on your user profile icon, navigate to the "Personal access tokens" section, and click "New token." Provide a name for the token, select the relevant organization, set an expiration, and choose "Full Access" in the scopes. This token will serve as your password to connect with Getint.
3. **Establish a Connection with Azure DevOps:** Ensure you're logged in as a user with the correct permissions. Click "Select App" and choose "Azure DevOps." Select "Create New" to establish a new connection with your Azure DevOps instance. Name your connection, and add the URL of your Azure instance. Provide the login credentials.
4. **Choose and Connect the Second App:** You can select and link an additional tool to integrate with Azure DevOps. Options include another Azure instance, ServiceNow, Jira, or any other supported tool.
5. **Map Types and Fields:** Link "Azure types" (Epics, Tasks, Issues) to synchronize with other tools. You can use the "Quick Build" feature, which allows you to map available fields automatically, or you can set them manually.
Getint's support team is committed to ensuring a smooth and efficient integration experience customized to your unique needs. If you encounter any challenges during setup or require assistance with missing functionalities, our dedicated support team can provide guidance and assistance.
### Supported Fields in Azure DevOps
Getint allows you to map fields between different platforms, and here's a list of our currently supported:
{% hint style="info" %}
#### **How Field Mappings Work:**
**One-Way Mapping:**
* When you update fields in one of the synced apps, those changes will appear in the other app. However, updates made in the other app won’t affect the first app because the fields are read-only.
**Two-Way Mapping:**
* Updates to synced fields will be reflected in both apps. If you modify a field in one app, the change will automatically sync to the other app as well.
**Tip:**
While technically it's not possible to directly modify read-only fields, we offer a solution to achieve bidirectional integration or migrate these fields using custom fields. Setting up this solution requires specific steps, but it is indeed possible. You can find more detailed information in this [article.](https://docs.getint.io/getting-started-with-the-platform/prepare-for-integration/understanding-the-difference-between-platforms-you-integrate)
{% endhint %}
| **Azure DevOps Field** | **One Way** | **Both Ways** |
| -------------------------------------------------------------------------------------------------------------------------------------------- | ----------- | ------------- |
| Activated By | ✔️ | ✔️ |
| Activated Date | ✔️ | ✔️ |
| Activity | ✔️ | ✔️ |
| Area ID | ✔️ | ✔️ |
| Area Path | ✔️ | ✔️ |
| Assigned To (Assignees) | ✔️ | ✔️ |
| Changed By | ✔️ | ✔️ |
| Closed By | ✔️ | ✔️ |
| Closed Date | ✔️ | ✔️ |
| Created By | ✔️ | ✔️ |
| Completed Work | ✔️ | ✔️ |
|
Custom fields
Date - Decimal - Identity - Integer - Picklist - Picklist integer - Text (Single/Multiple lines)
| ✔️ | ✔️ |
| Description (System.Description) | ✔️ | ✔️ |
| ID | ✔️ | |
| Iteration ID | ✔️ | ✔️ |
| Iteration Path | ✔️ | ✔️ |
| Priority | ✔️ | ✔️ |
| Reason | ✔️ | ✔️ |
| Remaining Work | ✔️ | ✔️ |
| Resolved By | ✔️ | ✔️ |
| Resolved Date | ✔️ | ✔️ |
| Stack Rank | ✔️ | ✔️ |
| State | ✔️ | ✔️ |
| State Change Date | ✔️ | ✔️ |
| Status | ✔️ | ✔️ |
| Story Points | ✔️ | ✔️ |
| Tags | ✔️ | ✔️ |
| Target Date | ✔️ | ✔️ |
| Team Project | ✔️ | ✔️ |
| Title | ✔️ | ✔️ |
| URL | ✔️ | |
| Work Item Type | ✔️ | ✔️ |
{% hint style="danger" %}
**Important Note:**\
We strive to maintain the accuracy of this list, but please be aware that supported fields may vary in the original product.
{% endhint %}
### Supported Item Types for Azure DevOps Integration
| Code Review Request | Code Review Response |
| ------------------- | -------------------- |
| Epic | Feedback Request |
| Issue | Feedback Response |
| Shared Parameter | Task |
### Limitations to be Considered
At Getint, we continuously update our supported features, fields, and compatible apps. However, there are a few important limitations to keep in mind:
* When Getint creates a new issue in Azure DevOps, it will always be one specific type of issue: an Epic, an Issue, a Test Plan, or a Task (to name a few). You can set the default item type with Getint or manually change it in Azure after it's created.
* Comments added to the issue will appear under the user account you choose to create the connection. To ensure seamless integration, creating a dedicated Service Account is recommended to build your integration. Although the original author’s name will appear in the comment footer, the comment will still be associated with the account that established the connection.
* Unfortunately, integrating the history of changes is not possible.
### Contacting Our Support Team
Our Support Team at Getint is eager to assist with your integration and migration needs and answer any other questions you may have. If you're seeking assistance or a deeper understanding of our solution, we invite you to schedule a demo call [here](https://www.getint.io/schedule-demo-call).
#### Case Studies
Large and small businesses have experienced the benefits of using Getint for their data integration needs. This has provided them with various solutions tailored to their teams and organizations. We invite you to explore some of our [Case Studies](https://www.getint.io/case-studies), which are true accounts of how Getint continually enhances and improves the tool integration process.
{% hint style="info" %}
**Are you looking for a specific solution that we don’t currently support?** Please get in touch with our [support team](https://getint.io/help-center), and we can assist you in developing a customized solution for your particular case.
{% endhint %}
# ClickUp
## Getint: Simplifying ClickUp Integration and Data Synchronization
Getint connects and synchronizes multiple tools, enabling seamless integrations between platforms such as ClickUp, Jira, Asana, and Azure DevOps. Available as both a Cloud and an on-premise solution, Getint offers the flexibility to meet diverse business requirements.
### Key Topics Covered:
* [Setting Up the App](#how-to-set-up-getint-for-clickup)
* [Supported Fields in ClickUp](#supported-fields-for-clickup-integration)
* [Limitations and Considerations](#limitations-and-considerations)
* [Contacting Support](#contacting-our-support-team)
Getint synchronizes data across platforms or instances, including ClickUp, allowing users to monitor and manage tasks and activities across projects while integrating ClickUp with other tools.
### How to Set Up Getint for ClickUp
Getint makes it easy to connect systems and synchronize or migrate data between them. Follow the steps below to get started with ClickUp.
**Step 1: Access Getint**
* **For Jira users**: If you plan to integrate Jira with ClickUp, download the Getint app from the [Atlassian Marketplace](https://marketplace.atlassian.com/apps/1231636/clickup-integration-for-jira-2-way-clickup-connector?hosting=cloud\&tab=overview).
* **For other tools**: Choose between Getint's **SaaS** or **On-Premise** deployment options, depending on your requirements.
**Step 2: Set Up a Connection with ClickUp**
* Ensure you have the necessary [access permissions](https://docs.getint.io/guides/quickstart/connection#clickup) in ClickUp.
* Select **ClickUp** as the application.
* Create a new connection and enter your ClickUp credentials.
**Step 3: Connect to Another Tool**
* Choose the platform you want to integrate with ClickUp, such as **Jira**, **Asana**, or **Azure DevOps**.
**Step 4: Map Types and Fields**
* Match ClickUp entities (for example, tasks, custom fields, or statuses) with their corresponding entities in the other tool.
* Use the **Quick Build** feature for automatic mapping, or manually customize mappings to fit your workflow.
Our support team is always available to help with setup or operational questions.
For additional guidance on using Getint with ClickUp, refer to:
* [Quickstart Guides](https://docs.getint.io/guides/quickstart)
* [Jira ClickUp Integration Guide](https://docs.getint.io/guides/integration-synchronization/jira-clickup-integration)
* [Migration Guides](https://docs.getint.io/guides/migration)
### Supported Fields for ClickUp Integration
Getint enables field mapping between ClickUp and other platforms. Below is an overview of the currently supported field-mapping options and their functionality.
{% hint style="info" %}
#### **How Field Mappings Work:**
**One-Way Mapping:**
* When you update fields in one of the synced apps, those changes will appear in the other app. However, updates made in the other app won’t affect the first app because the fields are read-only.
**Two-Way Mapping:**
* Updates to synced fields will be reflected in both apps. If you modify a field in one app, the change will automatically sync to the other app as well.
**Tip:**
While technically it's not possible to directly modify read-only fields, we offer a solution to achieve bidirectional integration or migrate these fields using custom fields. Setting up this solution requires specific steps, but it is indeed possible. For more detailed information, please refer to this [article.](https://docs.getint.io/getting-started-with-the-platform/prepare-for-integration/understanding-the-difference-between-platforms-you-integrate)
{% endhint %}
| **ClickUp Field** | **One Way** | **Both Ways** |
| -------------------------------------------------------------------------------------- | ----------- | ------------- |
| Assignee | ✔️ | ✔️ |
| Comments & Attachments | ✔️ | ✔️ |
|
Custom Fields
Dropdown - Labels - Number - People - Text
| ✔️ | ✔️ |
| Description | ✔️ | ✔️ |
| Id | ✔️ | |
| Item Type | ✔️ | |
| Status | ✔️ | ✔️ |
| Tags | ✔️ | |
| Title | ✔️ | ✔️ |
| URL | ✔️ | |
{% hint style="warning" %}
**Important Note:**\
We strive to maintain the accuracy of this list, but please be aware that supported fields may vary in the original product.
{% endhint %}
### Limitations and Considerations
At Getint, we continuously update our supported features, fields, and compatible apps. However, there are a few important points to consider:
* **Attachments**: Inline images aren’t supported for the Description field.
* **Change History**: Unfortunately, Getint cannot integrate the history of changes.
* **Comments**: Comments added by Getint will appear under the user account you choose during connection setup. Consider creating a dedicated Service Account for integration to maintain consistency. The original author’s name will appear in the comment footer, but the comment will be assigned to the connecting account.
* **Issue Types**: Currently, the integration supports ClickUp tasks as the only issue type.
* **Item Hierarchy**: Sub-items are not currently supported in Jira–ClickUp synchronization.
* **Multi-project Support**: Many-to-many project synchronization between Jira and ClickUp is not supported.
* **Synchronization Scope**: In ClickUp, you can specify a Space and Folder, but not an individual List, which means all lists in a folder are synced.
* **Text Formatting Errors**: Formatting is not fully preserved during synchronization; bullet points may not convert correctly in Jira, and embedded links can be removed.
### Contacting Our Support Team
Our dedicated Support Team is ready to assist with your integration and migration needs. If you have questions or need deeper insights into our solution, feel free to schedule a [demo call](https://www.getint.io/schedule-demo-call) with us.
#### Case Studies
Explore real-world examples of how Getint enhances tool integration for businesses of all sizes. Our [Case Studies](https://www.getint.io/case-studies) showcase tailored solutions that empower teams and organizations.
{% hint style="info" %}
**Are you looking for a specific solution that we don’t currently support?** Please get in touch with our [support team](https://getint.io/help-center), and we can assist you in developing a customized solution for your particular case.
{% endhint %}
# Freshdesk
## Getint: Streamlining Freshdesk Integration and Data Synchronization
Getint revolutionizes the integration and synchronization of various tools, including Freshdesk. It supports diverse connectivity scenarios such as Freshdesk-Jira, Freshdesk-Asana, Freshdesk-Monday, Freshdesk-Azure DevOps, and more. Whether you need a SaaS or On-premise solution, Getint offers the flexibility to meet the unique needs of different businesses.
### The Article Covers the Following Topics:
* [How to Set Up the App](#setting-up-getint-for-freshdesk)
* [Supported Fields for Freshdesk Integrations](#supported-fields-for-freshdesk-integrations)
* [Limitations and Considerations to Keep in Mind](#limitations-to-keep-in-mind)
* [Case Studies and Contacting Our Support Team](#case-studies-and-support-contact)
Getint ensures seamless data synchronization across platforms and instances, specifically supporting Freshdesk. Users can efficiently monitor and manage tasks in diverse environments while integrating seamlessly with other platforms.
### Setting Up Getint for Freshdesk
Getint simplifies data integration and migration. Follow these straightforward steps to connect your systems, such as Freshdesk, map types (i.e., Task - Incident), and fields (i.e., Description - Description). Whether you’re syncing data or performing a continuous one-time migration, Getint has you covered. Our dedicated support team is ready to assist you with any setup or operational challenges.
For more detailed guides on setting up your Freshdesk integration, refer to the following resources:
* [Starting with Getint - Quickstart Guides](https://docs.getint.io/guides/quickstart)
* [Integration Guides](https://docs.getint.io/guides/integration-synchronization)
* [Migration Guides](https://docs.getint.io/guides/migration)
* [Understanding Getint - Workflows](https://docs.getint.io/getintio-platform/workflows)
#### Simplified Freshdesk Integration Process
Here's a simplified version of how to integrate Freshdesk with other tools (you can find a detailed overview [**here**](https://docs.getint.io/guides/integration-synchronization/jira-freshdesk)):
1. **Access Getint:** If you’re using Jira, navigate to the **Apps** section, search for new apps, and acquire the app from the [Atlassian Marketplace.](https://marketplace.atlassian.com/apps/1227929/freshdesk-freshservice-jira-works-behind-the-firewall?hosting=cloud\&tab=overview) Alternatively, if you need to integrate Freshdesk with a non-Jira application, consider choosing either [Getint On-Premise or Getint SaaS.](https://www.getint.io/contact)
2. **Token Generation for Freshdesk:** Log in to your Freshdesk account, click on your profile picture in the top right corner, and select **Profile Settings.** In the sidebar on the right, locate the **View API key** button, click on it to access the API key, and complete the captcha verification when prompted. Copy the provided API key and paste it to authenticate your Getint integration.
3. **How to Establish a Connection with Freshdesk:** Ensure you’re logged in as a user with the correct permissions. Click **Select App** and choose **Freshdesk.** Select **Create New** to establish a new connection with your Freshdesk instance. Name your connection and add the **URL** of your Freshdesk instance. Provide your login credentials to connect with Getint.
4. **Choose and Connect the Second App:** Select and link another tool to integrate with Freshdesk—options include another Freshdesk instance, ServiceNow, Jira, or any other supported tool.
5. **Mapping Types and Fields:** Link **Freshdesk types** (Incidents) to synchronize with other tools. You can use the **Quick Build** feature, which allows you to map available fields automatically or set them manually.
Getint’s support team is committed to ensuring a smooth and efficient integration experience tailored to your unique needs. If you encounter any challenges during setup or require assistance with missing functionalities, our dedicated support team is here to help.
### Supported Fields for Freshdesk Integrations
Getint allows you to map fields between different platforms, and here's a list of our currently supported fields for Freshdesk integrations:
{% hint style="info" %}
#### **How Field Mappings Work:**
**One-Way Mapping:**
* When you update fields in one of the synchronized apps, those changes will appear in the other app. However, updates made in the other app won’t impact the first app because the fields are read-only.
**Two-Way Mapping:**
* Updates to synchronized fields will be reflected in both apps. If you modify a field in one app, the change will automatically sync to the other app as well.
**Tip:** While it’s technically not possible to directly modify read-only fields, we provide a solution for achieving bidirectional integration or migrating these fields using custom fields. Setting up this solution requires specific steps, but it is indeed feasible. You can find more detailed information in this [article.](https://docs.getint.io/getting-started-with-the-platform/prepare-for-integration/understanding-the-difference-between-platforms-you-integrate)
{% endhint %}
| **Freshdesk Field** | **One Way** | **Both Ways** |
| ------------------------------------------------------------------------------------------------ | ----------- | ------------- |
| Agent | ✔️ | ✔️ |
| Comments & Attachments | ✔️ | ✔️ |
|
Custom fields
Date - Dependent field - Dropdown - Single line text
| ✔️ | ✔️ |
| Description | ✔️ | ✔️ |
| Group | ✔️ | ✔️ |
| Id | ✔️ | |
| Priority | ✔️ | ✔️ |
| Requester | ✔️ | ✔️ |
| Status | ✔️ | ✔️ |
| Source | ✔️ | ✔️ |
| Subject | ✔️ | ✔️ |
| Type | ✔️ | ✔️ |
| URL | ✔️ | |
{% hint style="warning" %}
**Important Note:**\
We strive to maintain the accuracy of this list, but please be aware that supported fields may vary in the original product.
{% endhint %}
### Limitations to Keep in Mind
At Getint, we continuously update our supported features, fields, and compatible apps. However, there are a few important limitations to keep in mind:
* To ensure your integration functions correctly, you must map the following mandatory fields: Requester, Status (mapped with a fixed value “Open” for newly created tickets), and Priority. For detailed instructions on mapping these fields with platforms like Jira, please refer to the guide available [here.](https://docs.getint.io/guides/integration-synchronization/jira-freshdesk#field-mapping)
* Comments added to the issue will display under the user account you select when creating the connection. For a seamless integration, we recommend creating a dedicated Service Account. Although the original author’s name will appear in the comment footer, the comment will still be linked to the account that established the connection.
* Unfortunately, integrating the history of changes is not possible due to the technical limitations of Jira / Freshdesk APIs.
### Case Studies and Support Contact
Our Support Team at Getint is eager to assist with your integration and migration needs and answer any other questions you may have. If you're seeking assistance or a deeper understanding of our solution, we invite you to schedule a demo call [here](https://www.getint.io/schedule-demo-call).
#### Case Studies
Large and small businesses have experienced the benefits of using Getint for data integration. This has provided them with various solutions tailored to their teams and organizations. We invite you to explore some of our [Case Studies](https://www.getint.io/case-studies), which are true accounts of how Getint continually enhances and improves the tool integration process.
{% hint style="info" %}
**Are you looking for a specific solution that we don’t currently support?** Please get in touch with our [support team](https://getint.io/help-center), and we can assist you in developing a customized solution for your particular case.
{% endhint %}
# Freshservice
## Getint: Connecting Freshservice and Synchronizing Data Across Platforms
Getint makes it easier to connect Freshservice with other tools and keep data aligned. It supports a wide range of setups, including Freshservice-Jira, Freshservice-Asana, Freshservice-Monday, Freshservice-Azure DevOps, and more. Whether you’re using a SaaS or On-Premise version, Getint offers flexible options to support different business needs.
### What’s Inside:
* [How to Set Up the App](#setting-up-getint-with-freshservice)
* [Supported Fields for Freshservice Connections](#supported-fields-for-freshservice-integrations)
* [Key Limitations and Setup Notes](#things-to-keep-in-mind)
* [Case Studies and How to Reach Support](#case-studies-and-support)
Getint helps teams keep data consistent across platforms and environments. With support for Freshservice, users can track and manage work across systems without losing visibility or control.
### Setting Up Getint with Freshservice
Connecting Freshservice to other tools through Getint is straightforward. You can sync data or run a one-time migration. The process includes mapping issue types (e.g., Task → Incident) and fields (e.g., Description → Description). If you need help during setup, our support team is available to guide you.
#### Helpful Resources:
* [Quickstart Guides](https://docs.getint.io/guides/quickstart)
* [Integration Instructions](https://docs.getint.io/guides/integration-synchronization/jira-freshservice-integration)
* [Migration Steps](https://docs.getint.io/guides/migration)
* [Workflow Overview](https://docs.getint.io/getintio-platform/workflows)
#### Freshservice Integration: Step-by-Step
Here’s a quick look at how to connect Freshservice with other platforms:
1. **Access Getint**: If you're using Jira, go to the Apps section and install Getint from the [Atlassian Marketplace](https://marketplace.atlassian.com/apps/1227929/freshservice-freshdesk-integration-for-jira-2-way-work-sync?hosting=cloud\&tab=overview). For other platforms, choose either Getint SaaS or On-Premise, depending on your setup.
2. **Generate Your Freshservice API Token**: Log in to [Freshservice](https://docs.getint.io/guides/quickstart/connection#freshservice), click your profile icon in the top-right corner, and go to Profile Settings. On the right sidebar, click "View API Key," complete the captcha, and copy the key. You'll use this to connect Freshservice to Getint.
3. **Create the Connection**: Make sure you’re logged in with the right permissions. In Getint, click "Select App" and choose Freshservice. Then click "Create New" to start a new connection. Add your Freshservice URL, enter your credentials, and save the connection.
4. **Link a Second Tool**: Choose another platform to connect with Freshservice—this could be another Freshservice instance, Jira, ServiceNow, or any other supported tool.
5. **Map Types and Fields**: Use Getint's Quick Build feature to automatically map Freshservice fields, or configure them manually. You can link incident types and sync fields like status, priority, and description.
If you run into any issues or need help with setup, our support team is ready to assist.
### Supported Fields for Freshservice Integrations
Getint lets you map fields between Freshservice and other platforms. Here’s how it works:
#### Field Mapping Options:
* **One-Way Mapping**: Changes made in one app appear in the other, but not the reverse.
* **Two-Way Mapping**: Updates are reflected in both apps automatically.
{% hint style="info" %}
Tip: Read-only fields can’t be edited directly, but Getint offers a way to sync or migrate them using custom fields. Setup steps are available in our guides.
{% endhint %}
| **Freshservice Field** | **One Way** | **Both Ways** |
| ------------------------------------------------------------------------------ | ----------- | ------------- |
| Assigned to | ✔️ | ✔️ |
| Category | ✔️ | ✔️ |
| Comments & Attachments | ✔️ | ✔️ |
|
Custom fields
Date - Dropdown - Single line text
| ✔️ | ✔️ |
| Department | ✔️ | ✔️ |
| Description | ✔️ | ✔️ |
| Group | ✔️ | ✔️ |
| Id | ✔️ | |
| Item | ✔️ | ✔️ |
| Priority | ✔️ | ✔️ |
| Requester | ✔️ | ✔️ |
| Status | ✔️ | ✔️ |
| Source | ✔️ | ✔️ |
| Status | ✔️ | ✔️ |
| Subject | ✔️ | ✔️ |
| Sub-category | ✔️ | ✔️ |
| Time Tracking - Original Estimate | ✔️ | ✔️ |
| Time tracking date field | ✔️ | ✔️ |
| Type | ✔️ | ✔️ |
| URL | ✔️ | |
{% hint style="warning" %}
**Important Note:**\
We strive to maintain the accuracy of this list, but please be aware that supported fields may vary in the original product.
{% endhint %}
### Things to Keep in Mind
While Getint supports many features, here are a few important notes:
* **Required Fields**: You must map Requester, Status (set to "Open" for new tickets), and Priority for the integration to work properly. More information about field mappings [here](https://docs.getint.io/guides/integration-synchronization/jira-freshservice-integration#id-7.-field-mapping).
* **Comment Attribution**: Comments will appear under the account selected during setup. For best results, we recommend using a dedicated Service Account. The original author's name will still show in the comment footer.
* **Change History**: Syncing historical changes isn't supported due to API limitations in Jira and Freshservice.
### Case Studies and Support
Our team is here to help you get started, troubleshoot issues, and answer any questions. If you're seeking assistance or a deeper understanding of our solution, we invite you to schedule a demo call [here](https://www.getint.io/schedule-demo-call).
#### Real-World Examples
Companies of all sizes use Getint to connect their tools and manage data more effectively. Check out our [Case Studies](https://www.getint.io/case-studies) to see how others have used Getint in different environments.
{% hint style="info" %}
**Need something specific that's not currently supported?**
Please contact our [support team](https://getint.io/help-center), and we will assist you in developing a customized solution to your specific needs.
{% endhint %}
# GitHub
## Getint: Simplifying GitHub Integration and Data Synchronization
Getint facilitates seamless integration between multiple platforms, enabling synchronization across tools like GitHub, Jira, Asana, and Azure DevOps. It supports both SaaS and On-Premise deployment, offering adaptability to suit diverse business requirements.
### Key Topics Covered:
* [Installing and Configuring the Application](#installing-and-configuring-getint-for-github)
* [Supported GitHub Fields](#supported-github-fields)
* [Key Considerations](#key-considerations)
* [Contacting Support - Case Studies](#contacting-our-support-team)
By synchronizing data across instances and platforms, Getint empowers users to efficiently track and manage tasks while integrating GitHub with other project management tools.
### Installing and Configuring Getint for GitHub
Getint simplifies connecting and migrating data between systems. Below are the steps to get started:
**Step 1: Access Getint**
* **Want to integrate Jira with GitHub?** Just download the app from the Atlassian Marketplace. It's quick and easy! You can find it here: [GitHub Integration for Jira.](https://marketplace.atlassian.com/apps/1223933/github-integration-for-jira-github-connector?hosting=cloud\&tab=overview)
* Other tools: Select between [Getint On-Premise or SaaS options.](https://app.getint.io/app/auth/sign-up)
**Step 2: Set Up a Connection with GitHub**
* Ensure you have the correct access permissions. Here you will find all the steps to generate an access token in GitHub: [Generating a GitHub Token.](https://docs.getint.io/guides/quickstart/connection#github)
* Choose GitHub as the app, create a new connection, and enter your GitHub access token.
**Step 3: Connect to Another Tool**
* Choose the platform you want to integrate with GitHub, such as Jira.
**Step 4: Map Types and Fields**
* Match GitHub issue types, such as Tasks, with their equivalents in the other tool.
* Leverage the Quick Build feature for automatic mapping, or adjust mappings manually to fit your needs.
If you need help with setup or run into any challenges, our support team is always here to assist.
For additional guidance on using Getint with GitHub, refer to:
* [Quickstart Guides](https://docs.getint.io/guides/quickstart)
* [Jira GitHub Integration Guide](https://docs.getint.io/guides/integration-synchronization/jira-github-integration)
* [Migration Guides](https://docs.getint.io/guides/migration)
### Setting Up a Git Repository Integration
#### **Configuration Steps**
1. **Create a Git Connector Integration**: Navigate to the Getint dashboard and select Git Connector. Choose GitHub as your app.
2. **Authenticate with GitHub**: Generate an [access token](https://docs.getint.io/guides/quickstart/connection#github). Grant access to the repositories you want to sync.
3. **Set up OAuth for Jira**: Unlike Continuous Syncs or data Migrations, Git integrations need OAuth setup directly within your Jira environment. Follow the steps outlined in our guide: [Connection | Jira OAuth.](https://docs.getint.io/guides/quickstart/connection#jira-cloud-oauth)
4. **Select Repositories**: Choose one or more GitHub repositories to link with Getint. You can sync issues, pull requests, and commits.
5. **Test & Activate**: Run a test sync to verify everything works as expected. Once confirmed, activate the integration.
6. **Sync Your Branches**: Use the correct prefixes outlined in our [Git Integration](https://docs.getint.io/guides/integration-synchronization/git-integrations/git-connector-github#id-5.-test-the-integration-and-sync-your-branches) article to sync the branches, commits, and pull requests.
{% hint style="info" %}
All the installation steps to connect your Git Repository with Jira are located in our dedicated article: [Git Connector - GitHub](https://docs.getint.io/guides/integration-synchronization/git-integrations/git-connector-github).
{% endhint %}
### Supported GitHub Fields
Getint allows you to map fields between different platforms, and here's a list of our currently supported:
{% hint style="info" %}
#### **How Field Mappings Work:**
**One-Way Mapping:**
* When you update fields in one of the synced apps, those changes will appear in the other app. However, updates made in the other app won’t affect the first app because the fields are read-only.
**Two-Way Mapping:**
* Updates to synced fields will be reflected in both apps. If you modify a field in one app, the change will automatically sync to the other app as well.
**Tip:**
While technically it's not possible to directly modify read-only fields, we offer a solution to achieve bidirectional integration or migrate these fields using custom fields. Setting up this solution requires specific steps, but it is indeed possible. You can find more detailed information in this [article.](https://docs.getint.io/getting-started-with-the-platform/prepare-for-integration/understanding-the-difference-between-platforms-you-integrate)
{% endhint %}
| **GitHub Field** | **One Way** | **Both Ways** |
| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Assignee | ✔️ | ✔️ |
| Author | ✔️ | |
| Comments | ✔️ | ✔️ |
| Description | ✔️ | ✔️ |
| ID | ✔️ | |
| Labels | | |
| Title | ✔️ | ✔️ |
{% hint style="warning" %}
**Important Note:** While we make every effort to ensure the accuracy of this list, please be aware that supported fields may differ in the original product.
{% endhint %}
### Key Considerations
At Getint, we are committed to continuously updating our supported features, fields, and compatible apps. However, please keep the following key points in mind:
* **Attachments**: You can sync attachments from GitHub to Jira by providing S3 credentials.
* **Change History**: Getint cannot integrate the history of changes.
* **Comments**: Comments added by Getint will appear under the user account you choose during connection setup. Consider creating a dedicated Service Account for integration to maintain consistency. The original author’s name will appear in the comment footer, but the comment will be assigned to the connecting account. Also, comments and attachments transferred from GitHub to Jira will be set to public or private (they will be public by default). You can configure Jira to mark all comments from GitHub as private automatically. However, enabling both public and private visibility options is impossible.
* **Custom fields**: Currently, there's no support for custom fields.
* **Inline** **images** aren't supported.
* **Labels** aren't supported.
### Contacting Our Support Team
Our dedicated Support Team is here to assist with your integration and migration needs. Whether you have questions or seek deeper insights into our solution, you’re welcome to schedule a [demo call](https://www.getint.io/schedule-demo-call) with us.
#### Case Studies
Discover how Getint enhances tool integration for businesses of all sizes. Our [Case Studies](https://www.getint.io/case-studies) highlight real-world solutions designed to empower teams and organizations.
{% hint style="info" %}
**Looking for a solution we don’t currently support?** Reach out to our [support team](https://getint.io/help-center); we’d be happy to help you explore a customized solution tailored to your needs.
{% endhint %}
# GitLab
## Getint: Simplifying GitLab Integration and Data Synchronization
**Getint** is designed to connect and synchronize various tools, supporting integrations such as GitLab with Jira, Asana, or Azure DevOps. It offers both SaaS and On-Premise solutions, providing flexibility for different business needs.
### Key Topics Covered:
* [Setting Up the App](#how-to-set-up-getint-for-gitlab)
* [Supported Fields in GitLab](#supported-fields-for-gitlab-integration)
* [Supported Item Types](#supported-fields-for-gitlab-integration)
* [Limitations and Considerations](#limitations-and-considerations)
* [Contacting Support - Case Studies](#contacting-our-support-team)
Getint helps synchronize data across platforms or instances, including GitLab. It enables users to monitor and manage tasks or activities across projects and integrate GitLab with other tools.
### How to Set Up Getint for GitLab
Getint simplifies connecting and migrating data between systems. Below are the steps to get started:
**Step 1: Access Getint**
* **Want to integrate Jira with GitLab?** Just download the app from the Atlassian Marketplace. It's quick and easy! You can find it here: [GitLab Integration for Jira.](https://marketplace.atlassian.com/apps/1223999/gitlab-integration-for-jira-gitlab-connector-2-way-sync?hosting=cloud\&tab=overview)
* Other tools: Select between Getint On-Premise or SaaS options.
**Step 2: Set Up a Connection with GitLab**
* Ensure you have the correct access permissions. Here you will find all the steps to generate an access token in GitLab: [Generating a GitLab Token.](https://docs.getint.io/guides/quickstart/connection#gitlab)
* Choose GitLab as the app, create a new connection, and enter your GitLab access token.
**Step 3: Connect to Another Tool**
* Choose the platform you want to integrate with GitLab, such as Jira.
**Step 4: Map Types and Fields**
* Match GitLab issue types, such as Incidents, with their equivalents in the other tool.
* Leverage the Quick Build feature for automatic mapping, or adjust mappings manually to fit your needs.
If you need help with setup or run into any challenges, our support team is always here to assist.
For additional guidance on using Getint with GitLab, refer to:
* [Quickstart Guides](https://docs.getint.io/guides/quickstart)
* [Jira GitLab Integration Guide](https://docs.getint.io/guides/integration-synchronization/jira-gitlab)
* [Migration Guides](https://docs.getint.io/guides/migration)
### Supported Fields for GitLab Integration
Getint allows you to map fields between different platforms, and here's a list of our currently supported:
{% hint style="info" %}
#### **How Field Mappings Work:**
**One-Way Mapping:**
* When you update fields in one of the synced apps, those changes will appear in the other app. However, updates made in the other app won’t affect the first app because the fields are read-only.
**Two-Way Mapping:**
* Updates to synced fields will be reflected in both apps. If you modify a field in one app, the change will automatically sync to the other app as well.
**Tip:**
While technically it's not possible to directly modify read-only fields, we offer a solution to achieve bidirectional integration or migrate these fields using custom fields. Setting up this solution requires specific steps, but it is indeed possible. You can find more detailed information in this [article.](https://docs.getint.io/getting-started-with-the-platform/prepare-for-integration/understanding-the-difference-between-platforms-you-integrate)
{% endhint %}
| **GitLab Field** | **One Way** | **Both Ways** |
| ----------------- | ----------- | ------------- |
| Assignee | ✔️ | ✔️ |
| Attachments | ✔️ | |
| Author Name | ✔️ | |
| Closed At | ✔️ | |
| Comments | ✔️ | ✔️ |
| Confidential | ✔️ | |
| Created At | ✔️ | |
| Discussion Locked | ✔️ | |
| Due date | ✔️ | ✔️️ |
| Epic Id | ✔️ | |
| Epic Name | ✔️ | |
| ID | ✔️ | |
| Labels | ✔️ | ✔️ |
| Milestone Name | ✔️ | |
| Reporter | ✔️ | |
| Status | ✔️ | ✔️ |
| Time Estimate | ✔️ | |
| Time Spent | ✔️ | |
| Title | ✔️ | |
| Updated At | ✔️ | |
| URL | ✔️ | |
| Weight | ✔️ | |
{% hint style="warning" %}
**Important Note:** While we make every effort to ensure the accuracy of this list, please be aware that supported fields may differ in the original product.
{% endhint %}
### Limitations and Considerations
At Getint, we are committed to continuously updating our supported features, fields, and compatible apps. However, please keep the following key points in mind:
* **Attachments**: You can sync attachments from GitLab to Jira with a cookie header. These attachments will always sync one way from GitLab to the counterpart tool. More information about this option here: [Attachments Sync in GitLab Integration.](https://docs.getint.io/guides/integration-synchronization/jira-gitlab/attachments-sync-in-gitlab-integration)
* **Change History**: Getint cannot integrate the history of changes.
* **Comments**: Comments added by Getint will appear under the user account you choose during connection setup. Consider creating a dedicated Service Account for integration to maintain consistency. The original author’s name will appear in the comment footer, but the comment will be assigned to the connecting account. Also, comments and attachments transferred from GitLab to Jira will be set to public or private (they will be public by default). You can configure Jira to mark all comments from GitLab as private automatically. However, enabling both public and private visibility options is impossible.
* **Custom fields**: Currently, GitLab has no support for custom fields.
* **Inline** **images** aren’t supported.
* **Issue Types**: When Getint creates a new issue in GitLab, it will always be one specific type (i.e., Issue, or Incident). You can set the default item type using a rule or manually adjust it in GitLab after creation.
### Contacting Our Support Team
Our dedicated Support Team is here to assist with your integration and migration needs. Whether you have questions or seek deeper insights into our solution, you’re welcome to schedule a [demo call](https://www.getint.io/schedule-demo-call) with us.
#### Case Studies
Discover how Getint enhances tool integration for businesses of all sizes. Our [Case Studies](https://www.getint.io/case-studies) highlight real-world solutions designed to empower teams and organizations.
{% hint style="info" %}
**Looking for a solution we don’t currently support?** Reach out to our [support team](https://getint.io/help-center)—we’d be happy to help you explore a customized solution tailored to your needs.
{% endhint %}
# HubSpot
## Getint: Simplifying HubSpot Integration and Data Synchronization
**Getint** is designed to connect and synchronize various tools, supporting integrations such as HubSpot with Jira, Asana, or Azure DevOps. We offer SaaS and On-Premise solutions, providing flexibility for different business needs.
### Key Topics Covered:
* [Setting Up the App](#how-to-set-up-getint-for-hubspot)
* [Supported Fields in HubSpot](#supported-fields-for-hubspot-integration)
* [Supported Item Types](#supported-item-types-for-hubspot-integration)
* [Limitations and Considerations](#limitations-and-considerations)
* [Contacting Support - Case Studies](#contacting-our-support-team)
Getint helps synchronize data across platforms or instances, including HubSpot. It enables users to monitor and manage tasks or activities across projects and integrate HubSpot with other tools.
### How to Set Up Getint for HubSpot
Getint simplifies connecting and migrating data between systems. Below are the steps to get started:
**Step 1: Access Getint**
* For Jira users: If you want to integrate Jira with HubSpot, download the app from the [Atlassian Marketplace](https://marketplace.atlassian.com/apps/1231637/hubspot-integration-for-jira-bi-directional-issue-sync?hosting=cloud\&tab=overview).
* For other tools: Select between Getint On-Premise or SaaS options.
**Step 2: Set Up a Connection with HubSpot**
* Ensure you have the correct [access permissions](https://docs.getint.io/guides/quickstart/connection#hubspot).
* Choose HubSpot as the app, create a new connection, and enter your HubSpot credentials.
**Step 3: Connect to Another Tool**
* Pick the platform you want to integrate with HubSpot, such as Jira.
**Step 4: Map Types and Fields**
* Match HubSpot categories like Contacts or Deals with their counterparts in the other tool.
* Use the "Quick Build" feature for automatic mapping or customize mappings manually if needed.
Our support team is always available to assist with any setup or operational challenges.
For additional guidance on using Getint with HubSpot, refer to:
* [Quickstart Guides](https://docs.getint.io/guides/quickstart)
* [Jira HubSpot Integration Guide](https://docs.getint.io/guides/integration-synchronization/jira-hubspot-integration)
* [Migration Guides](https://docs.getint.io/guides/migration)
### Supported Fields for HubSpot Integration
Getint allows you to map fields between different platforms, and here's a list of our currently supported:
{% hint style="info" %}
#### **How Field Mappings Work:**
**One-Way Mapping:**
* When you update fields in one of the synced apps, those changes will appear in the other app. However, updates made in the other app won’t affect the first app because the fields are read-only.
**Two-Way Mapping:**
* Updates to synced fields will be reflected in both apps. If you modify a field in one app, the change will automatically sync to the other app as well.
**Tip:**
While technically it's not possible to directly modify read-only fields, we offer a solution to achieve bidirectional integration or migrate these fields using custom fields. Setting up this solution requires specific steps, but it is indeed possible. You can find more detailed information in this [article.](https://docs.getint.io/getting-started-with-the-platform/prepare-for-integration/understanding-the-difference-between-platforms-you-integrate)
{% endhint %}
| **HubSpot Field** | **One Way** | **Both Ways** |
| --------------------------------------------------------------- | ----------- | ------------- |
| All associated contact companies | ✔️ | |
| All associated contact emails | ✔️ | |
| All associated contact first names | ✔️ | |
| All associated contact last names | ✔️ | |
| All associated contact mobile phones | ✔️ | |
| All associated contact phones | ✔️ | |
| All conversation mentions | ✔️ | |
| All Owner IDs | ✔️ | |
| All Team IDs | ✔️ | |
| All teams | ✔️ | |
| Amount | ✔️ | ✔️ |
| Amount in company currency | ✔️ | |
| Annual contract value | ✔️ | |
| Annual recurring revenue | ✔️ | |
| Applied SLA | ✔️ | ✔️ |
| Assigned Teams | ✔️ | |
| Assigned To (Assignees) | ✔️ | ✔️ |
| Assignment Method | ✔️ | ✔️ |
| Associated Shared Deal Product Interests | ✔️ | |
| Associated Shared Deal Type | ✔️ | |
| Attributed reporting team | ✔️ | ✔️ |
| Auto-generated from thread id | ✔️ | |
| Average ticket sentiment | ✔️ | |
| Average ticket sentiment score | ✔️ | |
| Business units | ✔️ | ✔️ |
| Campaign of last booking in meetings tool | ✔️ | |
| Category | ✔️ | |
| Close date | ✔️ | ✔️ |
| Closed Deal Amount | ✔️ | |
| Closed deal amount in home currency | ✔️ | |
| Closed Deal Close Date | ✔️ | |
| Closed Deal Create Date | ✔️ | |
| Closed Deal Lost Reason | ✔️ | ✔️ |
| Closed won count | ✔️ | |
| Closed Won Date (Internal) | ✔️ | |
| Closed Won Reason | ✔️ | ✔️ |
| Companies | ✔️ | ✔️ |
| Comments & Attachments | ✔️ | ✔️ |
| Contacts | ✔️ | ✔️ |
| Conversation NPS score | ✔️ | |
| Conversations originating thread id | ✔️ | |
| Copied at | ✔️ | |
| Copied by user | ✔️ | |
| Copied ticket | ✔️ | |
| Copied ticket source | ✔️ | |
| Create Date | ✔️ | ✔️ |
| Created by | ✔️ | ✔️ |
| Created by user ID | ✔️ | |
| Cumulative time in | ✔️ | |
| Currency | ✔️ | ✔️ |
| Custom fields | ✔️ | ✔️ |
| Custom inbox ID | ✔️ | ✔️ |
| Customer Agent ticket status | ✔️ | |
| Date entered | ✔️ | |
| Date entered current stage | ✔️ | |
| Date exited | ✔️ | |
| Date of last engagement | ✔️ | |
| Date of last meeting booked in meetings tool | ✔️ | |
| Days to close | ✔️ | |
| Days to close (without rounding) | ✔️ | |
| Draft UserIDs | ✔️ | |
| Deal amount calculation preference | ✔️ | ✔️ |
| Deal Collaborator | ✔️ | ✔️ |
| Deal Description | ✔️ | ✔️ |
| Deal Name | ✔️ | ✔️ |
| Deal owner | ✔️ | ✔️ |
| Deal probability | ✔️ | ✔️ |
| Deal Score | ✔️ | |
| Deal Split Users | ✔️ | |
| Deal Stage | ✔️ | ✔️ |
| Deal stage probability shadow | ✔️ | |
| Deal Tags | ✔️ | |
| Deal Type | ✔️ | ✔️ |
| Email Subject | ✔️ | |
| External object ids | ✔️ | |
| Exchange rate | ✔️ | ✔️ |
| File upload | ✔️ | ✔️ |
| First agent email response date | ✔️ | |
| First agent response date | ✔️ | |
| First message sentiment | ✔️ | |
| First message sentiment score | ✔️ | |
| Forecast amount | ✔️ | |
| Forcast category | ✔️ | ✔️ |
| Forecast probability | ✔️ | ✔️ |
| Form | ✔️ | |
| Form submission conversion ID | ✔️ | |
| Global Term Line Item Discount Percentage | ✔️ | ✔️ |
| Global Term Line Item Recurring Frequency | ✔️ | ✔️ |
| Global Term Line Item Recurring Billing Period | ✔️ | ✔️ |
| Global Term Line Item Recurring Billing Start | ✔️ | |
| Help Desk onboarding ticket | ✔️ | |
| Helpdesk Sort Timestamp | ✔️ | |
| HubSpot Campaign | ✔️ | ✔️ |
| HubSpot Create Date | ✔️ | ✔️ |
| HubSpot Sales Lead | ✔️ | |
| HubSpot Shared Deal MRR | ✔️ | |
| HubSpot Shared Deal MRR Currency Code | ✔️ | |
| HubSpot Team | ✔️ | |
| ID | ✔️ | |
| Inbox ID | ✔️ | |
| Is Closed (numeric) | ✔️ | |
| Is Open (numeric) | ✔️ | |
| Item Type | ✔️ | |
| Language | ✔️ | ✔️ |
| Last Activity Date | ✔️ | |
| Last Activity Date (Ticket Note) | ✔️ | |
| Last Contacted | ✔️ | |
| Last CES | ✔️ | |
| Last customer reply date | ✔️ | |
| Last email activity | ✔️ | |
| Last email date | ✔️ | |
| Last email ID | ✔️ | |
| Last email type | ✔️ | |
| Last Modified Date | ✔️ | |
| Last Response Date | ✔️ | |
| Latest Approval Status | ✔️ | |
| Latest Approval Status ID | ✔️ | |
| Latest Meeting Activity | ✔️ | |
| Latest message | ✔️ | |
| Latest time in | ✔️ | |
| Latest Traffic Source | ✔️ | |
| Likelihood to close by the close date | ✔️ | |
| Medium of last booking in meetings tool | ✔️ | |
| Merged Deal IDs | ✔️ | |
| Merged Ticket IDs | ✔️ | |
| mentioned\_note\_user\_IDs | ✔️ | |
| mentions\_user\_IDs | ✔️ | |
| Microsoft Teams message ID for this ticket. | ✔️ | |
| Monthly recurring revenue | ✔️ | |
| Most relevant SLA status | ✔️ | ✔️ |
| Most Relevant SLA Type | ✔️ | ✔️ |
| Next Pipeline Impact | ✔️ | ✔️ |
| Next Activity Date | ✔️ | |
| Next Activity Type | ✔️ | |
| Next Meeting ID | ✔️ | |
| Next Meeting Name | ✔️ | |
| Next Meeting Start Time | ✔️ | |
| Next step | ✔️ | ✔️ |
| Next Step Updated At | ✔️ | |
| Number of Active Deal Registrations | ✔️ | |
| Number of Associated Contacts | ✔️ | |
| Number of Associated Line Items | ✔️ | |
| Number of Deal Splits | ✔️ | |
| Number of Sales Activities | ✔️ | |
| Number of target accounts | ✔️ | |
| Number of times contacted | ✔️ | |
| Object Type | ✔️ | |
| Open deal create date | ✔️ | |
| Original Traffic Source | ✔️ | ✔️ |
| Original Traffic Source Drill-Down 1 | ✔️ | |
| Original Traffic Source Drill-Down 2 | ✔️ | |
| Owner assigned date | ✔️ | |
| Owning Teams | ✔️ | ✔️ |
| Pinned Engagement ID | ✔️ | ✔️ |
| Pipeline | ✔️ | ✔️ |
| Primary Company ID | ✔️ | |
| Primary Company Name | | |
| Priority | ✔️ | ✔️ |
| Recent Sales Email Replied Date | ✔️ | |
| Record creation source | ✔️ | |
| Record creation source ID | ✔️ | |
| Record creation source user ID | ✔️ | |
| Record ID | ✔️ | |
| Record source | ✔️ | |
| Record source detail 1 | ✔️ | |
| Record source detail 2 | ✔️ | |
| Record source detail 3 | ✔️ | |
| Shared teams | ✔️ | ✔️ |
| Shared users | ✔️ | |
| Source Object ID | ✔️ | |
| Source of last booking in meetings tool | ✔️ | |
| Status transition | ✔️ | ✔️ |
| Task Type | ✔️ | ✔️ |
| Tasks completed | ✔️ | |
| Task Title | ✔️ | ✔️ |
| The predicted deal amount | ✔️ | |
|
The predicted deal amount in your company's currency
| ✔️ | |
| Time in | ✔️ | |
| Time to | ✔️ | |
| Total contract value | ✔️ | |
| Unique creation Key | ✔️ | |
| Updated by user ID | ✔️ | |
| URL | ✔️ | |
| User IDs of all notification followers | ✔️ | |
| User IDs of all notification unfollowers | ✔️ | |
| User IDs of all owners | ✔️ | |
| Users Interaction | ✔️ | |
| Weighted amount | ✔️ | |
| Weighted amount in company currency | ✔️ | |
{% hint style="warning" %}
**Important Note:**\
We strive to maintain the accuracy of this list, but please be aware that supported fields may vary in the original product.
{% endhint %}
### Supported Item Types for HubSpot Integration
| Company |
| --------- |
| Contact |
| Deal |
| Line Item |
| Quote |
| Task |
| Ticket |
### Limitations and Considerations
At Getint, we continuously update our supported features, fields, and compatible apps. However, there are a few important points to consider:
* **Issue Types:** When Getint creates a new issue in HubSpot, it will always be one specific type (i.e., Task, Deal, or Ticket). You can set the default item type using a rule or manually adjust it in HubSpot after creation.
* **Comments:** Comments added by Getint will appear under the user account you choose during connection setup. Consider creating a dedicated Service Account for integration to maintain consistency. The original author’s name will appear in the comment footer, but the comment will be assigned to the connecting account.
Comments and attachments transferred from HubSpot to Jira will be set to either public or private. You can configure Jira to mark all comments from HubSpot as private automatically. However, it is impossible to enable both public and private visibility options simultaneously.
* **Change History:** Unfortunately, Getint cannot integrate the history of changes.
* **Inline** **images** aren't supported for the Description field.
### Contacting Our Support Team
Our dedicated Support Team is ready to assist with your integration and migration needs. If you have questions or need deeper insights into our solution, feel free to schedule a [demo call](https://www.getint.io/schedule-demo-call) with us.
#### Case Studies
Explore real-world examples of how Getint enhances tool integration for businesses of all sizes. Our [Case Studies](https://www.getint.io/case-studies) showcase tailored solutions that empower teams and organizations.
{% hint style="info" %}
**Are you looking for a specific solution that we don’t currently support?** Please get in touch with our [support team](https://getint.io/help-center), and we can assist you in developing a customized solution for your particular case.
{% endhint %}
# Jira
## Getint: Simplifying Jira Integration and Data Synchronization
Getint is expertly designed to integrate and synchronize an extensive range of tools. It accommodates a variety of connectivity scenarios, such as Jira - Jira, Jira - Azure DevOps, Jira - Asana, Jira - ServiceNow, and more. With its availability as both a Software-as-a-Service (SaaS) and On-Premise solution, Getint offers the versatility to meet the unique requirements of various businesses.
### What does this article cover?
* [How to Set Up the App](#setting-up-getint-for-jira)
* [Supported Fields in Jira](#supported-fields-in-jira)
* [Limitations and Considerations to Make](#limitations-to-be-considered)
* [Contacting Our Support Team - Case Studies](#contacting-our-support-team)
Getint enables seamless data synchronization within the same platform or different platforms/different instances. It supports Jira and Jira Service Management of all types (Cloud, Server, Data Center), and across different projects. Allowing users to efficiently track and manage Jira tickets, tasks, bugs, and epics in diverse Jira environments, as well as integrating Jira with other platforms.
### Setting up Getint for Jira
Getint simplifies data integration and migration. With easy setup steps, you can connect your systems, such as Jira, map types (i.e., Task - Task), and fields (i.e., Priority - Priority). Whether you're looking to sync data continuously or perform a one-time migration, Getint has got you covered. Our dedicated support team is always ready to assist you with any challenges you may encounter during setup or operation.
For more detailed guides on how to set up your Jira integration, please make sure to check the following:
* [Starting with Getint - Quickstart Guides](https://docs.getint.io/guides/quickstart)
* [Integration Guides](https://docs.getint.io/guides/integration-synchronization)
* [Migration Guides](https://docs.getint.io/guides/migration)
* [Understanding Getint - Workflows](https://docs.getint.io/getintio-platform/workflows)
Here's a simplified version of how to integrate Jira with other tools (you can find a detailed overview [**here**](https://docs.getint.io/guides/integration-synchronization/jira-jira-integration)):
1. **Access the Getint App in Jira:** The app is available for download in the Atlassian Marketplace. After the installation, navigate to Jira, go to "Apps," and select "the Getint app." Select "Create Integration" then "Continuous Sync" or "Migration" based on your requirements.
2. **Token Generation for Jira Cloud:** Visit Atlassian Account Settings. Go to Security, navigate to the API Token section, and generate a token. This token serves as the password for the Jira Cloud.
3. **Establish a Connection with Jira:** Ensure you're logged in as a user with the correct permissions. Click "Select App" and choose Jira. Select "Create New" to establish a new connection with your Jira instance. Name your connection, and add the URL of your Jira instance (without "/" at the end). Provide the login credentials.
4. **Choose and Connect the Second App:** Choose and connect another tool you'd like to integrate with your Jira—either another Jira instance, DevOps, ServiceNow, Salesforce, or any other tool that we support.
5. **Map Types and Fields:** Link Jira types (Task, Bug, Epic, Story) to synchronize with other tools. You can use the "Quick Build" feature, which allows you to map available fields automatically, or you can set them manually.
Getint's support team is committed to ensuring a smooth and efficient integration experience customized to your unique needs. If you encounter any challenges during setup or require assistance with missing functionalities, our dedicated support team is readily available to provide guidance and help.
### Supported Fields in Jira
Getint allows you to map fields between different platforms, and here's a list of our currently supported:
{% hint style="info" %}
#### **How Field Mappings Work:**
**One-Way Mapping:**
* When you update fields in one of the synced apps, those changes will appear in the other app. However, updates made in the other app won’t affect the first app because the fields are read-only.
**Two-Way Mapping:**
* Updates to synced fields will be reflected in both apps. If you modify a field in one app, the change will automatically sync to the other app as well.
**Tip:**
While technically it's not possible to directly modify read-only fields, we offer a solution to achieve bidirectional integration or migrate these fields using custom fields. Setting up this solution requires specific steps, but it is indeed possible. You can find more detailed information in this [article.](https://docs.getint.io/getting-started-with-the-platform/prepare-for-integration/understanding-the-difference-between-platforms-you-integrate)
{% endhint %}
Jira Field
One Way
Both Ways
Assignee
✔️
✔️
Attachments
✔️
✔️
Created
✔️
Comments
✔️
✔️
Custom fields
Short text - Paragraph - Date - Number - Time Stamp - Labels - Dropdown - Checkbox - People - Dependent dropdown - URL
✔️
✔️
Description
✔️
✔️
Design
✔️
✔️
Due date
✔️
✔️
Flagged
✔️
✔️
ID
✔️
Issue color
✔️
✔️
Issue key
✔️
Issue type name
✔️
Labels
✔️
✔️
Linked issues
✔️
✔️
Priority
✔️
✔️
Project key
✔️
Project name
✔️
Reporter
✔️
✔️
Reporter display name
✔️
Reporter email
✔️
Request type
✔️
✔️
Resolution
✔️
Resolved
✔️
✔️
Satisfaction
✔️
Sprint
✔️
Start date
✔️
✔️
Status
✔️
✔️
Story point estimate
✔️
✔️
Story points
✔️
✔️
Subtasks
✔️
✔️
Time tracking - Original estimate
✔️
✔️
Time tracking - Remaining estimate
✔️
Time tracking - Time spent
✔️
Title (Summary)
✔️
✔️
Updated
✔️
URL
✔️
{% hint style="danger" %}
**Important Note:**\
We strive to maintain the accuracy of this list, but please be aware that supported fields may vary in the original product.
{% endhint %}
### Limitations to be Considered
At Getint, we're constantly updating our supported features, fields, and compatible apps. However, there are a few limitations you should be aware of:
* When a new issue is created in Jira by Getint, it will always be one type of issue, whether that's a Task, an Epic, a Feature, or a Bug. You can set the default item type using a rule or manually change it in Jira after it's created.
* Comments will be added as the user you choose to create the connection. Therefore, it is advised to create a dedicated Service Account to build your integration. The original author will appear in the comment footer; however, it will still be assigned to the account that established the connection.
* The history of changes can't be integrated.
### Contacting Our Support Team
Our Support Team at Getint is eager to assist with your integration and migration needs and answer any other questions you may have. If you're seeking assistance or a deeper understanding of our solution, we invite you to schedule a call [here](https://www.getint.io/schedule-demo-call).
#### Case Studies
Large and small businesses have experienced the benefits of using Getint for their data integration needs. This has provided them with various solutions tailored to their teams and organizations. We invite you to explore some of our [Case Studies](https://www.getint.io/case-studies), which are true accounts of how Getint continually enhances and improves the tool integration process.
{% hint style="info" %}
**Are you looking for a specific solution that we don’t currently support?** Please get in touch with our [support team](https://getint.io/help-center), and we can assist you in developing a customized solution for your particular case.
{% endhint %}
# Monday.com
## Getint: Simplifying Monday.com Integration and Data Synchronization
Getint, a powerful integration solution, seamlessly connects and synchronizes various tools. It supports multiple connectivity scenarios, including Jira - Monday.com, Monday.com - Azure DevOps, Monday.com - Asana, and more. Whether you choose Software-as-a-Service (SaaS) or On-Premise deployment, Getint provides the flexibility to meet the distinct needs of different businesses.
### What does this article cover?
* [How to Set Up the App](#setting-up-getint-for-monday.com)
* [Supported Fields in Monday.com](#supported-fields-in-monday.com)
* [Limitations and Considerations to Make](#limitations-to-be-considered)
* [Contacting Our Support Team - Case Studies](#contacting-our-support-team)
**Getint** facilitates smooth data synchronization across various platforms and instances. It supports **Monday.com,** allowing users to monitor and manage tasks in diverse environments effectively. Additionally, it enables seamless integration with other platforms.
### Setting up Getint for Monday.com
Getint simplifies data integration and migration. You can connect your systems with easy setup steps, such as Monday.com, map types (i.e., Task - Item), and fields (i.e., Assignee - Responsable). Whether you're looking to sync data continuously or perform a one-time migration, Getint has got you covered. Our dedicated support team is always ready to assist you with any challenges you may encounter during setup or operation.
For more detailed guides on how to configure your Monday.com integration, please make sure to check the following:
* [Starting with Getint - Quickstart Guides](https://docs.getint.io/guides/quickstart)
* [Integration Guides](https://docs.getint.io/guides/integration-synchronization)
* [Migration Guides](https://docs.getint.io/guides/migration)
* [Understanding Getint - Workflows](https://docs.getint.io/getintio-platform/workflows)
Here's a simplified version of how to integrate Monday.com with other tools (you can find a detailed overview [**here**](https://docs.getint.io/guides/integration-synchronization/jira-monday.com-integration)):
1. **Access Getint:** Navigate through the [Atlassian Marketplace](https://marketplace.atlassian.com/apps/1225780/monday-com-integration-for-jira-monday-com-connector?hosting=cloud\&tab=overview) or go to your "Apps" section in Jira, and search for the "Getint Monday.com integration app." Alternatively, if you need to integrate Monday.com with a non-Jira application, consider choosing either [Getint On-Premise or Getint SaaS.](https://app.getint.io/)
2. **Token Generation for Monday.com:** There are two options to see your API token:
1. **Admin Tab:**
* Log in to your "Monday.com" account.
* Click your "avatar/profile picture" in the top right corner.
* Go to **Administration** > **Connections** > **API.**
* Copy your personal token.
2. **Developer Tab:**
* Log in to your "Monday.com" account.
* Click your profile picture in the top right corner.
* Visit "Developers" to open the Developer Center.
* Click **My Access Tokens** > **Show.**
* Copy your personal token.
3. **Establish a Connection with Monday.com:** Ensure you're logged in as a user with the correct permissions. Click "Select App" and choose "Monday.com." Select "Create New" to establish a new connection with your Monday.com instance. Name your connection, and add the URL of your Monday.com instance. Provide the login credentials.
4. **Choose and Connect the Second App:** You can select and link an additional tool to integrate with Monday.com. Options include another Monday.com instance, ServiceNow, Jira, or any other supported tool.
5. **Map Types and Fields:** Link "Monday.com types" (Items, SubItems) to synchronize with other tools. You can use the "Quick Build" feature, which allows you to map available fields automatically, or you can set them manually.
Getint's support team is dedicated to delivering a seamless and efficient integration experience tailored to your specific requirements. Should you encounter any setup challenges or need assistance with missing features, our committed support team is ready to provide guidance and help.
### Supported Fields in Monday.com
Getint allows you to map fields between different platforms, and here's a list of our currently supported:
{% hint style="info" %}
#### **Field Mappings Explained:**
**One-Way Mapping:**
* When you update fields in one of the synchronized apps, those changes will appear in the other app.
* However, updates made in the other app won’t affect the first app because the fields are read-only.
**Two-Way Mapping:**
* Updates to synced fields will be reflected in both apps.
* If you modify a field in one app, the change will automatically sync to the other app as well.
**Tip:** While it’s technically not possible to directly modify read-only fields, we offer a solution for achieving bidirectional integration or migrating these fields using custom fields. Setting up this solution requires specific steps, but it is indeed possible. You can find more detailed information in this [article.](https://docs.getint.io/getting-started-with-the-platform/prepare-for-integration/understanding-the-difference-between-platforms-you-integrate)
{% endhint %}
| **Monday.com Field** | **One Way** | **Both Ways** |
| ------------------------------------------------------------------------------------------------------------------------------- | ----------- | ------------- |
| Comments & Attachments | ✔️ | ✔️ |
|
Custom fields
Dropdown - Label - People - Priority - Status - Text - Timeline Start Date/End Date
| ✔️ | ✔️ |
| Date | ✔️ | ✔️ |
| Group | ✔️ | ✔️ |
| ID | ✔️ | |
| Person | ✔️ | ✔️ |
| Status | ✔️ | ✔️ |
| Title (Name) | ✔️ | ✔️ |
| URL | ✔️ | |
{% hint style="danger" %}
**Important Note:**\
We strive to maintain the accuracy of this list, but please be aware that supported fields may vary in the original product.
{% endhint %}
### Limitations to be Considered
At Getint, we continuously update our supported features, fields, and compatible apps. However, there are a few important limitations to keep in mind:
* When you add comments to an issue, they will be displayed under the user account you select to establish the connection. For smooth integration, it’s advisable to create a dedicated Service Account specifically for building your integration. Although the original author’s name will be visible in the comment footer, the comment itself will remain associated with the account that set up the connection.
* Unfortunately, incorporating the history of changes is not feasible at this time.
* Attachments need to be uploaded from the **Files** column in your Monday.com project, not from the **Files** section within the tasks. Otherwise, your attachments will not trigger syncs to the other app you integrate.
* Updates to existing comments will not trigger syncs. Subcomments do not trigger syncs as well.
### Contacting Our Support Team
Our Support Team at Getint is eager to assist with your integration and migration needs and answer any other questions you may have. If you're seeking assistance or a deeper understanding of our solution, we invite you to schedule a demo call [here](https://www.getint.io/schedule-demo-call).
#### Case Studies
Large and small businesses have experienced the benefits of using Getint for their data integration needs. This has provided them with various solutions tailored to their teams and organizations. We invite you to explore some of our [Case Studies](https://www.getint.io/case-studies), which are true accounts of how Getint continually enhances and improves the tool integration process.
{% hint style="info" %}
**Are you looking for a specific solution that we don’t currently support?** Please get in touch with our [support team](https://getint.io/help-center), and we can assist you in developing a customized solution for your particular case.
{% endhint %}
# Notion
## Getint: Simplifying Notion Integration and Data Synchronization
Getint simplifies the integration and synchronization of a wide range of tools. It supports various connectivity scenarios, including Notion - Jira, Notion - Asana, Notion - Monday, Notion - Azure DevOps, and more. Whether you need a software-as-a-service (SaaS) or an On-premise solution, Getint offers the flexibility to meet the unique requirements of different businesses.
### The article covers the following topics:
* [How to Setup the App](#setting-up-getint-for-notion)
* [Supported Fields in Notion](#supported-fields-in-notion)
* [Limitations and Considerations to Keep in Mind](#limitations-to-keep-in-mind)
* [Case Studies and Contacting Our Support Team](#contacting-our-support-team-and-case-studies)
Getint ensures seamless data synchronization across platforms and instances, with specific support for Notion. Users can effectively monitor and manage tasks in diverse environments while seamlessly integrating with other platforms.
### Setting Up Getint for Notion
Getint simplifies data integration and migration. Follow these straightforward steps to connect your systems, such as Notion, map types (i.e., Task - Task), and fields (i.e., Description - Summary). Whether you’re syncing data or performing a continuous one-time migration, Getint has you covered. Our dedicated support team is ready to assist you with any setup or operational challenges.
For more detailed guides on setting up your Notion integration, refer to the following resources:
* [Starting with Getint - Quickstart Guides](https://docs.getint.io/guides/quickstart)
* [Integration Guides](https://docs.getint.io/guides/integration-synchronization)
* [Migration Guides](https://docs.getint.io/guides/migration)
* [Understanding Getint - Workflows](https://docs.getint.io/getintio-platform/workflows)
Here's a simplified version of how to integrate Notion with other tools (you can find a detailed overview [**here**](https://docs.getint.io/guides/integration-synchronization/jira-notion-integration)):
1. **Access Getint:** If you’re using Jira, navigate to the "Apps" section, search for new apps, and acquire the app from the [Atlassian Marketplace.](https://marketplace.atlassian.com/apps/1231784/notion-integration-for-jira?tab=overview\&hosting=cloud) Alternatively, if you need to integrate Notion with a non-Jira application, consider choosing either [Getint On-Premise or Getint SaaS.](https://www.getint.io/contact)
2. **Token Generation for Notion:**
* Open the "Notion" app.
* Click on the "three dots" located in the top right corner.
* Select "Add a Connection."
* Navigate to "Manage Connections" and choose "Develop or Manage integrations."
* Click on "New Integration."
* Provide a name for your integration, grant the necessary permissions, and copy the "API token." This will be your password to create a connection.
3. **How to Establish a Connection with Notion:** Ensure you’re logged in as a user with the correct permissions. Click "Select App" and choose "Notion." Select "Create New" to establish a new connection with your Notion instance. Name your connection and add the "URL" of your Notion instance. Provide your login credentials to connect with Getint.
4. **Choose and Connect the Second App:** Select and link another tool to integrate with Notion—options include another Notion instance, ServiceNow, Jira, or any other supported tool.
5. **Mapping Types and Fields:** Link Notion types (Tasks) to synchronize with other tools. You can use the "Quick Build" feature, which allows you to map available fields automatically or set them manually.
Getint's support team is committed to ensuring a smooth and efficient integration experience customized to your unique needs. If you encounter any challenges during setup or require assistance with missing functionalities, our dedicated support team can provide guidance and assistance.
### Supported Fields in Notion
Getint allows you to map fields between different platforms, and here's a list of our currently supported:
{% hint style="info" %}
#### **How Field Mappings Work:**
**One-Way Mapping:**
* When you update fields in one of the synchronized apps, those changes will appear in the other app. However, updates made in the other app won’t impact the first app because the fields are read-only.
**Two-Way Mapping:**
* Updates to synchronized fields will be reflected in both apps. If you modify a field in one app, the change will automatically sync to the other app as well.
**Tip:** While it’s technically not possible to directly modify read-only fields, we provide a solution for achieving bidirectional integration or migrating these fields using custom fields. Setting up this solution requires specific steps, but it is indeed feasible. You can find more detailed information in this [article.](https://docs.getint.io/getting-started-with-the-platform/prepare-for-integration/understanding-the-difference-between-platforms-you-integrate)
{% endhint %}
| **Notion Field** | **One Way** | **Both Ways** |
| -------------------------------------------------------------------------------------------------------------------- | ----------- | ------------- |
| Comments & Attachments | ✔️ | ✔️ |
|
Custom fields
Checkbox - Date - Description - Estimates - Select - Status - Text - URL
| ✔️ | ✔️ |
| Database Id | ✔️ | ✔️ |
| Due (End Date) | ✔️ | ✔️ |
| Due (Start Date) | ✔️ | ✔️ |
| Item Type | ✔️ | |
| Priority | ✔️ | ✔️ |
| Reason | ✔️ | ✔️ |
| Status | ✔️ | ✔️ |
| Summary | ✔️ | ✔️ |
| Task name | ✔️ | ✔️ |
| URL | ✔️ | |
{% hint style="warning" %}
**Important Note:**\
We strive to maintain the accuracy of this list, but please be aware that supported fields may vary in the original product.
{% endhint %}
### Limitations to Keep in Mind
At Getint, we continuously update our supported features, fields, and compatible apps. However, there are a few important limitations to keep in mind:
* At the time of publishing this article, we currently only support mapping Tasks for Notion, and Assignees are not supported.
* Comments added to the issue will display under the user account you select when creating the connection. For a seamless integration, we recommend creating a dedicated Service Account. Although the original author’s name will appear in the comment footer, the comment will still be linked to the account that established the connection.
* Unfortunately, integrating the history of changes is not possible due to the technical limitations of Jira / Notion APIs.
### Contacting Our Support Team & Case Studies
Our Support Team at Getint is eager to assist with your integration and migration needs and answer any other questions you may have. If you're seeking assistance or a deeper understanding of our solution, we invite you to schedule a demo call [here](https://www.getint.io/schedule-demo-call).
#### Case Studies
Large and small businesses have experienced the benefits of using Getint for their data integration needs. This has provided them with various solutions tailored to their teams and organizations. We invite you to explore some of our [Case Studies](https://www.getint.io/case-studies), which are true accounts of how Getint continually enhances and improves the tool integration process.
{% hint style="info" %}
**Are you looking for a specific solution that we don’t currently support?** Please get in touch with our [support team](https://getint.io/help-center), and we can assist you in developing a customized solution for your particular case.
{% endhint %}
# Salesforce
## Getint: Simplifying Salesforce Integration and Data Synchronization
Getint, a powerful integration solution, seamlessly connects and synchronizes various tools. It supports various connectivity scenarios, including Salesforce - Jira, Salesforce - Azure DevOps, and more. Whether you require Software-as-a-Service (SaaS) or On-Premise deployment, Getint provides the flexibility to meet the distinct needs of different businesses and companies.
### What does this article cover?
* [How to Set Up the App](#setting-up-getint-for-salesforce)
* [Supported Fields in Salesforce](#supported-fields-in-salesforce)
* [Limitations and Considerations to Make](#limitations-to-be-considered)
* [Contacting Our Support Team - Case Studies](#contacting-our-support-team)
**Getint** facilitates smooth data synchronization across various platforms and instances. It supports Salesforce, allowing users to monitor and manage tasks in diverse environments effectively. Additionally, it enables seamless integration with other platforms.
### Setting Up Getint for Salesforce
Getint simplifies data integration and migration. You can connect your systems with easy setup steps, such as Salesforce, map types (i.e., Task - Case), and fields (i.e., Priority - Priority). Whether you're looking to sync data continuously or perform a one-time migration, Getint has got you covered. Our dedicated support team is always ready to assist you with any challenges you may encounter during setup or operation.
For more detailed guides on how to set up your Salesforce integration, please make sure to check the following:
* [Starting with Getint - Quickstart Guides](https://docs.getint.io/guides/quickstart)
* [Integration Guides](https://docs.getint.io/guides/integration-synchronization)
* [Migration Guides](https://docs.getint.io/guides/migration)
* [Understanding Getint - Workflows](https://docs.getint.io/getintio-platform/workflows)
Here's a simplified version of how to integrate Salesforce with other tools (you can find a detailed overview [**here**](https://docs.getint.io/guides/integration-synchronization/jira-salesforce-integration)):
1. **Access Getint:** Navigate through the [Atlassian Marketplace](https://marketplace.atlassian.com/apps/1231635/connector-for-salesforce-jira-salesforce-integration?hosting=cloud\&tab=overview), go to your "Apps" section in Jira, and search for the "Getint Salesforce integration" app. Alternatively, if you need to integrate Salesforce with a non-Jira application, consider choosing either [Getint On-Premise or Getint SaaS.](https://app.getint.io/)
2. **Token Generation for Salesforce:** To connect with Salesforce, users must grant an "API token" to Getint via the "OAuth authentication" method within our app.
3. **Establishing a Connection with Salesforce:**
* Ensure you're logged in as a user with the correct permissions. Click "Select App" and choose "Salesforce."
* Select "Create New" to establish a new connection with your Salesforce instance. Name your connection, and add the URL of your Salesforce instance.
* Provide the login credentials. Click the "Authorize Getint" button.
* You’ll be redirected to the Salesforce login page. Once authorized, a confirmation message will prompt you to click "Add" to create the connection. Click "Add."
* Select the newly created connection and press "Connect."
4. **Choose and Connect the Second App:** You can select and link an additional tool to integrate with Salesforce. Options include another Salesforce instance, ServiceNow, Jira, or other supported tools.
5. **Map Types and Fields:** Link Salesforce types (Account, Case, and Contact) to synchronize with other tools. You can use the Quick Build feature, which allows you to map available fields automatically, or you can set them manually.
Getint’s support team is dedicated to delivering a seamless and efficient integration experience customized to your specific requirements. Should you encounter any inconveniences or need assistance with missing features, our committed support team is ready to provide guidance and help.
### Supported Fields in Salesforce
Getint allows you to map fields between different platforms, and here's a list of our currently supported:
{% hint style="info" %}
#### **How Field Mappings Work:**
**One-Way Mapping:**
* When you update fields in one of the synced apps, those changes will appear in the other app. However, updates made in the other app won’t affect the first app because the fields are read-only.
**Two-Way Mapping:**
* Updates to synced fields will be reflected in both apps. If you modify a field in one app, the change will automatically sync to the other app as well.
**Tip:** While technically it's not possible to directly modify read-only fields, we offer a solution to achieve bidirectional integration or migrate these fields using custom fields. Setting up this solution requires specific steps, but it is indeed possible. You can find more detailed information in this [article.](https://docs.getint.io/getting-started-with-the-platform/prepare-for-integration/understanding-the-difference-between-platforms-you-integrate)
{% endhint %}
| **Salesforce Field** | **One Way** | **Both Ways** |
| ------------------------------------------------------------------------------------------------ | ----------- | ------------- |
| Case Number | ✔️ | |
| Case Origin | ✔️ | ✔️ |
| Case Reason | ✔️ | ✔️ |
| Case Type | ✔️ | ✔️ |
| Company | ✔️ | ✔️ |
|
Custom fields
Date/Time - Email - Number - Phone - Picklist - Text
| ✔️ | ✔️ |
| Engineering Req Number | ✔️ | ✔️ |
| Free Text | ✔️ | ✔️ |
| ID | ✔️ | |
| Internal Comments | ✔️ | ✔️ |
| Item Type | ✔️ | |
| Name | ✔️ | ✔️ |
| Object Type | ✔️ | |
| Phone | ✔️ | ✔️ |
| Potenial Liability | ✔️ | ✔️ |
| Priority | ✔️ | ✔️ |
| Product | ✔️ | ✔️ |
| Single select | ✔️ | ✔️ |
| SLA Violation | ✔️ | ✔️ |
| Status | ✔️ | ✔️ |
| Subject | ✔️ | ✔️ |
| URL | ✔️ | |
{% hint style="danger" %}
**Important Note:**\
We strive to maintain the accuracy of this list, but please be aware that supported fields may vary in the original product.
{% endhint %}
### Limitations to be Considered
At Getint, we continuously update our supported features, fields, and compatible apps. However, there are a few important limitations to keep in mind:
* When you add comments to an issue, they will be displayed under the user account you select to establish the connection. For smooth integration, it’s advisable to create a dedicated Service Account specifically for building your integration. Although the original author’s name will be visible in the comment footer, the comment itself will remain associated with the account that set up the connection.
* Unfortunately, incorporating the history of changes is not feasible at this time.
### Contacting Our Support Team
Our Support Team at Getint is eager to assist with your integration and migration needs and answer any other questions you may have. If you're seeking assistance or a deeper understanding of our solution, we invite you to schedule a demo call [here](https://www.getint.io/schedule-demo-call).
#### Case Studies
Large and small businesses have experienced the benefits of using Getint for their data integration needs. This has provided them with various solutions tailored to their teams and organizations. We invite you to explore some of our [Case Studies](https://www.getint.io/case-studies), which are true accounts of how Getint continually enhances and improves the tool integration process.
{% hint style="info" %}
**Are you looking for a specific solution that we don’t currently support?** Please get in touch with our [support team](https://getintio.atlassian.net/servicedesk/customer/portals), and we can assist you in developing a customized solution for your particular case.
{% endhint %}
# ServiceNow
## Getint: Simplifying ServiceNow Integration and Data Synchronization
Getint is expertly designed to seamlessly integrate and synchronize a wide range of tools. It supports various connectivity scenarios, including ServiceNow - Jira, ServiceNow - Asana, ServiceNow - Azure DevOps, and ServiceNow - Zendesk. Whether you choose the Software-as-a-Service (SaaS) or On-Premise solution, Getint offers the flexibility to meet diverse business requirements.
### Key Points Covered in the Article:
* [Setting Up the App](#how-to-setup-getint-for-servicenow)
* [Supported Fields in ServiceNow](#supported-fields-for-servicenow-integration)
* [Limitations and Considerations](#limitations-and-considerations)
* [Contacting Our Support Team - Case studies](#contacting-our-support-team)
Getint enables seamless data synchronization within the same platform, different platforms/different instances. It supports ServiceNow across different projects. This allows users to efficiently track and manage ServiceNow tasks/incidents in diverse environments as well as integrate ServiceNow with other platforms.
### How to Set Up Getint for ServiceNow
Getint simplifies data integration and migration. With easy setup steps, you can connect your systems, such as ServiceNow, map types (i.e., Task - Incident), and fields (i.e., Assignee - Assigned to). Whether you're looking to sync data continuously or perform a one-time migration, Getint has got you covered. Our dedicated support team is always ready to assist you with any challenges you may encounter during setup or operation.
For more detailed guides on how to set up your ServiceNow integration, please make sure to check the following:
* [Starting with Getint - Quickstart Guides](https://docs.getint.io/guides/quickstart)
* [Integration Guides](https://docs.getint.io/guides/integration-synchronization)
* [Migration Guides](https://docs.getint.io/guides/migration)
* [Understanding Getint - Workflows](https://docs.getint.io/getintio-platform/workflows)
Here's a simplified version of how to integrate ServiceNow with other tools (you can find a detailed overview [**here**](https://docs.getint.io/guides/integration-synchronization/jira-servicenow-integration)):
1. **Accessing Getint:**
* If you're using Jira, find the app in the [Atlassian Marketplace](https://marketplace.atlassian.com/apps/1223935/servicenow-integration-for-jira-servicenow-connector?hosting=cloud\&tab=overview).
* For non-Jira applications, choose between [Getint On-Premise or Getint SaaS](https://app.getint.io/).
2. **Establish a Connection with ServiceNow:**
* Log in with the correct permissions.
* Select ServiceNow as the app, create a new connection, and provide the instance URL and login credentials.
3. **Choose and Connect the Second App:**
* Choose another tool (i.e., DevOps, Jira) to integrate with ServiceNow.
4. **Map Types and Fields:**
* Link ServiceNow types (e.g., Incidents, Tasks) to synchronize with other tools.
* Use the "Quick Build" feature or set mappings manually.
Getint's support team ensures a smooth integration experience customized to your needs. If you encounter challenges or need assistance, we're here to help!
### Supported Fields for ServiceNow Integration
Getint allows you to map fields between different platforms, and here's a list of our currently supported:
{% hint style="info" %}
#### **How Field Mappings Work:**
**One-Way Mapping:**
* When you update fields in one of the synced apps, those changes will appear in the other app. However, updates made in the other app won’t affect the first app because the fields are read-only.
**Two-Way Mapping:**
* Updates to synced fields will be reflected in both apps. If you modify a field in one app, the change will automatically sync to the other app as well.
**Tip:**
While technically it's not possible to directly modify read-only fields, we offer a solution to achieve bidirectional integration or migrate these fields using custom fields. Setting up this solution requires specific steps, but it is indeed possible. You can find more detailed information in this [article.](https://docs.getint.io/getting-started-with-the-platform/prepare-for-integration/understanding-the-difference-between-platforms-you-integrate)
{% endhint %}
| **ServiceNow Field** | **One Way** | **Both Ways** |
| --------------------------------------------------------------------------------------------------------- | ----------- | ------------- |
| Actual end | ✔️ | ✔️ |
| Actual start | ✔️ | ✔️ |
| Approval | ✔️ | ✔️ |
| Approval set | ✔️ | ✔️ |
| Assigned to (Assignees) | ✔️ | ✔️ |
| Assignment group | ✔️ | ✔️ |
| Attachments | ✔️ | ✔️ |
| Business impact | ✔️ | ✔️ |
| Business resolve time | ✔️ | |
| Caller | ✔️ | ✔️ |
| Category | ✔️ | ✔️ |
| Child Incidents | ✔️ | ✔️ |
| Close code | ✔️ | ✔️ |
| Close notes | ✔️ | ✔️ |
| Closed | ✔️ | ✔️ |
| Closed by | ✔️ | ✔️ |
| Configuration item | ✔️ | ✔️ |
| Contact type | ✔️ | ✔️ |
| Correlation display | ✔️ | ✔️ |
| Correlation ID | ✔️ | ✔️ |
| Created | ✔️ | |
| Created by | ✔️ | ✔️ |
| Comments | ✔️ | ✔️ |
|
Custom fields
Date - Dropdown fields - Text fields - Reference fields - URL
| ✔️ | ✔️ |
| Description | ✔️ | ✔️ |
| Due date | ✔️ | ✔️ |
| Effective number | ✔️ | |
| Escalation | ✔️ | |
| Expected start | ✔️ | ✔️ |
| Follow up | ✔️ | ✔️ |
| Id | ✔️ | |
| Impact | ✔️ | ✔️ |
| Incident state | ✔️ | ✔️ |
| Last reopened at | ✔️ | |
| Last reopened by | ✔️ | |
| Location | ✔️ | ✔️ |
| Notify | ✔️ | ✔️ |
| Number | ✔️ | ✔️ |
| On hold reason | ✔️ | ✔️ |
| Opened | ✔️ | ✔️ |
| Opened by | ✔️ | ✔️ |
| Order | ✔️ | ✔️ |
| Priority | ✔️ | ✔️ |
| Probable cause | ✔️ | ✔️ |
| Reassignment count | ✔️ | ✔️ |
| Reopen count | ✔️ | ✔️ |
| Resolve time | ✔️ | |
| Resolved | ✔️ | ✔️ |
| Resolved by | ✔️ | ✔️ |
| Service | ✔️ | ✔️ |
| Severity | ✔️ | ✔️ |
| Short description | ✔️ | ✔️ |
| State (Status) | ✔️ | ✔️ |
| Subcategory | ✔️ | ✔️ |
| Subtasks | ✔️ | ✔️ |
| Task type | ✔️ | ✔️ |
| Transfer reason | ✔️ | |
| Updated | ✔️ | |
| Updated by | ✔️ | ✔️ |
| Updates | ✔️ | ✔️ |
| Upon approval | ✔️ | ✔️ |
| Upon reject | ✔️ | ✔️ |
| Urgency | ✔️ | ✔️ |
| URL | ✔️ | |
{% hint style="danger" %}
**Important Note:**\
We strive to maintain the accuracy of this list, but please be aware that supported fields may vary in the original product.
{% endhint %}
### Limitations and Considerations
At Getint, we continuously update our supported features, fields, and compatible apps. However, there are a few important points to consider:
* **Issue Types:** When Getint creates a new issue in ServiceNow, it will always be one specific type (e.g., Task or Incident). You can set the default item type using a rule or manually adjust it in ServiceNow after creation.
* **Comments:** Comments added by Getint will appear under the user account you choose during connection setup. Consider creating a dedicated Service Account for integration to maintain consistency. The original author's name will appear in the comment footer, but the comment will be assigned to the connecting account.
* **Change History:** Unfortunately, Getint cannot integrate the history of changes.
* **Private Tasks:** While Getint allows the creation of private tasks in ServiceNow, setting them up on boards is not supported.
### Contacting Our Support Team
Our dedicated Support Team is ready to assist with your integration and migration needs. If you have questions or need deeper insights into our solution, feel free to schedule a [demo call](https://www.getint.io/schedule-demo-call) with us.
#### Case Studies
Explore real-world examples of how Getint enhances tool integration for businesses of all sizes. Our [Case Studies](https://www.getint.io/case-studies) showcase tailored solutions that empower teams and organizations.
{% hint style="info" %}
**Are you looking for a specific solution that we don’t currently support?** Please get in touch with our [support team](https://getint.io/help-center), and we can assist you in developing a customized solution for your particular case.
{% endhint %}
# Trello
## Getint: Simplifying Trello Integration and Data Synchronization
Getint connects and synchronizes multiple tools, allowing teams to create seamless integrations between platforms such as Trello, Jira, Asana, and Azure DevOps. Available as both a Cloud and an on-premise solution, Getint provides the flexibility to support a wide range of business needs and deployment preferences.
### Key Topics Covered:
* [App Setup](#app-setup)
* [Supported Trello Fields](#supported-trello-fields)
* [Limitations and Important Notes](#limitations-and-important-notes)
* [Contacting Our Support Team](#contacting-our-support-team)
Getint enables data synchronization across platforms and instances, including Trello. This allows users to track, manage, and update tasks across multiple projects while keeping Trello aligned with other tools in their ecosystem.
### App Setup
Getint simplifies the process of connecting systems and synchronizing or migrating data between them. Follow the steps below to start integrating Trello with your preferred tools.
**Step 1: Access Getint**
* **For Jira users:** If you are integrating Jira with Trello, install the Getint app directly from the [Atlassian Marketplace](https://marketplace.atlassian.com/apps/1231790/integration-for-jira-and-trello-2-way-integration?hosting=cloud\&tab=overview).
* **For other platforms:** Select either the browser version ([app.getint.io](http://app.getint.io/)) or On-Premise version of Getint based on your organizational requirements.
**Step 2: Set Up a Connection with Trello**
* Ensure you have the necessary [access permissions](https://docs.getint.io/guides/quickstart/connection#trello) in Trello.
* Select **Trello** as the application.
* Create a new connection and enter your Trello credentials.
**Step 3: Connect to Another Tool**
* Choose the platform you want to integrate with Trello, such as **Jira** or **Azure DevOps**.
**Step 4: Map Types and Fields**
* Match Trello types and fields with their corresponding entities in the other tool.
* Use the **Quick Build** option for automatic mapping, or define mappings manually to better align with your workflows.
Our support team is always available to help with setup or operational questions.
For additional guidance on using Getint with Trello, refer to:
* [Quickstart Guides](https://docs.getint.io/guides/quickstart)
* [Jira Trello Integration Guide](https://docs.getint.io/guides/integration-synchronization/jira-trello-integration)
* [Migration Guides](https://docs.getint.io/guides/migration)
### Supported Trello Fields
Getint enables field mapping between Trello and other platforms. Below is an overview of the currently supported field-mapping options and their functionality.
{% hint style="info" %}
#### **How Field Mappings Work:**
**One-Way Mapping:**
* When you update fields in one of the synced apps, those changes will appear in the other app. However, updates made in the other app won’t affect the first app because the fields are read-only.
**Two-Way Mapping:**
* Updates to synced fields will be reflected in both apps. If you modify a field in one app, the change will automatically sync to the other app as well.
**Tip:**
While technically it's not possible to directly modify read-only fields, we offer a solution to achieve bidirectional integration or migrate these fields using custom fields. Setting up this solution requires specific steps, but it is indeed possible. For more detailed information, please refer to this [article.](https://docs.getint.io/getting-started-with-the-platform/prepare-for-integration/understanding-the-difference-between-platforms-you-integrate)
{% endhint %}
| **Trello Field** | **One Way** | **Both Ways** |
| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Attachments | | |
| Comments | ✔️ | ✔️ |
| Custom Fields | | |
| Description | ✔️ | ✔️ |
| Id | ✔️ | |
| Item Type | ✔️ | |
| List | ✔️ | ✔️ |
| Status | ✔️ | ✔️ |
| Title | ✔️ | ✔️ |
| URL | ✔️ | |
{% hint style="warning" %}
**Important Note:**\
We strive to maintain the accuracy of this list, but please be aware that supported fields may vary in the original product.
{% endhint %}
### Limitations and Important Notes
At Getint, we continuously update our supported features, fields, and compatible apps. However, there are a few important points to consider:
* **Attachments**: Syncing attachments isn’t supported.
* **Change History**: Unfortunately, Getint cannot integrate the history of changes.
* **Comments**: Comments added by Getint will appear under the user account you choose during connection setup. Consider creating a dedicated Service Account for integration to maintain consistency. The original author’s name will appear in the comment footer, but the comment will be assigned to the connecting account.
* **Custom Fields**: Aren’t supported for this integration.
* **Issue Types**: Currently, the integration supports Trello Cards as the only issue type.
* **Multi-project support**: Many-to-many project synchronization between Jira and Trello is not supported.
* **Text Formatting Errors**: Formatting is not fully preserved during synchronization; bullet points may not convert correctly in Jira.
### Contacting Our Support Team
Our dedicated Support Team is ready to assist with your integration and migration needs. If you have questions or need deeper insights into our solution, feel free to schedule a [demo call](https://www.getint.io/schedule-demo-call) with us.
#### Case Studies
Explore real-world examples of how Getint enhances tool integration for businesses of all sizes. Our [Case Studies](https://www.getint.io/case-studies) showcase tailored solutions that empower teams and organizations.
{% hint style="info" %}
**Are you looking for a specific solution that we don’t currently support?** Please get in touch with our [support team](https://getint.io/help-center), and we can assist you in developing a customized solution for your particular case.
{% endhint %}
# Wrike
## Getint: Simplifying Wrike Integration and Data Synchronization
Getint connects and synchronizes multiple tools, allowing teams to create seamless integrations between platforms such as Wrike, Jira, Asana, and Azure DevOps. Available as both a Cloud and an on-premise solution, Getint provides the flexibility to support a wide range of business needs and deployment preferences.
### Key Topics Covered:
* [App Setup](#app-setup)
* [Supported Wrike Fields](#supported-wrike-fields)
* [Limitations and Important Notes](#limitations-and-important-notes)
* [Support Resources and Case Studies](#contacting-our-support-team)
Getint enables data synchronization across platforms and instances, including Wrike. This allows users to track, manage, and update tasks across multiple projects while keeping Wrike aligned with other tools in their ecosystem.
### App Setup
Getint simplifies the process of connecting systems and synchronizing or migrating data between them. Follow the steps below to start integrating Wrike with your preferred tools.
**Step 1: Access Getint**
* **For Jira users:** If you are integrating Jira with Wrike, install the Getint app directly from the [Atlassian Marketplace](https://marketplace.atlassian.com/apps/1223936/wrike-integration-for-jira-wrike-connector?hosting=cloud\&tab=overview).
* **For other platforms:** Select either the browser version ([app.getint.io](http://app.getint.io/)) or On-Premise version of Getint based on your organizational requirements.
**Step 2: Set Up a Connection with Wrike**
* Ensure you have the necessary [access permissions](https://docs.getint.io/guides/quickstart/connection#wrike) in Wrike.
* Select **Wrike** as the application.
* Create a new connection and enter your Wrike credentials.
**Step 3: Connect to Another Tool**
* Choose the platform you want to integrate with Wrike, such as **Jira** or **Azure DevOps**.
**Step 4: Map Types and Fields**
* Match Wrike types and fields with their corresponding entities in the other tool.
* Use the **Quick Build** option for automatic mapping, or define mappings manually to better align with your workflows.
Our support team is always available to help with setup or operational questions.
For additional guidance on using Getint with Wrike, refer to:
* [Quickstart Guides](https://docs.getint.io/guides/quickstart)
* [Jira Wrike Integration Guide](https://docs.getint.io/guides/integration-synchronization/jira-wrike-integration)
* [Migration Guides](https://docs.getint.io/guides/migration)
### Supported Wrike Fields
Getint enables field mapping between Wrike and other platforms. Below is an overview of the currently supported field-mapping options and their functionality.
{% hint style="info" %}
#### **How Field Mappings Work:**
**One-Way Mapping:**
* When you update fields in one of the synced apps, those changes will appear in the other app. However, updates made in the other app won’t affect the first app because the fields are read-only.
**Two-Way Mapping:**
* Updates to synced fields will be reflected in both apps. If you modify a field in one app, the change will automatically sync to the other app as well.
**Tip:**
While technically it's not possible to directly modify read-only fields, we offer a solution to achieve bidirectional integration or migrate these fields using custom fields. Setting up this solution requires specific steps, but it is indeed possible. For more detailed information, please refer to this [article.](https://docs.getint.io/getting-started-with-the-platform/prepare-for-integration/understanding-the-difference-between-platforms-you-integrate)
{% endhint %}
| **Wrike Field** | **One Way** | **Both Ways** |
| ------------------------------------------------------------------------ | ----------- | ------------- |
| Assignee | ✔️ | ✔️ |
| Comments & Attachments | ✔️ | ✔️ |
| Custom Fields **Date - Number - Single Select - Text** | ✔️ | ✔️ |
| Description | ✔️ | ✔️ |
| Due Date | ✔️ | ✔️ |
| Id | ✔️ | |
| Is Milestone | ✔️ | |
| Start Date | ✔️ | ✔️ |
| Status | ✔️ | ✔️ |
| Title | ✔️ | ✔️ |
| URL | ✔️ | |
{% hint style="warning" %}
**Important Note:**\
We strive to maintain the accuracy of this list, but please be aware that supported fields may vary in the original product.
{% endhint %}
### Limitations and Important Notes
At Getint, we continuously update our supported features, fields, and compatible apps. However, there are a few important points to consider:
* **Change History**: Unfortunately, Getint cannot integrate the history of changes.
* **Comments**: Comments added by Getint will appear under the user account you choose during connection setup. Consider creating a dedicated Service Account for integration to maintain consistency. The original author’s name will appear in the comment footer, but the comment will be assigned to the connecting account.
* **Multi-project support**: Many-to-many project synchronization between Jira and Wrike is not supported.
* **Sub-tasks**: Currently, syncing sub-tasks is not supported.
* **Text Formatting Errors**: Formatting is not fully preserved during synchronization. For example, bullet points may not convert correctly in Jira.
### Contacting Our Support Team
Our dedicated Support Team is ready to assist with your integration and migration needs. If you have questions or need deeper insights into our solution, feel free to schedule a [demo call](https://www.getint.io/schedule-demo-call) with us.
#### Case Studies
Explore real-world examples of how Getint enhances tool integration for businesses of all sizes. Our [Case Studies](https://www.getint.io/case-studies) showcase tailored solutions that empower teams and organizations.
{% hint style="info" %}
**Are you looking for a specific solution that we don’t currently support?** Please get in touch with our [support team](https://getint.io/help-center), and we can assist you in developing a customized solution for your particular case.
{% endhint %}
# Zendesk
## Getint: Simplifying Zendesk Integration and Data Synchronization
**Getint** connects and synchronizes various tools, enabling integrations between Zendesk and platforms like Jira, Asana, or Azure DevOps. It offers both SaaS and On-Premise solutions, allowing businesses to choose the deployment option that best fits their needs.
### Key Topics Covered:
* [Setting Up the App](/getting-started-with-the-platform/apps-connectors/zendesk#how-to-set-up-getint-for-zendesk)
* [Supported Fields in Zendesk](#supported-fields-for-zendesk-integration)
* [Limitations and Considerations](#limitations-and-considerations)
* [Contacting Support - Case Studies](#contacting-our-support-team)
Getint synchronizes data across platforms and instances, including Zendesk. It allows users to track and manage tasks or activities across projects while connecting Zendesk with other tools for improved coordination.
### How to Set Up Getint for Zendesk
Getint simplifies connecting and migrating data between systems. Below are the steps to get started:
**Step 1: Access Getint**
* For Jira users: If you want to integrate Jira with Zendesk, download the app from the Atlassian Marketplace [here](https://marketplace.atlassian.com/apps/1223934/zendesk-integration-for-jira-2-way-zendesk-connector?hosting=cloud\&tab=overview).
* For other tools: Select between Getint On-Premise or SaaS options.
**Step 2: Set Up a Connection with Zendesk**
* Ensure you have the correct [access permissions](https://docs.getint.io/guides/quickstart/connection#zendesk).
* Choose Zendesk as the app, create a new connection, and enter your Zendesk credentials.
**Step 3: Connect to Another Tool**
* Pick the platform you want to integrate with Zendesk, such as Jira.
**Step 4: Map Types and Fields**
* Match Zendesk categories with their counterparts in the other tool.
* Use the **Quick Build** feature for automatic mapping or customize mappings manually if needed.
Our support team is always available to assist with any setup or operational challenges.
For additional guidance on using Getint with Zendesk, refer to:
* [Quickstart Guides](https://docs.getint.io/guides/quickstart)
* [Jira Zendesk Integration Guide](https://docs.getint.io/guides/integration-synchronization/jira-zendesk-integration)
* [Migration Guides](https://docs.getint.io/guides/migration)
### Supported Fields for Zendesk Integration
Getint allows you to map fields between different platforms, and here's a list of our currently supported:
{% hint style="info" %}
#### **How Field Mappings Work:**
**One-Way Mapping:**
* When you update fields in one of the synced apps, those changes will appear in the other app. However, updates made in the other app won’t affect the first app because the fields are read-only.
**Two-Way Mapping:**
* Updates to synced fields will be reflected in both apps. If you modify a field in one app, the change will automatically sync to the other app as well.
**Tip:**
While technically it's not possible to directly modify read-only fields, we offer a solution to achieve bidirectional integration or migrate these fields using custom fields. Setting up this solution requires additional steps, but it is indeed possible. You can find more detailed information in this [article.](https://docs.getint.io/getting-started-with-the-platform/prepare-for-integration/understanding-the-difference-between-platforms-you-integrate)
{% endhint %}
| **Zendesk Field** | **One Way** | **Both Ways** |
| --------------------------------------------------------------------------------- | ----------- | ------------- |
| Assignee | ✔️ | ✔️ |
| Brand | ✔️ | ✔️ |
| Comments & Attachments | ✔️ | ✔️ |
|
Custom Fields:
Date - Dropdown - Multi-Line - Text
| ✔️ | ✔️ |
| Description | ✔️ | ✔️ |
| Group | ✔️ | ✔️ |
| ID | ✔️ | |
| IS Side Conversation | ✔️ | |
| Priority | ✔️ | ✔️ |
| Recipient | ✔️ | ✔️ |
| Requester email (on-create only) | ✔️ | |
| Requester name (on-create only) | ✔️ | |
| Status | ✔️ | ✔️ |
| Tags (Labels) | ✔️ | |
| Ticket form | ✔️ | ✔️ |
| Ticket form ID | ✔️ | ✔️ |
| Title (Subject) | ✔️ | ✔️ |
| Topic | ✔️ | ✔️ |
| Type | ✔️ | ✔️ |
| URL | ✔️ | |
{% hint style="warning" %}
**Important Note:**\
We strive to maintain the accuracy of this list, but please be aware that supported fields may vary in the original product.
{% endhint %}
### Limitations and Considerations
At Getint, we continuously update our supported features, fields, and compatible apps. However, there are a few important points to consider:
* **Issue Types**: When Getint creates a new issue in Zendesk, it will always be one specific type (Ticket).
* **Comments**: Comments added by Getint will appear under the user account you choose during connection setup. Consider creating a dedicated Service Account for integration to maintain consistency. The original author's name will appear in the comment footer, but the comment will be assigned to the connecting account.
Comments and attachments transferred from Zendesk to Jira can be set to either public, private, or skipped completely. You can configure your integration to enable both public and private visibility options simultaneously.
* **Change History**: Unfortunately, Getint cannot integrate the history of changes.
* **Inline** **Images** aren’t supported for the Description field.
* **On-create Only Fields**: These fields will only trigger when a new ticket is created in Zendesk. This means that if you add this field to your integration later or if you update an existing issue in Jira, it won’t be possible to retrieve the information from these fields.
* **Ticket Synchronization**: Keep in mind that when you start a new integration, all existing tickets in Zendesk will begin syncing with the connected tool, one by one. If you disable your previous integration and set up a new one, the syncing process will restart automatically, which may result in duplicate tickets.
### Contacting Our Support Team
Our dedicated Support Team is ready to assist with your integration and migration needs. If you have questions or need deeper insights into our solution, feel free to schedule a [demo call](https://www.getint.io/schedule-demo-call) with us.
#### Case Studies
Explore real-world examples of how Getint enhances tool integration for businesses of all sizes. Our [Case Studies](https://www.getint.io/case-studies) showcase tailored solutions that empower teams and organizations.
{% hint style="info" %}
**Are you looking for a specific solution that we don’t currently support?** Please get in touch with our [support team](https://getint.io/help-center), and we can assist you in developing a customized solution for your particular case.
{% endhint %}
# Quickstart
## Introduction
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).
Feel free to explore the platform and experience the benefits of Getint!
#### Why Choose Getint?
* **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
#### 1. Access the Welcome Page:
On the welcome page, you will be prompted to create a new integration. Click **Create Integration**.
* 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).
#### 2. Connect Your First Application:
* Select a side to connect your first app (the direction will be important later on, when defining the synchronization flow), and click **Connect App**.
* 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).
* In the next screen, create the connection to the intended workspace by pasting the workspace URL into the field and clicking **Next** (In this example, we are using Azure DevOps).
* Add the username and API token of the integration service account. Feel free to name the connection for distinction and click **Add**.
* In the next screen, click the drop-down to locate your newly created connection and select it.
* In the next screen, click the drop-down to select your workspace project, and click Connect to complete the connection. Also, 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)).
{% hint style="warning" %}
Decide this before you continue. If you leave **Sync many projects** unticked, that side of the integration stays locked to the project you select here, and adding more projects later means building a new integration from scratch. Ticking the option is the safer choice, since a many-projects integration can be reduced to a single project afterwards.
{% endhint %}
* **Repeat for the Second Application (Example: Jira)**: Follow the steps above to establish a connection with your second application.
#### 3. Map Work Item Types
* Select the **Quick Build** for an easier and faster setup.
* In the pop-up screen, click **Build** for Getint to automatically map similar work item types and create field mappings
* 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.
* Provide a name to your integration in the upper-left corner field, and click **Create** once you are satisfied with your build.
* 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
* Within your integration editor screen**,** 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.
* 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.
* 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="" %}
* **Status Mapping**: Customize your status mappings to fit your workflow.
* Map any remaining options through the highlighted dropdowns.
* **Comments and Attachments**: Configure your comments syncing setup.
* Enable attachment sync at the bottom of the screen. Make sure to apply your settings.
* Save Your Progress: Don’t forget to save your integration changes.
* **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
* 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.
* **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.
* **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.
### Conclusion
By following these steps, you have established a functional integration between your workspaces**.** 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.
# Access Tokens & Requirements
Connecting various applications within your organization is pivotal for fostering seamless collaboration and optimizing workflow efficiency. Getint offers a user-friendly platform made to simplify the integration process between diverse applications like Jira, ServiceNow, Azure DevOps, and Asana. This comprehensive guide will walk you through each step to establish robust connections effortlessly, ensuring smooth operations and enhanced productivity across your organization. Let's dive in!
### User Account Requirements
To initiate the integration process, you'll need user accounts in both systems you plan to integrate. We highly recommend using a dedicated service account with administrative privileges. This ensures all integration functions can execute smoothly, enabling Getint to perform a wide range of actions effectively. While administrative access is preferred, the essential requirement is that the user account possesses the necessary permissions to create, update, and manage projects, types, and fields within the applications.
### Role of the Service Account
The Service Account plays a pivotal role in facilitating integration operations. Here's what it entails:
* Getint operates under the Service Account to execute various actions, including task creation and updates across integrated platforms.
* Comments generated by Getint will be attributed to the Service Account, with clear indications of the original author in the comment footer. This practice fosters transparency and preserves context in communication threads
### Providing Connection Details
To kickstart the integration process, specific details are required:
* **URL of the Instance**: This refers to the web address where your application, such as Jira or ServiceNow, is hosted.
* **Username**: Enter the username associated with the Service Account in the application.
* **Password/Token**: Depending on the application, you may need to provide either a password or an API token for authentication.
By providing these details, Getint seamlessly connects your applications, mediating between two entities that would otherwise operate independently. It ensures smooth communication and data exchange, enabling your team to collaborate effectively across platforms and enhance productivity.
*Now, let's connect with each application, generating its tokens:*
### **Jira**
Jira offers integration options for Cloud, Server, and Data Center. Depending on your choice, the method for generating a Personal Access Token varies.
#### **Jira Cloud - API Token (Unscoped)**
It is required to use a Personal Access Token for integration:
* Log in to your Atlassian account and visit Atlassian Account Settings.
* Go to Security and select **Personal API Token**.
* Click on **Create API token** and provide a label for your token to identify it.
* Click **Create** to generate the token.
* Copy the token and ensure it is stored securely in a safe location.
This API token will work as the authentication mechanism for connecting Jira Cloud with Getint, enabling seamless integration and data synchronization between the two platforms.
{% embed url="" %}
#### **Forge Apps/Onpremise - Scoped Tokens**
While standard API tokens grant the full permissions of the associated user, **Scoped Tokens** allow you to limit what an application can see and do.
{% hint style="warning" %}
Scoped tokens are currently only available for **Forge apps** and **Jira On-Premise (self-hosted)** environments. They are **not** available for standard Jira Cloud service accounts or Jira Data Center deployments.
{% endhint %}
* Go to your profile, then **Account settings** > **Security** > **Create and manage API tokens**.
* Click **Create API token with scopes**.
* Set the token name and expiry date. Then, select Jira as the app and choose the relevant scopes.
* Next, depending on your company's security requirements, you can select either classic or granular scopes. The necessary permissions for each of them go as follows:
1. **Classic Scopes:**
* **Manage**
`manage:jira-configuration`
`manage:jira-data-provider`
`manage:jira-project`
`manage:jira-webhook`
* **Read**
`read:account`
`read:jira-user`
`read:me`
`read:jira-work`
* **Write**
`write:jira-work`
`write:servicedesk-request`
2. **Granular Scopes:**
* **Read**
`read:issue:jira`
`read:issue-meta:jira`
`read:issue.transition:jira`
`read:comment:jira`
`read:attachment:jira`
`read:issue.property:jira`
`read:issue-link-type:jira`
`read:project:jira`
`read:project-version:jira`
`read:field:jira`
`read:user:jira`
`read:board-scope:jira-software`
`read:sprint:jira-software`
`read:servicedesk:jira-service-management`
`read:jira-work`
`read:jira-user`
* **Write**
`write:issue:jira`
`write:comment:jira`
`write:attachment:jira`
`write:issue.property:jira`
`write:issue-link:jira`
`write:project-version:jira`
`write:board-scope:jira-software`
`write:sprint:jira-software`
`write:jira-work`
* **Delete**
`delete:comment:jira`
`delete:attachment:jira`
`delete:issue-link:jira`
* **Manage**
`read:servicedesk:jira-service-management`
`manage:jira-configuration`
`manage:jira-project`
`manage:jira-data-provider`
After generating your access token, copy it and store it safely.
#### **Jira Cloud - OAuth**
To add another layer of security and to meet certain tools' requirements (i.e., GitHub, GitLab, Azure DevOps), you can set up a connection with Jira OAuth. You will need your OAuth credentials as well as your Email and Personal Access Token.
{% hint style="warning" %}
Jira OAuth is only available for connections that use the Git connector. If you select Continuous Sync or Migration, you can't create the connection using OAuth. When OAuth is available, you'll set it up by adding your client ID and client secret.
{% endhint %}
* Go to **https\://(yourinstancename).atlassian.net/secure/admin/oauth-credentials.** Click **OAuth credentials** and then **Create credentials**.
{% hint style="info" %}
Ensure you have admin permissions in your Jira instance; otherwise, you won't be able to generate an OAuth token.
{% endhint %}
* Establish the parameters for your OAuth. You can find more information regarding each permission [here.](https://support.atlassian.com/jira-software-cloud/docs/allow-oauth-access/)
* When setting up OAuth credentials for integrations, the server base URL doesn't impact the validity of the credentials (client ID and secret key). This means that you can use any URL, such as a [getint.io](http://getint.io/), to generate your client ID and secret key.
{% hint style="danger" %}
It is important to note that **Development information** must be selected.
{% endhint %}
* Your newly created credentials will appear in the corresponding screen as shown below.
* To establish the connection, use your OAuth credentials along with your email and personal access token. You can create the personal access token by following the instructions provided at the beginning of this connector or clicking [here](https://docs.getint.io/guides/quickstart/connection#jira-cloud-oauth).
Here is an example of the correct way to enter all credentials
With these credentials, you'll be able to successfully connect your Jira instance to another tool. This opens up new opportunities for your integration journey, enabling smooth integration and data synchronization between the two platforms.
#### **Connecting Jira Data Center/Server**
Unlike the cloud, the data center will not require a token but can work with an email and a password. If you chose to use the token, leave the **email** option blank in the Getint platform:
* Log in to your Jira Data Center instance.
* Click on the Avatar on the top right of the screen.
* Select **Profile** and then **Personal Access Tokens**.
* Click on **Create Token**, provide a name for your token, and select if this token will expire and when.
* Copy the token and ensure it is stored securely in a safe location.
{% embed url="" %}
#### **Jira Service Management**
Jira also has the Jira Service Management option for service tasks and projects. This can also be integrated and will use a Personal Token as a Password:
* Log in to your Jira instance.
* Click on the Avatar on the top right of the screen.
* Select **Profile** and then **Personal Access Tokens**.
* Click on **Create Token**, provide a name for your token, and select if this token will expire and when.
* Copy the token and ensure it is stored securely in a safe location.
Connect as you would for a Jira Cloud, Server, or Data Center, depending on your type of access.
{% hint style="info" %}
The permission level of personal access tokens in the Data Center is set to the level of access you currently have.
{% endhint %}
### **Airtable**
To ensure seamless synchronization with Airtable, it is crucial to generate an access token with all the necessary scopes highlighted below:
* Click on your profile icon and navigate to the **Account** section.
* Choose the **Builder Hub** subsection, then select **Personal Access Tokens**.
* Press the **Create New Token** button.
* Name your token and select the appropriate scopes.
* Specify which team the token would give access to.
* Press create and ensure to store it securely in a safe location.
#### Video Tutorial
{% embed url="" %}
### **Asana**
Generating an Asana Token:
* Log in to your Asana account.
* Click on your profile picture and go to **Settings**.
* Select the **Apps** tab, scroll down to **Build new apps**, click **View developer console**.
* Click **Create new token**, provide a description, and create the token.
* Copy and securely store the token.
{% embed url="" %}
### **Azure DevOps**
If you want to integrate Azure DevOps (ADO) with your Server or Cloud, you must provide a token with the necessary permissions. Follow the steps below to generate a token:
* Log in to your **Azure DevOps** organization.
* Open **User Settings** from the profile menu.
* Select **Personal Access Tokens** from the left sidebar.
* Click **New Token** and enter a name for the token.
* Set the expiration for the token and select the appropriate scopes:
* **Work Items** - Read & Write
* **Project and Team** - Read & Write
* **Graph** - Read (graph permission is necessary to ensure accurate user data retrieval)
* **Code** - Read (if you're syncing repositories with the Git Connector)
* Click **Create**, then copy and securely store the generated token. This token will authenticate and authorize Getint to access your Azure DevOps organization.
* When configuring the Azure DevOps connection details in Getint, provide the generated token as the **password**.
{% embed url="" %}
### **ClickUp**
To connect to ClickUp, enter your personal API token into the API TOKEN field. Any ClickUp user, including team members and guests, can generate this token within their account settings.
#### Steps to Generate a ClickUp API Token
1. Log in to your ClickUp account.
2. Click on your profile picture.
3. Select **Settings**.
4. Click on **ClickUp API** in the left-hand menu.
5. Generate your access token.
{% embed url="" %}
### **Freshdesk**
To sync your Freshdesk tickets, calls, and other details, you'll need to authenticate Getint with your Freshdesk API key. Follow these steps:
1. Log in to your Freshdesk account.
2. Click your profile picture in the top right corner and select **Profile Settings**.
3. In the right-hand sidebar, click **View API Key**. Complete the captcha verification if prompted.
4. Copy the **API key**.
5. Paste the key into Getint to authenticate the integration.
If you ever need to deauthorize an app from connecting to your helpdesk, you can reset the API key. Keep in mind that resetting it disconnects every other app using that key as well, so you'll need to supply the new key to each of those apps before they can resume working.
**Set the Correct Instance URL**
Freshdesk lets you customize your instance URL, but Getint can only establish the connection using your primary (original) URL.
For example, your current URL might be `https://support.getint.io`, while your original URL was `https://help-getint.io`. In that case, enter the original URL (`https://help-getint.io`) when configuring the connection.
{% embed url="" %}
### **Freshservice**
* To retrieve your API key, log in to Freshservice and click your profile icon in the upper-right corner to access **Profile Settings**. On the following page, select **Show API Key**, complete the security captcha if required, and copy the key for your integration.
{% embed url="" %}
### **GitHub**
Like other platforms, you can generate a Personal Access Token in GitHub to facilitate integration with external tools and platforms. However, the app is now offering a beta version that can also be used:
#### **Generating a GitHub Token (Classic):**
* Log in to your GitHub account.
* Go to **Settings**, then **Developer settings**.
* Select **Personal access tokens** and select **Generate new token**. In the dropdown menu, select **Generate new Token (Classic)**.
* On the screen that will appear, provide a name for your Token.
* Select the scopes like the example below, and save:
* Copy and securely store the token.
#### **Video Tutorial for Token (Classic)**
{% embed url="" %}
#### **Generating a Fine-Grained Token:**
* Log in to your GitHub account.
* Go to **Settings**, then **Developer settings**.
* Select **Personal Access Tokens**, then go to **Fine-grained personal access Tokens**.
* Click on Generate New Token. Choose a name for your Token, set the expiration date and repository access, and provide the necessary access permissions in the dropdown list.
#### **Video Tutorial for Fine-Grained Token**
{% embed url="" %}
### **GitLab**
#### **Generating a GitLab Token:**
GitLab offers a comprehensive platform for version control, collaboration, and continuous integration. You can generate a Personal Access Token to enable integration with other applications:
1. Log in to your GitLab account.
2. Click your avatar or profile picture in the top-left or top-right corner (depending on your GitLab version), then select **Preferences**.
3. In the left sidebar, navigate to the **Access** section (typically near the top) and select **Personal access tokens**.
4. Click **Generate token** to open the form, and ensure you select **Legacy token** or **Fine-grained Token**.
For more information about permissions, watch the video tutorials below:
#### **GitLab Legacy Token Tutorial**
{% embed url="" %}
#### **GitLab Fine-grained Token Tutorial**
{% embed url="" %}
### **HubSpot**
To connect with the HubSpot app, the user must provide an API token from a Private App. Only API Tokens are supported at the moment. To create a Private App:
* Log in to your HubSpot account, and click on your initials in the top right corner.
* Select **Profile and Preferences** and then navigate to **Integrations** > **Private Apps**.
* Click **Create a Private App**.
* On the Basic Info tab, provide a name for your App and then select **Scopes**:
* After you're done configuring your app, click **Create app** on the top right.
{% embed url="" %}
### **Monday.com**
Generating a Monday.com Token:
* Log in to Monday.com, click on your initials in the top right corner, and navigate to Administration.
* On the next screen, select **API** and regenerate the token.
* Copy the Personal Access token, then continue your integration setup following the guide provided for [Jira Monday.com integration](https://docs.getint.io/guides/integration-synchronization/jira-monday-integration).
{% embed url="" %}
### **Notion**
Integrating Notion with Getint allows you to synchronize your project management tasks seamlessly across platforms. Below is a detailed guide on how to connect Getint with Notion:
* In the Notion app, click on the three dots in the top right corner, then select **Connections** and navigate to **Manage Connections**. Choose **Develop or manage connections**.
* Select **Create a new connection**, provide a name for your connection, and grant the necessary permissions.
* Scroll up to **Content access**, and edit the access for the token. Ensure to select the appropriate workspaces you would like to integrate.
* Save the changes, and copy the generated API token.
{% embed url="" %}
### **Salesforce**
To connect with Salesforce, users must grant permissions to Getint via the OAuth authentication method. These credentials are securely stored in a dedicated Getint database and are used exclusively by that user. Follow the steps below to create a new connection between Getint and your Salesforce instance:
1. Sign in to your Salesforce account, then click the **Cog** icon in the upper-right corner of the screen. From there, select **Setup** to access your user settings.
2. Navigate to **Platform Tools**, then select **Apps**. From there, go to **External Client Apps** and open the **External Client App Manager**.
3. Select **New External Client App** to create a new application.
4. Enter a unique name, your email address, and the API name.
5. **Enable OAuth**:
* Turn on **OAuth** by scrolling down and enabling it.
* Enter the **Callback URL**: `https://login.salesforce.com/services/oauth2/callback`.
* Choose the required **OAuth Scope: Manage user data via APIs (API)**.
{% hint style="info" %}
Salesforce mandates the use of HTTPS for the Callback URL to ensure secure communication.
{% endhint %}
6. Scroll down to the **Flow Enablement** section and activate the **Client Credentials Flow**. After that, turn off all other options in the **Security** section.
7. **Create the External Client App**:
* Click **Create** at the bottom of the page.
* Once the app is created, go back to edit its settings. You should see the new client listed.
8. **Edit Settings for the new Client**:
* Select **Edit** to access the settings.
* Open the section for **OAuth Policies**.
9. Enable **Client Credentials Flow** and enter the username found under **Personal Information** in your profile. Click **Save** at the bottom of the page to apply your changes.
10. **Generate** `client_id` **and** `client_secret`**:**
* Go to the **Settings** tab from the **Policies** tab.
* Select "**Consumer Key and Secret**" to proceed.
* You’ll be redirected to a verification screen.
* Copy the **Consumer Key** **(client\_id)** and **Consumer Secret** **(client\_secret)** for future use.
Using these credentials, you're ready to establish a connection with Salesforce in Getint.
11. **Create a Salesforce Connection in Getint**:
* Choose **Salesforce** and click **Create a Connection**.
* Enter your Salesforce Instance URL in the **URL** field and click **Next**.
* Give the connection a name and input the **client\_id** and **client\_secret**.
* Add the connection, then select it to complete the setup.
{% hint style="warning" %}
Make sure to use the correct URLs to connect to your instance:
* `https://YOUR_INSTANCE_NAME.develop.lightning.force.com`
* `https://YOUR_INSTANCE_NAME.develop.my.salesforce.com`
Salesforce has several editions, including Enterprise, Unlimited, Performance, Developer, Group, Essentials, and Professional. The API is automatically enabled in Enterprise, Unlimited, Performance, and Developer editions. For Group, Essentials, and Professional editions, the API is not enabled by default.
If you run into issues or can't find the API option, reach out to the Help and Training Community or contact our support team through the [support portal.](https://getint.io/help-center)
{% endhint %}
### **ServiceNow**
Integration involves providing connection details like instance URLs and credentials or API tokens to enable seamless communication with other applications. The ServiceNow will require the creation of a special user, as shown in [Creating a ServiceNow User for Getint Integration](https://docs.getint.io/guides/integration-synchronization/jira-servicenow-integration/creating-a-servicenow-user-for-getint-integration).
**Set Up ServiceNow Connection**
* Click CONNECT APP, and then click ServiceNow.
* Input the URL of your ServiceNow instance you want to connect to, and click **Next**.
* In the next screen, provide the name for the connection, username, and password for the ServiceNow account.
* Click **Add** to set up the connection.
{% embed url="" %}
{% hint style="warning" %}
You will get an **insufficient permissions** or **user cannot be authenticated** error if you haven't created the ServiceNow user.
{% endhint %}
### **Trello**
Trello is part of the Atlassian environment. Being linked to your Atlassian, the user creating the connection must have access to the project and admin permissions to enable the connection.
* In the Getint app, select **Trello** and **Create a new connection**.
* Name your connections, select **Authorize Getint**, review the permissions, and accept.
* Select the project that you want to sync and select **Connect**.
* Choose the connection you just created and press connect. Continue your integration setup following the guide provided for [Jira Trello](https://docs.getint.io/getting-started-with-the-platform/integration-synchronization/jira-trello-integration) integration.
{% embed url="" %}
### **Wrike**
Generating a Wrike Token:
* Log in to your Wrike account.
* Click on your initials on the top right of the page, select **Apps & Integrations**, then go to **API**.
* On the API tab, add a name for your Token in the **App Name** field and click **Create New**.
* Scroll down to the bottom of the page and under **Permanent Access Token**, select **Create Token**.
* Add your Wrike password and click on **Obtain token**. Then select **Copy Token**.
{% embed url="" %}
### **Zendesk**
Connecting with Zendesk requires API access, which is configured in the Admin Center. Two authentication methods are supported: **API Token** and **OAuth**.
{% hint style="warning" %}
Zendesk is removing API tokens as an authentication method for the Ticketing, Help Center, and Voice APIs. The rollout happens in three phases:
* **July 28, 2026**: tokens unused for 30 days or more are deactivated automatically. Accounts created on or after this date cannot create API tokens.
* **October 27, 2026**: no account can create new API tokens. Existing active tokens keep working.
* **April 30, 2027**: all remaining API tokens stop working permanently and cannot be reactivated.
API tokens still work for Getint connections today, and both methods can run in parallel until the final date. If you are creating a new Zendesk connection, use OAuth. For details, see [Zendesk's announcement](https://support.zendesk.com/hc/en-us/articles/10851263566234-Announcing-the-removal-of-API-tokens-as-an-authentication-method-for-API-requests).
{% endhint %}
#### Zendesk - API Token
* Sign in to your Zendesk account, click the dropdown menu next to the Zendesk logo in the upper-left corner, and select **Admin Center**.
* In the Admin Center, navigate to **Apps and Integrations** from the left-hand menu, then choose **API Tokens** from the secondary menu.
* Accept the agreement by selecting the checkbox and clicking **Get Started**. On the following page, click **Add API Token**, enter a name for the token, and save your changes. The API token will be generated once saved.
* After the token is created, open **API Configuration** from the secondary menu and enable the **Allow API Token Access** option.
#### Video Tutorial for API Token
{% embed url="" %}
#### Zendesk - OAuth
To connect with OAuth, you register an OAuth client in your Zendesk Admin Center and copy two values into Getint: the **unique identifier** and the **secret**.
{% hint style="info" %}
You need administrator permissions in your Zendesk instance to create an OAuth client. The **Secret** value is displayed in full only once, right after you save the client.
{% endhint %}
* Sign in to your Zendesk account, click the dropdown menu next to the Zendesk logo in the upper-left corner, and select **Admin Center**.
* In the sidebar, click **Apps and integrations**, then select **APIs** > **OAuth clients**.
* Click **Add OAuth client** on the right side of the OAuth client list.
* Complete the client details:
* **Client name**: the name users see when they are asked to grant access.
* **Description**: optional short description of the client.
* **Company**: optional company name shown on the authorization screen.
* **Unique identifier**: auto-filled from the client name and editable. This is the value Getint asks for as the client ID, so copy it exactly as displayed.
* **Client kind**: select **Confidential**.
* **Redirect URLs**: enter the callback URL. The URL must be absolute and use HTTPS.
* **Scopes**: select **read** and **write**. Leaving the field empty allows all scopes.
* Click **Save**. The page refreshes, and a **Secret** field appears at the bottom of the form with the generated value.
* Copy the **Secret** and store it in a safe location. The characters may extend past the width of the field, so select the full value before copying.
* Click **Save** again to return to the OAuth client list.
* In Getint, select **Zendesk** and create a new connection. Enter your Zendesk instance URL, name the connection, and paste the **unique identifier** and the **secret**.
#### **Video Tutorial for OAuth**
{% embed url="" %}
{% hint style="info" %}
If you have any questions or need assistance, please do not hesitate to contact us at our [Help Center](https://getint.io/help-center) or [Schedule a Demo](https://calendly.com/d/cpws-jb2-8xx/demo-call-all-team).
{% endhint %}
# Integration Overview
An integration connects **two applications** and defines how items are synced between them. Each integration has its own configuration, mappings, filters, and execution rules. This page explains how integrations are structured and how they work behind the scenes.
### **Integration Sections**
Each integration contains several configuration areas:
#### **Applications Icons**
Displays the two applications connected by this integration.
It is also possible to change the connection and use a Query or JQL for advanced filtering by clicking the icons. See the documentation:[ Filtering Items for Integration in Getint](https://docs.getint.io/getintio-platform/workflows/filtering-items-for-integration-in-getint) and [How to Use JQL Filters for Jira Integrations](https://docs.getint.io/getintio-platform/workflows/how-to-use-jql-filters-for-jira-integrations).
#### **More**
Here, you can access and control the integration interval between runs (Onpremise and Data Center deployments), the trigger behavior, ownership, and other execution rules. You can also disable the integration and export it.
Under this section, you will also find **Advanced Configuration.** It includes scripting options and advanced logic for cases that require customization. You can discover more about [Advanced Scripting](https://docs.getint.io/getintio-platform/advanced-scripting) or [contact us](https://getintio.atlassian.net/servicedesk/customer/portals) for help.
#### **Items Filtering**
Allows you to filter which items should be synced.
You can include or exclude items based on fields, conditions, or specific values. For more details on how to use the filters, check our documentation: [Filtering Items for Integration in Getint](https://docs.getint.io/getintio-platform/workflows/filtering-items-for-integration-in-getint).
#### **Integration Name**
If a name is not provided, Getint will give it a generic name with the creation date when selecting "Create." The name can be changed at any time.
Here you can also see the status, integration owner, the date of creation, and the access it was given.
#### **Type Mapping**
Defines how item types from one application translate into work item types in the other.
Within Type Mapping, you can:
* **Map work item types** between both applications.
* **Copy configuration** to reuse the same mapping settings.
* **Disable** a mapping without removing it.
* **Access to edit** the field mappings.
* **Delete** a mapping.
#### **Migration Configuration**
Used when migrating existing or legacy items between applications. See more about migration options and configurations on our guides: [Migration Guides](https://docs.getint.io/guides/migration).
## **Structure of an Integration**
Integrations are built around **Type Mappings**.
A type mapping tells Getint how to translate a Work Item type from one system when it’s created or updated in the other.
**Example**
Jira might use (not limited to):
* Task
* Bug
* Story
Azure might use (not limited to):
* Task
* User Story
* Issue
If you want an *Issue* in Azure to create a *Bug* in Jira, you simply map **Issue → Bug**.
Work items that are **not** included in any mapping will **not** be synced.
Here, you can also use the [**Quick Build**](https://docs.getint.io/getintio-platform/quick-build) to facilitate the mapping of work items and fields, map [dependencies](https://docs.getint.io/guides/integration-synchronization/jira-azure-devops-integration/syncing-dependencies-between-jira-and-azure-devops-using-getint), and [manage the fields](https://docs.getint.io/guides/integration-synchronization/how-to-map-fields).
### **Mapping Multiple Types Into One**
You can map several item types on one side into a single type on the other.
Example:
* Jira *Bug*, *Task*, and *Story* → *Azure Issue*
When Azure needs to create the corresponding Issue, Getint uses the **first matching work item type** from the top of your mapping list.
## **How Integrations Run**
Integrations run automatically based on the interval defined in **Settings** (For Cloud users, the minimum interval is 180 seconds).
Here’s how the execution works:
1. Getint checks the integration run interval in Settings.
2. When the scheduled time is reached, the integration starts.
3. For each connected application, Getint looks for all changes since the **last run**.
4. Only items that match your Type Mappings, Filtering Rules, and Sync Logic are processed.
5. Each execution is logged and can be viewed in **Reporting → Runs**.
This provides a clear record of what happened, when it occurred, and which items were synced.
### **Need Help?**
If you have questions while setting up your integration, or if something doesn’t behave the way you expect, feel free to reach out. Our support team is happy to help you troubleshoot, review your configuration, or point you in the right direction. Contact us directly through our [help page](https://getintio.atlassian.net/servicedesk/customer/portals).
# Integration Guides
# Git Repository integration
With the integration of Git, repository management becomes highly practical and efficient. We currently support integration with Azure DevOps, GitLab, and GitHub. Whether you're merging branches, tracking changes, or rolling back to previous versions, you can track all these changes seamlessly within your Jira instance. This integration allows you to easily track **repositories**, **branches**, **commits**, and **pull requests**.
Our Git integration app for Jira is available at the following link: [Git Connector for Jira.](https://marketplace.atlassian.com/apps/1236406/git-connector-for-jira-azure-devops-github-gitlab?hosting=cloud\&tab=overview)
{% hint style="warning" %}
While it is possible to create a Git integration using other integration apps, it is mandatory to have the Git Connector app installed.
{% endhint %}
### How to Build a Git Integration
#### 1. Launch the Getint App:
* Navigate to **Apps**, launch the app **Git Connector for Jira**, go to **Integrations**, click **Create Integration**, and select **Sync GIT Repository**.
* If you’re using Getint On-Premise, simply launch the app, click **Create Integration**, and select **GIT**.
#### 2. Create a Connection for the App Containing the Git Repository:
* Select the app you want to integrate by clicking the **Connect App** button.
* Create a connection or select an existing one.
* Follow the next steps depending on the app you selected. We’re taking GitLab as an example, but the process is the same for the rest of the connectors.
* Once you've added your details, you'll find your new connection in the dropdown list of available connections. Please select it and click **Connect** to complete the process.
{% hint style="info" %}
For detailed instructions on creating a connection and generating an access token, please refer to our comprehensive guide: [Connections | Tokens and Requirements](https://docs.getint.io/guides/quickstart/connection).
{% endhint %}
#### 3. Establish a Connection with Jira:
* Make sure you are logged in with admin rights, then click on **Connect App** and select **Jira**. Choose **Create New** to establish a fresh connection with your Jira instance and enter the URL of your Jira instance.
* Unlike **Continuous Syncs** or **Migrations**, GIT integrations require users to set up OAuth in their Jira instance. Please ensure you have admin permissions; otherwise, you will not be able to set up the OAuth credentials. Then, follow our guide to configure a Jira OAuth at the following: [Connection | Jira OAuth.](https://docs.getint.io/guides/quickstart/connection#jira-cloud-oauth)
* Enter the necessary details to establish the connection.
* Once you've added your details, you'll find your new connection in the dropdown list of available connections. Please select it and click **Connect** to complete the process.
#### 4. Building Your Integration:
* By default, the Git repositories will sync with all projects in your Jira instance. However, unchecking this option allows you to select one or multiple projects where you want this information to be available.
* For example, you can select specific projects based on your company’s needs. Next, choose the Git repositories you want to sync. Finally, name your integration and click **Create** at the top right corner of the screen to save it.
* Once you've created your integration, it will be easily accessible in the **Integrations** section within Workflows, and it is marked with a code icon.
* If you did not install the Git Connector app as instructed at the beginning of the article, you will encounter an error like the one shown below:
#### 5. Test the Integration and Sync Your Branches
* To start syncing branches, ensure that you use the ID of the Jira task as a prefix for the branch names. For branch names, only underscores or dashes can be used instead of spaces. For example **ED-23-resolve-support-ticket-9843-migrate**.
* For example, if you’re syncing an item with the Jira ID **ED-23**, your branch should be named **ED-23 + branch name**, as shown below:
Example of proper branch naming for synchronization. Using GitHub as an example, the same principle applies to the other connectors.
* If the correct naming prefix is not used to sync your items, an error like the one below will occur:
* The Git repository details of your Jira items will be available in the Development field. Refresh the page if you don’t see any changes to the Development field.
{% hint style="warning" %}
Depending on your Project template, the Development field may not be visible. In such cases, you must either add the field by modifying the issue layout or switch to a different template.
{% endhint %}
* By clicking on this field, you can easily access all the information that is being collected from the repositories.
{% hint style="info" %}
Getint enables the synchronization of Repositories, Branches, Commits, and Pull Requests. However, please note that changes cannot be submitted from Jira to the Git repository. The synchronization of repository information is one-way from the Git connector.
{% endhint %}
### Conclusion
With this comprehensive guide, you can seamlessly integrate Git with Jira and take full advantage of efficient repository management. If you require any assistance or have further questions, don't hesitate to contact us [here](https://getint.io/help-center).
# Git Connector - Azure DevOps
With the integration of Git, repository management becomes highly practical and efficient. We currently support integration with Azure DevOps. Whether you're merging branches, tracking changes, or rolling back to previous versions, you can track all these changes seamlessly within your Jira instance. This integration lets you easily track **repositories**, **branches**, **commits**, and **pull requests**.
Our Git integration app for Jira is available at the following link: [Git Connector for Jira.](https://marketplace.atlassian.com/apps/1236406/git-connector-for-jira-azure-devops-github-gitlab?hosting=cloud\&tab=overview)
{% hint style="warning" %}
While it is possible to create a Git integration using the Azure DevOps integration app, it is mandatory to have the Git Connector app installed.
{% endhint %}
### How to Build a Git Integration for Azure DevOps
#### 1. Launch the Getint App:
* Navigate to **Apps**, launch the app **Git Connector for Jira**, go to **Integrations**, click **Create Integration**, and select **Sync GIT Repository**.
* If you’re using Getint On-Premise, simply launch the app, click **Create Integration**, and select **GIT**.
#### 2. Create a Connection with Azure DevOps:
* Click the **Connect App** button, and select **Azure DevOps**.
* Create a connection or select an existing one.
* Tap on **Create a new connection** if you don’t have an existing one.
* Enter your instance URL, and click on **Connect**.
* Name the connection, input your email, and paste the token generated (create the personal access token following the instructions in this guide: [Connections](https://docs.getint.io/guides/quickstart/connection#azure-devops)). Then click **Add**.
* Once you've added your details, you'll find your new connection in the dropdown list of available connections. Please select it and click **Connect** to complete the process.
{% hint style="warning" %}
For Git Azure DevOps integrations, it is important to set the scope **Code** to **Read**. Otherwise, you’ll get the following error:
*Unfortunately, your integration failed to save due to the following reason: Forbidden.*
{% endhint %}
#### 3. Establish a Connection with Jira:
* Ensure that you are logged in with administrative rights, then click on **Connect App** and select **Jira**. Click on **Create New** to set up a new connection with your Jira instance and enter the URL of your Jira instance.
* Unlike **Continuous Syncs** or **Migrations**, GIT integrations require users to set up OAuth in your Jira instance. Please ensure you have admin permissions; otherwise, you will not be able to set up the OAuth credentials. Then, follow our guide to configure a Jira OAuth at the following: [Connection | Jira OAuth.](https://docs.getint.io/guides/quickstart/connection#jira-cloud-oauth)
* Enter the necessary details to establish the connection.
* After entering your details, your new connection will appear in the dropdown list of available connections. Please select it and click **Connect** to finalize the setup.
#### 4. Building Your Integration:
* By default, the Git repositories will synchronize with all projects in your Jira instance. However, if you uncheck this option, you can choose one or multiple projects where you want this information to be accessible.
* For instance, you can choose specific projects according to your company's requirements. Then, select the Git repositories you wish to synchronize. Lastly, give your integration a name and click **Create** at the top right corner of the screen to save it.
* After creating your integration, it will be readily available in the Integrations section within Workflows, identified by a code icon.
* If you did not install the Git Connector app as instructed at the beginning of the article, you will encounter an error like the one shown below:
#### 5. Test the Integration and Sync Your Branches
* To start syncing branches, use the Jira task ID as a prefix for the branch, commit, and pull request names. For branch names, only underscores or dashes can be used instead of spaces. For example **ED-32\_Energy\_Dot**.
* For instance, if you are syncing an item with the Jira ID **ED-32**, your branch should be named **ED-32** followed by the branch name, as shown below:
Example of proper branch naming for synchronization.
* If you fail to use the correct naming prefix to sync your items, you will encounter an error similar to the one shown below:
* The Git repository details of your Jira items will be available in the Development field. Refresh the page if you don’t see any changes to the Development field.
{% hint style="warning" %}
Depending on your Project template, the Development field may not be visible. In such cases, you must either add the field by modifying the issue layout or switch to a different template.
{% endhint %}
* Clicking on this field allows you to effortlessly access all the information being fetched from the repositories.
{% hint style="info" %}
Getint enables the synchronization of Repositories, Branches, Commits, and Pull Requests. However, please note that changes cannot be submitted from Jira to the Git repository. The synchronization of repository information is one-way from Azure DevOps.
{% endhint %}
### Conclusion
By following this detailed guide, you can effortlessly integrate Azure DevOps repositories with Jira and fully leverage efficient repository management. Should you need any assistance or have additional questions, please feel free to contact us here.
# Git Connector - GitHub
Effortlessly sync your GitHub repositories with Jira using our in-depth guide. This comprehensive resource helps your team track changes, manage issues, and collaborate effectively.
We guide you through every step, from setting up the integration to configuring OAuth credentials and ensuring smooth data synchronization. As of now, we support syncing repositories, branches, commits, and pull requests. Discover how to link your GitHub repositories to Jira projects, enabling you to monitor branches, commits, and pull requests directly within Jira. This guide will show you how to combine the strengths of GitHub and Jira to optimize your workflow, boost visibility, and enhance productivity.
Access our Git integration app for Jira through this link: [Git Connector.](https://marketplace.atlassian.com/apps/1236406/git-connector-for-jira-azure-devops-github-gitlab?hosting=cloud\&tab=overview)
{% hint style="warning" %}
The Git Connector app is not required if you're using the GitHub integration app.
{% endhint %}
### How to Build a Git Integration for GitHub
#### 1. Launch the Getint App:
* Go to **Apps**, open the Git Connector for Jira app, navigate to **Integrations**, click **Create Integration**, and choose **Sync GIT Repository**.
* If you’re using Getint On-Premise, simply open the app, click **Create Integration**, and choose **Sync GIT Repository**.
#### 2. Create a Connection with GitHub:
* Click the **Connect App** button, and select **GitHub**.
* Create a connection or select an existing one.
* Tap on **Create a new connection** if you don’t have an existing one.
* Name the connection, and paste the token generated (create the personal access token following the instructions in this guide: [Connections](https://docs.getint.io/guides/quickstart/connection#github)). Then click **Add**.
* Once you've added your details, you'll find your new connection in the dropdown list of available connections. Please select it and click **Connect** to complete the process.
#### 3. Establish a Connection with Jira:
* Ensure that you are logged in with administrative rights, then click on **Connect App** and select **Jira**. Click on **Create New** to set up a new connection with your Jira instance and enter the URL of your Jira instance.
* Unlike **Continuous Syncs** or **Migrations**, GIT integrations require users to set up OAuth in your Jira instance. Please ensure you have admin permissions; otherwise, you will not be able to set up the OAuth credentials. Then, follow our guide to configure a Jira OAuth at the following: [Connection | Jira OAuth.](https://docs.getint.io/guides/quickstart/connection#jira-cloud-oauth)
* Enter the necessary details to establish the connection.
* After entering your details, your new connection will appear in the dropdown list of available connections. Please select it and click **Connect** to finalize the setup.
#### 4. Building Your Integration:
* By default, the Git repositories will automatically synchronize with all projects in your Jira instance. However, if you disable this option, you can specify one or multiple projects where this information should be available.
* For example, you can pick particular projects based on your company's needs. Next, identify the Git repositories you want to sync. Finally, name your integration and click **Create** in the top right corner of the screen to save it.
* After creating your integration, it will be readily available in the Integrations section within Workflows, identified by a code icon.
* If you did not install the Git Connector app as instructed at the beginning of the article, you will encounter an error like the one shown below:
#### 5. Test the Integration and Sync Your Branches
* To start syncing items, use the Jira task ID as a prefix for the branch, commit, and pull request names. For branch names, only underscores or dashes can be used instead of spaces. For example **ED-34**\_**New\_branch**.
* For instance, if you are syncing an item with the Jira ID **ED-34**, your branch should be named **ED-34** followed by the branch name, as shown below:
* If you fail to use the correct naming prefix for branches and commits, you will encounter an error similar to the one shown below:
* The Git repository details of your Jira items will be available in the Development field. Refresh the page if you don’t see any changes to the Development field.
{% hint style="warning" %}
Depending on your Project template, the Development field may not be visible. In such cases, you must either add the field by modifying the issue layout or switch to a different template.
{% endhint %}
* Clicking on this field allows you to effortlessly access all the information being fetched from the repositories.
{% hint style="info" %}
Getint enables the synchronization of Repositories, Branches, Commits, and Pull Requests. However, please note that changes cannot be submitted from Jira to the Git repository. The synchronization of repository information is one-way from GitHub.
{% endhint %}
### Conclusion
With this comprehensive guide at your disposal, you can seamlessly integrate GitHub repositories with Jira and unlock the full potential of efficient repository management. If you need any help or have any questions along the way, don't hesitate to reach out to us here.
# Git Connector - GitLab
This article provides a comprehensive guide on how to sync GitLab repositories with Jira, allowing teams to track changes, manage issues, and collaborate more effectively.
We cover everything from setting up the integration to configuring OAuth credentials and ensuring smooth data synchronization. Learn how to link your GitLab repositories to Jira projects, enabling you to monitor branches, commits, and pull requests directly within Jira. By following this guide, you can leverage the combined power of GitLab and Jira to streamline your workflow, enhance visibility, and improve productivity.
You can access our Git integration app for Jira using the following link: [Git Connector.](https://marketplace.atlassian.com/apps/1236406/git-connector-for-jira-azure-devops-github-gitlab?hosting=cloud\&tab=overview)
{% hint style="warning" %}
The Git Connector app is not required if you're using the GitLab integration app.
{% endhint %}
### How to Build a Git Integration for GitLab
#### 1. Launch the Getint App:
* Go to **Apps**, open the Git Connector for Jira app, navigate to **Integrations**, click **Create Integration**, and choose **GIT**.
* If you’re using Getint On-Premise, simply open the app, click **Create Integration**, and choose **Sync GIT Repository**.
#### 2. Create a Connection with GitLab:
* Click the **Connect App** button, and select **GitLab**.
* Create a connection or select an existing one.
* Tap on **Create a new connection** if you don’t have an existing one.
* Enter your instance URL, and click on **Connect**. Do NOT provide a URL if you are using GitLab Cloud.
* Name the connection, and paste the token generated (create the personal access token following the instructions in this guide: [Connections](https://docs.getint.io/guides/quickstart/connection#gitlab)). Then click **Add**.
* Once you've added your details, you'll find your new connection in the dropdown list of available connections. Please select it and click **Connect** to complete the process.
#### 3. Establish a Connection with Jira:
* Ensure that you are logged in with administrative rights, then click on **Connect App** and select **Jira**. Click on **Create New** to set up a new connection with your Jira instance and enter the URL of your Jira instance.
* Unlike **Continuous Syncs** or **Migrations**, GIT integrations require users to set up OAuth in your Jira instance. Please ensure you have admin permissions; otherwise, you will not be able to set up the OAuth credentials. Then, follow our guide to configure a Jira OAuth at the following: [Connection | Jira OAuth.](https://docs.getint.io/guides/quickstart/connection#jira-cloud-oauth)
* Enter the necessary details to establish the connection.
* After entering your details, your new connection will appear in the dropdown list of available connections. Please select it and click **Connect** to finalize the setup.
#### 4. Building Your Integration:
* By default, the Git repositories will automatically synchronize with all projects in your Jira instance. However, if you disable this option, you can specify one or multiple projects where this information should be available.
* For example, you can pick particular projects based on your company's needs. Next, identify the Git repositories you want to sync. Finally, name your integration and click **Create** in the top right corner of the screen to save it.
* After creating your integration, it will be readily available in the Integrations section within Workflows, identified by a code icon.
* If you did not install the Git Connector app as instructed at the beginning of the article, you will encounter an error like the one shown below:
#### 5. Test the Integration and Sync Your Branches
* To start syncing branches, use the Jira task ID as a prefix for the branch, commit, and pull request names. For branch names, only underscores or dashes can be used instead of spaces. For example **ED-33**\_**feature\_user\_authentication**.
* For instance, if you are syncing an item with the Jira ID **ED-33**, your branch should be named **ED-33** followed by the branch name, as shown below:
* If you fail to use the correct naming prefix for branches and commits, you will encounter an error similar to the one shown below:
* The GitLab repository details of your Jira items will be available in the Development field. Refresh the page if you don’t see any changes to this field.
{% hint style="info" %}
Depending on your Project template, the Development field may not be visible. In such cases, you must either add the field by modifying the issue layout or switch to a different template.
{% endhint %}
* Clicking on this field allows you to effortlessly access all the information fetched from the GitLab Repository.
{% hint style="info" %}
Getint enables the synchronization of Repositories, Branches, Commits, and Pull Requests. However, please note that changes cannot be submitted from Jira to the Git repository. The synchronization of repository information is one-way from GitLab.
{% endhint %}
### Conclusion
With this comprehensive guide at your disposal, you can seamlessly integrate GitLab repositories with Jira and unlock the full potential of efficient repository management. If you need any help or have any questions along the way, don't hesitate to reach out to us here.
# Non-Jira Connectors
## Building a Non-Jira Integration
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
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
The Getint licensing model for non-Jira connectors focuses on predictable costs and scalability:
#### Standard Licensing
* 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
* 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
* **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
#### 1. Access the Getint App
* 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
* 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
* 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
* 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
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
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
* 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
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
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
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
* 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
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
* 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
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).
# Asana Azure DevOps integration
## Integrating Asana and Azure DevOps
Connecting Asana with Azure DevOps synchronizes project management data with development records, keeping business and engineering teams aligned. This integration automates updates between platforms in real time, removing manual data entry and reducing the risk of cross-departmental discrepancies across tasks, statuses, and project data.
### Asana Azure DevOps Licensing Model
The Getint licensing model for Asana and Azure DevOps focuses on predictable costs and scalability:
#### Standard Licensing
* This tier covers a direct integration between one Asana instance and one Azure DevOps 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
* Designed for managed service providers or large organizations, this option supports three or more instances. It allows for a specific number of connections (e.g., up to 10 instances) 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:
* **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**: Both Asana and Azure DevOps require Personal Access Tokens to establish a secure connection. You can find the steps to generate the access token for your connectors here: [Connection Guide](https://docs.getint.io/guides/quickstart/connection#asana).
* **Service Accounts**: Because the integration attributes comments to the user who created the connection, we recommend using dedicated Service Accounts for both instances to maintain a clear distinction between automated updates and individual user activity.
### Setting Up Your Asana Azure DevOps Integration
#### 1. Access the Getint App
* 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.
#### 2. Create an Integration
* Go to **Workflows** (lightning bolt icon) and click **Create Integration**. From this menu, select **Continuous Sync** or **Data Migration**.
#### 3. Generate an Asana Personal Access Token
* Log in to Asana and follow the video below to generate your Access Token.
{% embed url="" %}
* Make sure to securely store your token, as it will only be visible once.
#### 4. Generate an Azure DevOps Token
To integrate Azure DevOps (Server or Cloud), you must provide a token with the necessary permissions. Follow the steps below to generate one:
* Log in to your Azure DevOps organization.
* Open **User Settings** from the profile menu.
* Select **Personal Access Tokens** from the left sidebar.
* Click **New Token** and enter a name for the token.
* Set the expiration and select the appropriate scopes:
* **Work Items**: Read & Write
* **Project and Team**: Read & Write
* **Graph**: Read (required for accurate user data retrieval)
* **Code**: Read (if you're syncing repositories with the Git Connector)
* Click **Create**, then copy and securely store the generated token. This token authenticates and authorizes Getint to access your Azure DevOps organization.
* When configuring the Azure DevOps connection details in Getint, provide the generated token as the password.
{% embed url="" %}
#### 5. Connect to Asana
* In Getint, click on **Connect App** and choose Asana. Enter your Access Token for Asana.
* Once the connection is established, choose the workspace and project(s) you want to integrate with Asana from the dropdown menu.
* Click **Connect** to establish the connection.
#### 6. Connect to Azure DevOps
* Click on **Connect App** and choose Azure DevOps, then select **Create a new connection**. Enter the URL for the connection and click **Next**.
* Provide a name for the connection, enter your email, and paste the token generated in the previous steps. Click **Add** to complete.
* Once the connection is established, select the Azure DevOps project(s) you want to synchronize from the dropdown menu and click **Connect**.
#### 7. Configure Type Mapping
* **Quick Build**: Automatically map fields and types between applications with this feature.
* **Manual Mapping**: Use this feature for full control over the integration. Select **+ Add Type Mapping** to define how your types map between systems. This could include:
* Asana *Tasks* → Azure DevOps *User Stories*.
* Asana *Sub-Tasks* → Azure DevOps *Tasks*.
#### 8. Item Routing
If you selected multiple projects on either or both sides, you must define Item Routing. 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).
#### 9. Field Mapping
* Review or manually map fields within mapped types, including **title**, **description**, and **assignees**.
* Define the synchronization flow for each field, using the arrows in the middle and selecting **Apply**.
{% hint style="warning" %}
**Inline images** aren't supported for the **Description** field.
{% endhint %}
#### 10. Assignee Mapping
* Use the assignee mapping option to match Asana assignees to Azure DevOps assignees. For more details, visit our doc: [Assignees (users) mapping](https://docs.getint.io/getintio-platform/workflows/assignees-users-mapping).
#### 11. Status Mapping
* Map status fields to align between Asana and Azure DevOps. For example, Asana *Done* could be mapped to Azure DevOps *Closed/Resolved*, and Asana *In Progress* to Azure DevOps *Active*.
* You can also configure the status direction to support unidirectional transitions instead of bidirectional updates.
#### 12. How to Manage Comments & Attachments:
* Comments are enabled by default. You can configure these settings to match your organization's needs, such as selecting unidirectional or bidirectional sync and filtering by criteria like creation date, author, or visibility (public/private).
* To synchronize attachments, toggle on the **Synchronize attachments** setting and choose the sync direction.
#### 13. Advanced Tab
* 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 bidirectional updates.
#### 14. Filtering:
It is possible to filter the synchronization to have it customized 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 on the filtering icon near the app icon in your integration. This will apply to that side of the integration.
* Select if the filtering applies to *All*, *New*, and *Synced* items.
* Note that if the option **New items** is selected, the filtering will apply only to the new items, and the already synced items will continue to sync and update. If the option **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. It is possible to filter more than one option for each field.
* Select **Apply** after creating the filters and **Save** the integration.
#### 15. Test the Integration
* Create test issues or tasks in Asana or Azure DevOps 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
Following this guide lets you set up the Asana-Azure DevOps integration with Getint. This configuration supports data synchronization of issues, tasks, and workflows across development and project management tools, allowing teams to collaborate while connecting developers and project managers.
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).
# Asana Freshservice integration
Connect Asana and Freshservice so that project management and IT service teams share a single source of truth. Changes in one platform automatically reflect in the other, eliminating manual handoffs and duplicate work.
This guide walks you through licensing, prerequisites, and a step-by-step setup using Getint.
### Requirements to Build Your Integration
Make sure you have the following ready. Gathering these first will make the setup steps below go smoothly.
| Requirement | Details |
| ----------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Getint Account** | Sign up at [app.live.getint.io](https://app.live.getint.io/) (SaaS) or deploy the [On-premise version](https://docs.getint.io/getting-started-with-the-platform/deployment-options/on-premise-deployment) (provided by our Support Team). |
| **Asana Access** | A Personal Access Token (see Step 3) and admin rights to the project you want to sync. |
| **Freshservice Access** | Your instance URL (e.g., `https://yourcompany.freshservice.com`) and an API key (see Step 4). |
| **Service Accounts** | Dedicated accounts in both tools are recommended so that synced comments are attributed consistently. |
{% hint style="info" %}
**Why service accounts?** Comments and changes are attributed to the user who created the connection. Using a dedicated service account in each tool keeps attribution clean and avoids tying the integration to a personal login.
{% endhint %}
### Licensing Model
Getint offers two licensing options for the Asana-Freshservice connector.
| | Standard License | Network License |
| ---------------- | ---------------------------------------------- | ------------------------------------------------------------------------------ |
| **Best for** | A single team connecting two tools | Managed service providers or orgs integrating three or more instances |
| **Coverage** | One Asana instance ↔ one Freshservice instance | Up to a defined number of connections (e.g., up to 10 instances) |
| **Tools** | Fixed pair, priced by the apps you sync | Any mix of tools; you can swap integrated tools while the license stays active |
| **Sync limits** | Unlimited projects and work items | Unlimited work items across covered connections |
| **Hidden costs** | None | None |
For full pricing and terms, see the [Licensing Page](https://docs.getint.io/billing-and-services/licensing).
{% hint style="info" %}
**Note**: This connector is a non-Jira connector, so it uses the simple fixed-fee Standard License rather than Jira-specific pricing.
{% endhint %}
### Setting Up Your Asana-Freshservice Integration
#### 1. Access the Getint App
* Log in at [app.live.getint.io](https://app.live.getint.io/). No account yet? Click **Sign up**.
* Enter your details, select the apps you want to connect, and click **Create new workspace**.
* Open the new workspace to launch Getint.
#### 2. Create an Integration
* Go to **Workflows** (the lightning bolt icon). Click **Create Integration**.
* Choose your integration type:
* **Continuous Sync** keeps both tools updated on an ongoing basis.
* **Data Migration** moves data one time from one tool to another.
#### 3. Generate an Asana Personal Access Token
* Log in to Asana, click your profile picture, and go to **Settings**.
* Open the **Apps** tab, scroll to **Build new apps**, and click **View developer console**.
* Click **Create new token**, add a description, and create it.
* Copy the token and store it somewhere secure, since you won't be able to view it again.
{% embed url="" %}
#### 4. Generate a Freshservice API Key
* Log in to Freshservice and click your **profile icon** (upper-right).
* Go to **Profile Settings**.
* Select **Show API Key** and complete the security captcha if prompted.
* Copy the key and store it securely.
{% embed url="" %}
#### 5. Connect to Asana
* In Getint, click **Connect App** and choose **Asana**. Enter your Asana Personal Access Token.
* Select the project you want to integrate.
* Click **Connect**.
{% hint style="warning" %}
This integration syncs **one project** at a time. Selecting multiple projects will cause Freshservice to disappear from your available options. To sync more projects, create separate integrations.
{% endhint %}
#### 6. Connect to Freshservice
* Click **Connect App** and choose **Freshservice**.
* Enter your instance URL (e.g., `https://yourcompany.freshservice.com`) and click **Next**.
* Name the connection and paste your **API key** into the password field.
* Click **Add**, then select the connection to continue.
{% hint style="info" %}
For detailed steps on how to configure your **Freshservice API token**, please refer to our guide [Connection](https://docs.getint.io/guides/quickstart/connection#freshservice).
{% endhint %}
#### 7. Configure Type Mapping
Decide which item types correspond across the two tools.
* **Quick Build** automatically maps fields and types between Asana and Freshservice.
* **Manual Mapping**: click **+ Add Type Mapping** to define mappings yourself, such as Asana **Tasks** to Freshservice **Service Requests** or **Incidents**.
**Example:** Task ↔ Service Request.
#### 8. Field Mapping
* Select the fields to synchronize, such as **Title**, **Description**, **Assignees**, and **Custom** fields. In addition to this, for the Freshservice connection to work, it is necessary to map some key fields:
1. **Reporter/Requester Mapping**:
* Link the **Reporter** field in Asana to the **Requester** field in Freshservice.
* Ensure that requesters on both platforms are mapped to allow Getint to match them appropriately.
* In case a fixed value, like an email, is supposed to be defined for this field, the configuration can be done like the picture below (also mapped automatically by default).
2. **Status Field**:
* Freshservice mandates status mapping for the integration to function. A default value needs to be set for the ticket creation only, pointing towards the Freshservice side, avoiding this option being picked up again when the issues are updated:
3. **Priority Field**:
* Mapping the priority field is necessary for the integration to operate within Freshservice.
{% hint style="warning" %}
**Inline images** in the **Description** field are not supported.
{% endhint %}
#### 9. Assignee Mapping
Match Freshservice agents to Asana members so work stays assigned to the right people. See [Assignees (users) mapping](https://docs.getint.io/getintio-platform/workflows/assignees-users-mapping) for details.
#### 10. Status Mapping
* Map status values so they stay aligned. For example, Asana **In Progress** → Freshservice **Pending**.
* Optionally set the status direction to **unidirectional** if you only want transitions to flow one way rather than both.
#### 11. Comments & Attachments
The **Comments & Attachments** tab is enabled by default.
* Choose **unidirectional** or **bidirectional** sync, and filter by criteria such as creation date or author.
* Use **Customize comments creation** to set comments as public or private, or to skip them entirely.
* Enable attachments, and set the attachment sync direction to **bidirectional**, **App A (left)**, or **App B (right)**.
#### 12. Advanced Tab
Enable **Customize create/update actions** for fine-grained control over how items sync, for example, one-way creation from the left app combined with bidirectional updates.
#### 13. Filtering
Filtering lets you sync only the items you care about. See [Items Filtering](https://docs.getint.io/getintio-platform/workflows/items-filtering) for the full reference.
To add a filter in the UI:
1. Click the filtering icon next to an app icon. The filter applies to that side of the integration.
2. Choose the scope:
* **All** applies to every item.
* **New** applies only to new items; already-synced items keep syncing and updating.
* **Synced** updates only items that are already synced, based on the filter.
3. Pick the field and value to filter on. You can add multiple conditions per field.
4. Click **Apply**, then **Save** the integration.
#### 14. Test the Integration
* Create a test task in Asana and a test ticket in Freshservice.
* Confirm each one appears and updates correctly in the other tool.
* Check the integration status and logs in Getint to verify everything runs as expected.
***
### Troubleshooting & FAQ
**The second app disappeared after I selected my project**: You likely selected more than one project in Step 5. Each integration supports a single project, so remove the extra selection or create a separate integration for each additional project.
**My comments are attributed to the wrong user**: Comments are attributed to the account that created the connection (generated the API token). Re-create the connection using a dedicated service account in each tool so attribution stays consistent.
**Images in my task descriptions aren't coming through**: Inline images in the **Description** field aren't supported. Attach images as file attachments instead, and confirm attachment sync is enabled in Step 11.
**Statuses aren't updating the way I expect**: Check your status mapping (Step 10). If a status only changes in one tool, confirm whether you set the direction to unidirectional, since bidirectional is required for changes to flow both ways.
**I can't find my Freshservice API key**: It's under **Profile Settings → Show API Key**. You may need to complete a CAPTCHA. If the option isn't visible, confirm your account has the necessary permissions.
**Can I sync more than two instances?** Yes. The **Network License** supports three or more instances and lets you swap tools while the license stays active. See the [Licensing Page](https://docs.getint.io/billing-and-services/licensing).
**Should I use Continuous Sync or Data Migration?** Use **Continuous Sync** for an ongoing two-way connection. Use **Data Migration** for a one-time transfer of existing data.
***
### Conclusion
You've now set up the Asana-Freshservice integration with Getint, keeping tasks, tickets, and workflows in sync across project management and IT service management so teams collaborate without switching tools.
Need a hand? Reach out through the [Support Center](https://getint.io/help-center) or [schedule a demo](https://calendly.com/d/cpws-jb2-8xx/demo-call-all-team).
# Asana GitLab integration
## Integrating Asana and GitLab
Connecting Asana with GitLab synchronizes project management data with development records, ensuring technical and sales teams remain aligned. This integration automates updates between platforms, eliminating manual data entry and reducing the risk of cross-departmental discrepancies.
### Asana GitLab Licensing Model
The Getint licensing model for Asana and GitLab focuses on predictable costs and scalability:
#### Standard Licensing
* This tier covers a direct integration between one Asana instance and one GitLab instance for a fixed fee. It includes unlimited project and work item synchronization without hidden charges.
#### Network License
* Designed for managed service providers or large organizations, this option supports three or more instances. It allows for a specific number of connections (e.g., up to 10 instances) 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:
* **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**: Both Asana and GitLab require Personal Access Tokens to establish a secure connection. You can find the steps to generate the access token for your connectors here: [Connection Guide](https://docs.getint.io/guides/quickstart/connection#asana).
* **Service Accounts**: Because the integration attributes comments to the user who created the connection, we recommend using dedicated Service Accounts for both instances to maintain a clear distinction between automated updates and individual user activity.
### Setting Up Your Asana GitLab Integration
#### 1. Access the Getint App
* 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
* Go to **Workflows** (lightning bolt icon), and click **Create Integration**. From this menu, select **Continuous Sync** or **Data Migration**.
#### 3. Generate an Asana Personal Access Token
* Log in to Asana and follow the video below to generate your Access Token.
{% embed url="" %}
#### 4. Generate a GitLab Token
* Log in to your GitLab account. In the top-left or top-right corner (depending on your version), click on your **Avatar/Profile Picture** and select **Preferences**.
* In the left-hand sidebar, look for the **Access** section (usually near the top) and select **Personal access tokens**.
* Click **Generate token** to open the form, and ensure you select **Legacy Token** or **Fine-grained Token**.
For specific permissions, please follow the video tutorials below:
**GitLab Legacy Token Tutorial**
{% embed url="" %}
**GitLab Fine-grained Token Tutorial**
{% embed url="" %}
#### 5. Connect to Asana
* In Getint, click on **Connect App** and choose Asana.
* Enter your Access Token for Asana.
* Select the project you wish to integrate with Asana.
{% hint style="warning" %}
You can only select one project when syncing with GitLab. Selecting multiple projects will cause GitLab to disappear from your available integration options.
{% endhint %}
* Click **Connect** to establish the connection.
#### 6. Connect to GitLab
* Click on **Connect App** and choose GitLab. Enter your GitLab instance URL (if using GitLab On-premise), then enter the generated Access token and click **Next**.
* **Add** the connection and select it.
#### 7. Select GitLab Project
* Select the established GitLab connection and choose the project you want to integrate with.
#### 8. Configure Type Mapping
* **Quick Build**: Automatically map fields and types between applications with this feature.
* **Manual Mapping**: Use this feature for full control over the integration. Select **+Add Type Mapping** to define your types, such as Incident, Task, or Issue.
* **Example:** Task ↔ Issue.
#### 9. Field Mapping
* Review or manually map fields within mapped types, including **title**, **description**, and **assignees**.
* Ensure synchronization flow is defined for each field, using the arrows and selecting **Apply**.
{% hint style="warning" %}
Unlike Assignees, Reporters are not supported in this integration because they are read-only on both platforms, and read-only fields cannot be modified.
{% endhint %}
#### 10. Assignee Mapping
* Use the assignee mapping option to match GitLab assignees to Asana assignees. For more details, visit our doc: [Assignees (users) mapping](https://docs.getint.io/getintio-platform/workflows/assignees-users-mapping).
#### 11. Status Mapping
* Map status fields to align between GitLab and Asana. For example, **To do** in Asana could be mapped to **Opened** in GitLab.
* You can also configure the status direction to support unidirectional transitions instead of bidirectional updates.
#### 12. How to Manage Comments & Attachments:
* The **Comments** are enabled by default. You can configure these settings to match your organization’s needs, such as selecting unidirectional or bidirectional sync and filtering by criteria like creation date, author, or visibility (public/private).
* For attachments, toggle on the **Synchronize attachments** setting. You will notice that you need to enter a cookie header.
{% hint style="warning" %}
**Inline images** aren’t supported for the **Description** field.
{% endhint %}
* To locate your GitLab Cookie, open your GitLab Groups page, right-click, and select Inspect. Navigate to the Network tab and refresh the page to capture the network activity. Next, select the entry named **groups** from the list of requests. You can then retrieve the required value by viewing the Cookie field under the Request Headers section of the Headers tab.
{% hint style="warning" %}
Sometimes the developer tools won't display any data for the cookie header. To fix this, click on your Group or Project, and this should make the options visible.
{% endhint %}
* Copy the information and paste it into the **GitLab Cookie Header** field in Getint. Click **Apply** to submit the changes and save your integration.
* Ensure to test the attachments after enabling them.
{% hint style="warning" %}
Currently, attachments are only supported one way from GitLab to the other app in the integration. Also, there is no API available to download and upload attachments via a GitLab integration. As a result, this alternative remains the only option for downloading attachments from synced comments, provided they come from GitLab.
{% endhint %}
#### 13. Advanced Tab
* 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 bidirectional updates.
#### 14. Filtering:
It is possible to filter the synchronization to have it customized 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 on the filtering icon near the app icon in your integration. This will apply to that side of the integration.
* Select if the filtering applies to *All*, *New*, and *Synced* items.
* Note that if the option **New items** is selected, the filtering will apply only to the new items, and the already synced items will continue to sync and update. If the option **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. It is possible to filter more than one option for each field.
* Select **Apply** after creating the filters and **Save** the integration.
#### 15. Test the Integration
* Create test issues or tasks in Jira or Asana and observe how they synchronize.
* Ensure 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
Following this guide lets you set up the Jira-Asana integration with Getint. This configuration supports data synchronization of issues, tasks, and workflows across development and project management tools, allowing teams to collaborate while connecting developers and project managers.
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).
# Asana Salesforce integration
## Integrating Asana and Salesforce
Connecting Asana with Salesforce allows technical and sales teams to synchronize project management data with customer relationship management records. This integration ensures that updates on one platform are reflected on the other, reducing manual data entry and preventing discrepancies between your departments.
### Asana Salesforce Licensing Model
The Asana-Salesforce licensing model with Getint is designed to accommodate different integration needs. Here’s an overview:
#### Standard Licensing
* For non-Jira connectors, we offer a simple license tied to a fixed fee depending on the apps you’re syncing.
* This license covers the integration between 1 instance A (Asana) and 1 instance B (Salesforce).
* No hidden costs. You can sync an unlimited number of projects and work items between these instances.
#### Network License
* For managed services companies or organizations looking to integrate three or more instances (whether the tools are the same or different), Getint offers a **Network License.** This custom license covers a specific number of connections (i.e., up to 10 instances) and imposes no restrictions on the tools involved. You can also swap the integrated tools while the license remains active, offering unparalleled flexibility.
For more details on licensing, visit our [**Licensing Page**](https://docs.getint.io/billing-and-services/licensing).
#### Salesforce API Requirements
Salesforce requires API access for integration. API access is enabled by default in the following editions:
* Enterprise Edition
* Unlimited Edition
* Performance Edition
* Developer Edition
API access is **NOT enabled** by default in:
* Group Edition
* Essentials Edition
* Professional Edition
{% hint style="info" %}
If using a Salesforce edition without API access enabled, please contact Salesforce support or refer to the Salesforce Help & Training Community.
{% endhint %}
#### Requirements to Build Your Integration:
* For non-Jira connectors, we offer 2 options: [**Getint Saas**](https://app.live.getint.io/) and the **On-premise version** (self-hosted environment). More information about Getint On-premise [here](https://docs.getint.io/getting-started-with-the-platform/deployment-options/on-premise-deployment).
* Comments are attributed to the user who created the connection. Therefore, we recommend using dedicated Service Accounts for both instances.
* **Personal Access Tokens** are required for Asana and Salesforce authentication. You can find the steps to generate the access token for your connectors here: [Connection Guide](https://docs.getint.io/guides/quickstart/connection#asana).
### Setting Up Your Asana Salesforce Integration
#### 1. Access the Getint App
* 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
* Go to **Workflows** (lightning bolt icon), and click **Create Integration**. From this menu, select **Continuous Sync** or **Data Migration**.
#### 3. Generate an Asana Personal Access Token
* Log in to Asana and follow the video below to generate your Access Token.
{% embed url="" %}
#### 4. Generate Salesforce Credentials
* Generate OAuth credentials to connect with Salesforce. These allow Getint to access your instance.
{% embed url="" %}
{% hint style="info" %}
For detailed instructions on setting up your account credentials, please refer to our [Salesforce Tokens & Requirements](https://docs.getint.io/guides/quickstart/connection#salesforce) guide.
{% endhint %}
#### 5. Connect to Asana
* In Getint, click on **Connect App** and choose Asana.
* Enter your Access Token for Asana.
* Select the project you wish to integrate with Asana.
{% hint style="warning" %}
You can only select one project when syncing with Salesforce. Selecting multiple projects will cause Salesforce to disappear from your available integration options.
{% endhint %}
* Click **Connect** to establish the connection.
#### 6. Connect to Salesforce
* Now, click on **Connect App** and choose Salesforce. Enter your Salesforce instance URL in the **URL** field and click **Next**.
* Assign a name to the connection and enter the **client\_id** and **client\_secret** credentials.
* **Add** the connection and select it.
#### 7. Configure Type Mapping
* **Quick Build**: Automatically map fields and types between applications with this feature.
* **Manual Mapping**: Use this feature for full control over your integration. Click **+Add Type Mapping** to manually define your types, such as Case, Task, Account, and Contact.
* **Example mapping**: Task ↔ Case.
#### 8. Field Mapping
* Review or manually map fields within mapped types, including **title**, **description**, and **assignees**.
* Ensure synchronization flow is defined for each field, using the arrows and selecting **Apply**.
#### 9. Assignee Mapping
* Use the assignee mapping option to match Salesforce assignees to Asana assignees. For more details, visit our doc: [Assignees (users) mapping](https://docs.getint.io/getintio-platform/workflows/assignees-users-mapping).
#### 10. Status Mapping
* Map status fields to align between Salesforce and Asana. For example, **To do** in Asana could be mapped to **New** in Salesforce.
* You can also configure the status direction to support unidirectional transitions instead of bidirectional updates.
#### 11. How to Manage Comments & Attachments:
* The **Comments & Attachments** tab is enabled by default. You can configure these settings to match your organization’s needs, such as selecting unidirectional or bidirectional sync and filtering by criteria like creation date, author, or visibility (public/private).
* Use the **Customize comments creation** setting to manage how comments are processed. You can set comments to Public or Private, or choose to skip them entirely.
* You can configure the attachment sync direction by choosing between bidirectional, App A (left), or App B (right).
{% hint style="warning" %}
**Inline images** aren’t supported for the **Description** field.
{% endhint %}
#### 12. Advanced Tab
* 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 bidirectional updates.
#### 13. Filtering:
It is possible to filter the synchronization to have it customized 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 on the filtering icon near the app icon in your integration. This will apply to that side of the integration.
* Select if the filtering applies to *All*, *New*, and *Synced* items.
* Note that if the option **New items** is selected, the filtering will apply only to the new items, and the already synced items will continue to sync and update. If the option **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. It is possible to filter more than one option for each field.
* Select **Apply** after creating the filters and **Save** the integration.
#### 14. Test the Integration
* Create test issues or tasks in Jira or Asana and observe how they synchronize.
* Ensure 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
Following this guide lets you set up the Jira-Asana integration with Getint. This configuration supports data synchronization of issues, tasks, and workflows across development and project management tools, allowing teams to collaborate while connecting developers and project managers.
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).
# Asana ServiceNow integration
## Integrating Asana and ServiceNow
Integrating Asana with ServiceNow keeps project management data and development records synchronized, helping technical and sales teams stay aligned. This integration automatically updates information across both platforms, reducing manual data entry and lowering the risk of inconsistencies between departments.
### Asana ServiceNow Licensing Model
The Getint licensing model for Asana and ServiceNow focuses on predictable costs and scalability:
#### Standard Licensing
* This tier covers a direct integration between one Asana instance and one ServiceNow 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
* Designed for managed service providers or large organizations, this option supports three or more instances. It allows for a specific number of connections (e.g., up to 10 instances) 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:
* **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**: Both Asana and ServiceNow require Personal Access Tokens to establish a secure connection. You can find the steps to generate the access token for your connectors here: [Connection Guide](https://docs.getint.io/guides/quickstart/connection#asana).
* **Service Accounts**: Because the integration attributes comments to the user who created the connection, we recommend using dedicated Service Accounts for both instances to maintain a clear distinction between automated updates and individual user activity.
### Setting Up Your Asana ServiceNow Integration
#### 1. Access the Getint App
* 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
* Go to **Workflows** (lightning bolt icon), and click **Create Integration**. From this menu, select **Continuous Sync** or **Data Migration**.
#### 3. Generate an Asana Personal Access Token
* Log in to Asana and follow the video below to generate your Access Token.
{% embed url="" %}
#### 4. Creating a ServiceNow User for Getint
Rather than using Admin credentials, the recommended approach is to create a dedicated ServiceNow user with specific, scoped permissions. Follow these steps:
* **Create the user**: In ServiceNow, go to **All** → **User Administration** → **Users**, click **New**, fill in the user details, and click **Submit**. ⚠️*Make sure to uncheck **Password needs reset**, or Getint will block the connection with a misleading permissions error. Then click **Set Password** to generate credentials.*
* **Create a custom role**: Go to **System Security** → **Users and Groups** → **Roles**, click **New**, name your role (e.g., `getint`), and click **Submit**.
* **Elevate to Security Admin**: Click your profile image, select **Elevate Role**, choose **security\_admin**, and click update. This is required to modify ACL settings.
* **Create 6 ACL records**: Go to **System Security → Access Control (ACL)** and create the following permission records, adding your custom role to the **Requires Role** section of each:
| Record | Table | Field | Operation |
| ------ | ----------------------------------- | ------------- | --------- |
| 1 | `Dictionary Entry (sys_dictionary)` | \* (Asterisk) | Read |
| 2 | `Dictionary Entry (sys_dictionary)` | None | Read |
| 3 | `Field Class (sys_glide_object)` | \*(Asterisk) | Read |
| 4 | `Choice (sys_choice)` | \*(Asterisk) | Read |
| 5 | `Field Class (sys_glide_object)` | None | Read |
| 6 | `Journal Entry (sys_journal_field)` | None | Read |
* **Assign roles to the user**: Go back to **User Administration → Users**, find your user, open the **Roles** tab, click **Edit**, and add both itil permission and your custom role. Click **Save → Update**.
The user is now ready to establish the ServiceNow connection.
{% hint style="info" %}
For full details and screenshots, see the complete guide: [Creating a ServiceNow User for Getint Integration](https://docs.getint.io/guides/integration-synchronization/jira-servicenow-integration/creating-a-servicenow-user-for-getint-integration).
{% endhint %}
#### 5. Connect to Asana
* In Getint, click on **Connect App** and choose Asana.
* Enter your Access Token for Asana.
* Select the project(s) you wish to integrate with Asana.
* Click **Connect** to establish the connection.
#### 6. Connect to ServiceNow
* Click on **Connect App** and choose ServiceNow. Enter your ServiceNow instance URL, then enter your username and password. At last, click **Add** to create the connection.
* **Add** the connection, and now it will be available for selection.
#### 7. Configure Type Mapping
* **Quick Build**: Automatically align fields and data types between applications using this feature.
* **Manual Mapping**: If you want full control over the integration, select **+ Add Type Mapping** to define how your types map between systems, such as Incident, Task, or Change Request.
* **Example**: Task ↔ Change Request.
#### 8. Item Routing
If you selected multiple projects for the Asana connection, you must define Item Routing. 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).
#### 9. Field Mapping
* Review or manually map fields within mapped types, including **title**, **description**, and **assignees**.
* Ensure synchronization flow is defined for each field, using the arrows and selecting **Apply**.
#### 10. Assignee Mapping
Use the **Assignee mapping** option to match ServiceNow assignees (assigned to) with their corresponding Asana assignees. This step ensures that when a task, incident, or ticket syncs between the two systems, it’s 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).
#### 11. Status Mapping
Use the **Status mapping** option to align workflow states between ServiceNow and Asana. Each platform uses its own terminology for task or ticket progress, so mapping ensures that updates stay 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 Asana → **New** in ServiceNow
* **In Progress** in Asana → **Review** in ServiceNow
* **Completed** in Asana → **Closed** in ServiceNow
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 unidirectional transitions instead of bidirectional updates.
#### 12. How to Manage Comments & Attachments:
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 distinct logic flows for these items:
* **Bidirectional**: Updates to comments or attachments in either Asana or ServiceNow will reflect in the other platform.
* **Unidirectional to Asana**: Data flows exclusively from ServiceNow to Asana. Changes made in Asana will not sync back to ServiceNow.
* **Unidirectional to ServiceNow**: Data flows exclusively from Asana to ServiceNow. Changes made in ServiceNow will not sync back to Asana.
**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 specific 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, deciding whether they should flow from ServiceNow to Asana, from Asana to ServiceNow, or both ways.
{% hint style="warning" %}
**Inline images** aren’t supported for the **Description** field.
{% endhint %}
#### 13. Advanced Tab
* 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 bidirectional updates.
#### 14. Filtering:
It is possible to filter the synchronization to have it customized 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 on the filtering icon near the app icon in your integration. This will apply to that side of the integration.
* Select if the filtering applies to *All*, *New*, and *Synced* items.
* Note that if the option **New items** is selected, the filtering will apply only to the new items, and the already synced items will continue to sync and update. If the option **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. It is possible to filter more than one option for each field.
* Select **Apply** after creating the filters and **Save** the integration.
#### 15. Filtering Items Across Multiple Asana–ServiceNow Integrations
* If you want to sync **Asana Project A** only with ServiceNow incidents assigned to **Assignment Group A**, use the filter items feature. In Getint, you configure the connection by mapping the types and fields between ServiceNow and Asana so fields like **Assignee** and **Assignment Group** stay aligned during syncs.
This filtering ensures that only incidents belonging to the correct group appear in **Asana Project A**.
* On a separate integration, you can set up (or duplicate the existing integration) to integrate **Asana Project B** with ServiceNow Incidents that belong to **Assignment Group B.** Here, different filtering will be needed. You can define filter rules in Getint to control which items are synchronized, specifying criteria such as status or priority to ensure only relevant items are synced. This helps manage data efficiently and avoids unnecessary clutter. Remember to save the integration once the filters are applied to ensure they are active.
{% hint style="info" %}
Instead of applying filters for each individual project, you can use **Item Routing for Many Projects** to manage all Asana projects within a single integration. This feature automatically routes incoming ServiceNow items to the correct Asana project based on the rules you define, reducing the need to maintain multiple separate integrations.
{% endhint %}
#### 16. Test the Integration
* Create test issues or tasks in ServiceNow or Asana and observe how they synchronize.
* Ensure 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
Following this guide lets you set up the ServiceNow-Asana integration with Getint. This configuration supports data synchronization of issues, tasks, and workflows across development and project management tools, allowing teams to collaborate while connecting developers and project managers.
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).
# Freshdesk to Freshdesk integration
## Freshdesk-Freshdesk integration
The Getint platform connects two Freshdesk instances to unify customer support across teams, regions, or business units. It supports fast ticket syncing, automated workflows, and shared visibility between help desks, helping reduce response times and keep both sides aligned. Follow this 2026 guide for a quick setup that works for businesses of all sizes. Use the Freshdesk-Freshdesk integration with Getint for better multi-instance support management.
### Freshdesk-Freshdesk Licensing Model
The **Freshdesk-Freshdesk licensing model** with Getint fits various integration needs. Here is an overview:
#### Standard Licensing
* A Getint license is required to enable data synchronization between the two Freshdesk instances.
* This keeps setup simple and quick, with no extra configurations needed beyond the connection details.
#### Flexible License
* For managed services companies or organizations integrating four or more instances (same or different tools), Getint provides a **Flexible License**. This custom option includes a set number of connections (up to 10 instances) with no tool limits. You can switch integrated tools anytime during the license term for maximum adaptability.
For licensing details, visit our [**Pricing Page**](https://docs.getint.io/licensing).
#### Requirements to Build Your Integration
* Comments are attributed to the user who created the connection. Therefore, we recommend using dedicated **Service Accounts** for both instances.
* An **API key** is required for each Freshdesk instance. Learn more here: [Access Tokens](https://docs.getint.io/guides/quickstart/connection#jira).
### Setting Up Your Freshdesk-Freshdesk Integration
#### 1. Access the Getint App
* Log in to the Getint platform to begin configuring your integration.
#### 2. Create Integration
Click **Create Integration** and select either:
* **Continuous Sync** for ongoing synchronization.
* **Migration** for a one-time data transfer.
#### 3. Generate a Freshdesk API Key (First Instance)
* Log in to your first Freshdesk account, click on your profile picture in the top right corner, and select **Profile Settings**.
* In the sidebar on the right, click on the **View API key** button to access the API key.
* Complete the CAPTCHA verification, if prompted, and copy the API Key for integration.
{% embed url="" %}
{% hint style="warning" %}
You can reset the API Key to stop an app from connecting to your helpdesk if you need to. Remember that doing so will also disconnect other apps that use the same key.
{% endhint %}
#### 4. Generate a Freshdesk API Key (Second Instance)
* Repeat the same steps in your second Freshdesk account: open **Profile Settings**, click **View API key**, complete the captcha if prompted, and copy the API Key.
#### 5. Create a Connection with Both Freshdesk Instances
**First Freshdesk Connection:**
* Select **Freshdesk** as the connection app, and click **Create New Connection**.
* Enter your first Freshdesk instance URL in the **URL** field and click **Next**.
* Assign a name to the connection and enter the API key as the password.
* **Add** the connection and select it.
**Second Freshdesk Connection:**
* Select **Freshdesk** as the connection app again, and click **Create New Connection**.
* Enter your second Freshdesk instance URL in the **URL** field and click **Next**.
* Assign a name to the connection and enter the API key as the password.
* **Add** the connection and select it.
#### 6. Configure Type Mapping
* **Quick Build**: Use the Quick Build feature to automatically map fields and types between both instances, simplifying the process.
* **Manual Mapping**: For greater control, manually map the types yourself. This approach lets you adapt the mapping to meet your specific needs. Click **+ Add type mapping** to map the Freshdesk **Incident** type on one instance to the **Incident** type on the other.
* For example, **Service Request ↔ Service Request**.
#### 7. Configure Field Mapping
Select the fields to synchronize, such as **Subject**, **Description**, **Agents**, and **Custom** fields. In addition to this, for the Freshdesk connections to work, it is necessary to map some key fields:
1. **Requester Mapping**:
* Link the **Requester** field on the first instance to the **Requester** field on the second instance.
* Ensure that requesters on both instances are mapped to allow Getint to match them appropriately.
2. **Status Field**:
* Freshdesk requires status mapping for the integration to work. You need to set a default value for ticket creation only, pointing to the receiving Freshdesk side, and then disable the status option on Update so it isn't picked up again when tickets are being updated in between syncs.
3. **Priority Field**:
* Mapping the priority field is necessary for the integration's operation within Freshdesk.
After all fields and types have been configured, give your integration a distinctive name and save the settings.
#### 8. Assignee Mapping
Use the assignee mapping option to match agents between the two Freshdesk instances, enabling precise synchronization of ticket ownership. For more details, visit our doc: [Assignees (users) mapping](https://docs.getint.io/getintio-platform/workflows/assignees-users-mapping).
#### 9. Status Mapping
Map status fields to align between the two Freshdesk instances. For example, **Open** on one instance could be mapped to **Open** on the other.
#### 10. How to Manage Comments & Attachments:
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 distinct logic flows for these items:
* **Bidirectional**: Updates to comments or attachments in either instance will reflect in the other.
* **Unidirectional to the first instance**: Data flows exclusively from the second Freshdesk to the first. Changes made in the first will not sync back.
* **Unidirectional to the second instance**: Data flows exclusively from the first Freshdesk to the second. Changes made in the second 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 specific fields while keeping other mapped fields active.
**Comment Privacy**
You can control the visibility of comments synced between the two instances. The integration supports toggling between public and private comments freely, so you can configure public comments on one side to appear as private on the other, and vice versa. This gives your teams full control over what is visible to end users versus internal staff across both instances.
{% hint style="info" %}
For a full overview of filtering logic, AND/OR conditions, and date-based filtering, refer to the [Comments Filtering documentation](https://docs.getint.io/getintio-platform/workflows/filtering-items-for-integration-in-getint/how-to-filter-comments).
{% endhint %}
#### 11. Filtering Options
Customize synchronization by applying filters:
* After completing your integration, add filters to each app by clicking the filter icon next to its app icon. This will affect the corresponding side of the integration.
* Choose the filter scope:
* **ALL items filter**: Rules will be verified for every item before synchronization.
* **NEW items filter**: Rules will be verified only for newly created items that have not yet been synced.
* **SYNCED items filter**: Rules will be verified for items that were already synced in the past.
Add values for the filters and click **Apply**. For more details on how to use the filter, refer to our [Filtering Guide](https://docs.getint.io/getintio-platform/workflows/items-filtering).
#### 12. Test the Integration
Before deploying the integration to your production environment, perform a verification cycle to ensure data flows correctly between both **Freshdesk** instances.
**Verification Steps**
1. **Initial Creation:**
* Create a test ticket in the first **Freshdesk** instance.
* Create a test ticket in the second **Freshdesk** instance.
* Confirm that the tickets appear in the respective instances according to your mapping rules.
2. **Field & Feature Validation:**
* **Updates**: Modify a mapped field and confirm the change is reflected in the linked instance.
* **Comments & Attachments**: Add a comment or upload a file to verify the sync direction and visibility.
* **Status Transitions**: Change the status (e.g., move a ticket to "Pending") and verify the linked **Freshdesk** ticket updates accordingly.
3. **Audit Logs:**
* Access the **Logs** tab within the platform.
* Review the entries to confirm successful executions and identify any potential mapping errors or permission conflicts.
***
#### Conclusion
By following these steps, you have established a functional integration between two **Freshdesk** instances. This setup automates the synchronization of records, workflows, and communication, keeping support teams aligned across both help desks.
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).
# Freshservice to Freshdesk integration
The Getint platform connects Freshservice and Freshdesk to unify IT service management (ITSM) and customer support. It supports fast ticket syncing, automated workflows, and shared visibility across teams, helping reduce response times and keep both sides aligned. Follow this guide for a quick setup that works for businesses of all sizes. Use the Freshservice-Freshdesk integration with Getint for better service and support management.
### Freshservice-Freshdesk Licensing Model
The **Freshservice-Freshdesk licensing model** with Getint fits various integration needs. Here is an overview:
#### Standard Licensing
* A single Getint license enables data synchronization between Freshservice and Freshdesk.
* This keeps setup simple and quick, with no extra configurations needed on either side.
#### Flexible License
* For managed services companies or organizations integrating four or more instances (same or different tools), Getint provides a **Flexible License**. This custom option covers a set number of connections (up to 10 instances) without tool limits. You can switch integrated tools anytime during the license term for maximum adaptability.
For licensing details, visit our [**Pricing Page**](https://docs.getint.io/licensing).
#### Requirements to Build Your Integration
* Access to the **Getint platform** is required.
* Comments are attributed to the user who created the connection. Therefore, we recommend using dedicated **Service Accounts** for both instances.
* An **API key** is required for Freshservice authentication, and an **API key** is required for Freshdesk. Learn more here: [Access Tokens](https://docs.getint.io/guides/quickstart/connection).
### Setting Up Your Freshservice-Freshdesk Integration
#### 1. Access the Getint Platform:
* 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 Integration
Go to **Workflows** (lightning bolt icon), click **Create Integration**, and select either:
* **Continuous Sync** for ongoing synchronization.
* **Migration** for a one-time data transfer.
#### 3. Generate a Freshservice API Key
* Log in to your Freshservice account, click on your profile picture in the top right corner, and select **Profile Settings**.
* On the new page, click on **Show API Key** to access the API key.
* Complete the CAPTCHA verification, if prompted, and copy the API Key for integration.
{% embed url="" %}
{% hint style="info" %}
You can reset the API Key to stop an app from connecting to your service desk if you need to. Remember that doing so will also disconnect other apps that use the same key.
{% endhint %}
#### 4. Generate a Freshdesk API Key
* Log in to your Freshdesk account, click on your profile picture in the top right corner, and select **Profile Settings**.
* In the sidebar on the right, click on the **View API key** button to access the API key.
* Complete the CAPTCHA verification, if prompted, and copy the API Key for integration.
{% embed url="" %}
{% hint style="info" %}
You can reset the API Key to stop an app from connecting to your helpdesk if you need to. Remember that doing so will also disconnect other apps that use the same key.
{% endhint %}
#### 5. Create a Connection with Freshservice and Freshdesk
**Freshservice Connection:**
* Select **Freshservice** as the connection app, and click **Create New Connection**.
* Enter your Freshservice instance URL in the **URL** field and click **Next**.
* Assign a name to the connection and enter the API key.
* **Add** the connection and select it.
**Freshdesk Connection:**
* Select **Freshdesk** as the connection app, and click **Create New Connection**.
* Enter your Freshdesk instance URL in the **URL** field and click **Next**.
* Assign a name to the connection and enter the API key as the password.
* **Add** the connection and select it.
#### 6. Configure Type Mapping
* **Quick Build**: Use the Quick Build feature to automatically map fields and types between applications, simplifying the process.
* **Manual Mapping**: For greater control, manually map the types yourself. This approach lets you adjust the mapping to meet your specific needs. Click **+ Add type mapping** to add Freshservice types (Incident, Service Request) and map them to the Freshdesk **Service Request** type.
* For example, **Incident ↔ Service Request**.
#### 7. Configure Field Mapping
Select the fields to synchronize, such as **Title**, **Description**, **Assignees**, and **Custom** fields. In addition to this, for the connection to work, it is necessary to map some key fields:
1. **Requester Mapping**:
* Link the **Requester** field in Freshservice to the **Requester** field in Freshdesk.
* Ensure that requesters on both platforms are mapped to allow Getint to match them appropriately.
* In case a fixed value, like an email, is supposed to be defined for this field, the configuration can be done accordingly.
2. **Status Field**:
* Both Freshservice and Freshdesk mandate status mapping for the integration to function. A default value needs to be set for the ticket creation only, avoiding this option being picked up again when the tickets are updated.
3. **Priority Field**:
* Mapping the priority field is necessary for the integration's operation within both Freshservice and Freshdesk.
After all fields and types have been configured, give your integration a distinctive name and save the settings.
#### 8. Assignee Mapping
Use the assignee mapping option to match Freshdesk agents to Freshservice assigned to fields.
For more details, visit our doc: [Assignees (users) mapping](https://docs.getint.io/getintio-platform/workflows/assignees-users-mapping).
#### 9. Status Mapping
Map status fields to align between Freshservice and Freshdesk. For example, **Open** in Freshservice could be mapped to **Open** in Freshdesk or to a different status if your organization has renamed them.
#### 10. How to Manage Comments & Attachments:
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 distinct logic flows for these items:
* **Bidirectional**: Updates to comments or attachments in either Freshservice or Freshdesk will reflect in the other platform.
* **Unidirectional to Freshservice**: Data flows exclusively from Freshdesk to Freshservice. Changes made in Freshservice will not sync back to Freshdesk.
* **Unidirectional to Freshdesk**: Data flows exclusively from Freshservice to Freshdesk. Changes made in Freshdesk will not sync back to Freshservice.
**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 specific fields while keeping other mapped fields active.
{% hint style="info" %}
For a full overview of filtering logic, AND/OR conditions, and date-based filtering, refer to the [Comments Filtering documentation](https://docs.getint.io/getintio-platform/workflows/filtering-items-for-integration-in-getint/how-to-filter-comments).
{% endhint %}
#### 11. Filtering Options
Customize synchronization by applying filters:
* After completing your integration, add filters to each app by clicking the filter icon next to its app icon. This will affect the corresponding side of the integration.
* Choose the filter scope:
* **ALL items filter**: Rules will be verified for every item before synchronization.
* **NEW items filter**: Rules will be verified only for newly created items that have not yet been synced.
* **SYNCED items filter**: Rules will be verified for items that were already synced in the past.
* Add values for the filters and click **Apply**.
For more details on how to use the filter, refer to our [Filtering Guide](https://docs.getint.io/getintio-platform/workflows/items-filtering).
#### 12. Test the Integration
Before deploying the integration to your production environment, perform a verification cycle to ensure data flows correctly between **Freshservice** and **Freshdesk**.
**Verification Steps**
1. **Initial Creation:**
* Create a test ticket in **Freshservice**.
* Create a test ticket in **Freshdesk**.
* Confirm that the items appear in the respective platforms according to your mapping rules.
2. **Field & Feature Validation:**
* **Updates**: Modify a mapped field and confirm the change is reflected on the linked platform.
* **Comments & Attachments**: Add a comment or upload a file to verify the sync direction and visibility.
* **Status Transitions**: Change the status (e.g., move a Freshservice ticket to "Pending") and verify the **Freshdesk** ticket updates accordingly.
3. **Audit Logs:**
* Access the **Logs** tab within the platform.
* Review the entries to confirm successful executions and identify any potential mapping errors or permission conflicts.
***
### Conclusion
By following these steps, you have established a functional integration between **Freshservice** and **Freshdesk**. This setup automates the synchronization of records, workflows, and communication, bridging the gap between IT service and customer support teams.
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).
# Salesforce Azure DevOps integration
### Integrating Salesforce and Azure DevOps
Connecting Salesforce with Azure DevOps links customer records with engineering work, keeping sales, support, and development teams aligned. Cases raised by customers reach the development backlog without manual re-entry, and progress made by engineers flows back to the teams that own the customer relationship. Follow this guide to set up bidirectional synchronization between your Salesforce org and your Azure DevOps organization.
### Salesforce Azure DevOps Licensing Model
The Getint licensing model for Salesforce and Azure DevOps covers different integration needs. Here is an overview:
#### Standard Licensing
* For non-Jira connectors, we offer a simple license tied to a fixed fee depending on the apps you are syncing.
* This license covers the integration between 1 instance A (Salesforce) and 1 instance B (Azure DevOps).
* No hidden costs. You can sync an unlimited number of work items between these instances.
You can find more information about our pricing structure here: [Getint Pricing](https://www.getint.io/pricing).
#### Network License
* For managed services companies or organizations integrating three or more instances (whether the tools are the same or different), Getint offers a **Network License**. This custom license covers a specific number of connections (for example, up to 10 instances) and imposes no restrictions on the tools involved. You can also swap the integrated tools while the license remains active.
For more details on licensing, visit our [Licensing Page](https://docs.getint.io/licensing).
#### Salesforce API Requirements
Salesforce requires API access for integration. API access is enabled by default in the following editions:
* Enterprise Edition
* Unlimited Edition
* Performance Edition
* Developer Edition
API access is **NOT enabled** by default in:
* Group Edition
* Essentials Edition
* Professional Edition
{% hint style="info" %}
If you are using a Salesforce edition without API access enabled, contact Salesforce support or refer to the Salesforce Help & Training Community.
{% endhint %}
#### Requirements to Build Your Integration
* **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**: Azure DevOps requires a Personal Access Token, and Salesforce requires OAuth credentials (`client_id` and `client_secret`). You can find the steps to generate credentials for both connectors here: [Connection Guide](https://docs.getint.io/guides/quickstart/connection#azure-devops).
* **Service Accounts**: Comments are attributed to the user who created the connection, so we recommend using dedicated **Service Accounts** on both sides to keep automated updates distinct from individual user activity.
***
### Setting Up Your Salesforce Azure DevOps Integration
#### 1. Access the Getint App
* 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.
#### 2. Create an Integration
* Go to **Workflows** (lightning bolt icon) and click **Create Integration**. From this menu, select **Continuous Sync** or **Data Migration**.
#### 3. Generate an Azure DevOps Token
To integrate Azure DevOps (Server or Cloud), you must provide a token with the necessary permissions. Follow the steps below to generate one:
* Log in to your Azure DevOps organization.
* Open **User Settings** from the profile menu.
* Select **Personal Access Tokens** from the left sidebar.
* Click **New Token** and enter a name for the token.
* Set the expiration and select the appropriate scopes:
* **Work Items**: Read & Write
* **Project and Team**: Read & Write
* **Graph**: Read (required for accurate user data retrieval)
* **Code**: Read (if you are syncing repositories with the Git Connector)
* Click **Create**, then copy and securely store the generated token. This token authenticates and authorizes Getint to access your Azure DevOps organization.
* When configuring the Azure DevOps connection details in Getint, provide the generated token as the password.
{% embed url="" %}
#### 4. Generate Salesforce Credentials
Salesforce uses OAuth authentication. You grant permissions to Getint through an External Client App, and the resulting credentials are stored in a dedicated Getint database for use by that user only.
* Sign in to Salesforce, click the **Cog** icon in the upper-right corner, and select **Setup**.
* Go to **Platform Tools** > **Apps** > **External Client Apps**, then open the **External Client App Manager**.
* Select **New External Client App** and enter a unique name, your email address, and the API name.
* Enable **OAuth**:
* Scroll down and turn on OAuth.
* Enter the Callback URL: `https://login.salesforce.com/services/oauth2/callback`.
* Select the OAuth scope **Manage user data via APIs (API)**.
* In the **Flow Enablement** section, activate **Client Credentials Flow**, then turn off all other options in the **Security** section.
* Click **Create** at the bottom of the page. Once the app exists, go back into its settings to continue.
* Select **Edit**, open **OAuth Policies**, enable **Client Credentials Flow**, and enter the username shown under **Personal Information** in your profile. Click **Save**.
* Open the **Settings** tab, select **Consumer Key and Secret**, complete the verification screen, and copy the **Consumer Key** (`client_id`) and **Consumer Secret** (`client_secret`).
{% hint style="info" %}
Salesforce requires HTTPS for the Callback URL.
{% endhint %}
{% embed url="" %}
#### 5. Connect to Azure DevOps
* In Getint, click **Connect App** and choose Azure DevOps, then select **Create a new connection**. Enter the URL for the connection and click **Next**.
* Provide a name for the connection, enter your email, and paste the token generated in the previous steps. Click **Add** to complete.
* Once the connection is established, select the Azure DevOps project you want to synchronize from the dropdown menu and click **Connect**.
{% hint style="warning" %}
You can only select one project when syncing with Salesforce. Selecting multiple projects will cause Salesforce to disappear from your available integration options.
{% endhint %}
#### 6. Connect to Salesforce
* Click **Connect App** and choose Salesforce. Enter your Salesforce instance URL in the **URL** field and click **Next**.
* Assign a name to the connection and enter the **client\_id** and **client\_secret** credentials.
* **Add** the connection and select it.
{% hint style="info" %}
Use the correct URL format to connect to your instance:
* `https://YOUR_INSTANCE_NAME.develop.lightning.force.com`
* `https://YOUR_INSTANCE_NAME.develop.my.salesforce.com`
{% endhint %}
#### 7. Configure Type Mapping
* **Quick Build**: Automatically map fields and types between applications with this feature.
* **Manual Mapping**: Use this option for full control over the integration. Click **+ Add Type Mapping** to define how your types map between systems. This could include:
* Salesforce *Case* to Azure DevOps *Bug*.
* Salesforce *Account* to Azure DevOps *Task*.
#### 8. Field Mapping
* Review or manually map fields within mapped types, including **subject**, **description**, **priority**, and **assignees**.
* Define the synchronization flow for each field, using the arrows in the middle and selecting **Apply**.
{% hint style="warning" %}
**Inline images** are not supported for the **Description** field.
{% endhint %}
#### 9. Assignee Mapping
* Use the assignee mapping option to match Salesforce users to Azure DevOps users, which keeps ownership of work items accurate on both sides. For more details, visit our doc: [Assignees (users) mapping](https://docs.getint.io/getintio-platform/workflows/assignees-users-mapping).
#### 10. Status Mapping
* Go to the **Status** tab and map status fields to align between Salesforce and Azure DevOps. For example, Salesforce *New* could be mapped to Azure DevOps *New*, Salesforce *Working* to Azure DevOps *Active*, and Salesforce *Closed* to Azure DevOps *Done*.
* You can also configure the status direction to support unidirectional transitions instead of bidirectional updates.
#### 11. How to Manage Comments & Attachments:
* The **Comments & Attachments** tab is enabled by default. You can configure these settings to match your organization's needs, such as selecting unidirectional or bidirectional sync and filtering by criteria like creation date, author, or visibility (public/private).
* Use the **Customize comments creation** setting to manage how comments are processed. You can set comments to Public or Private, or choose to skip them entirely.
* To synchronize attachments, toggle on the **Synchronize attachments** setting and choose the sync direction between bidirectional, App A (left), or App B (right).
{% hint style="info" %}
For a full overview of filtering logic, AND/OR conditions, and date-based filtering, refer to the [Comments Filtering documentation](https://docs.getint.io/getintio-platform/workflows/filtering-items-for-integration-in-getint/how-to-filter-comments).
{% endhint %}
#### 12. Advanced Tab
* 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 bidirectional updates.
#### 13. Filtering:
It is possible to filter the synchronization to have it customized 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 on the filtering icon near the app icon in your integration. This will apply to that side of the integration.
* Select if the filtering applies to *All*, *New*, and *Synced* items.
* Note that if the option **New items** is selected, the filtering will apply only to the new items, and the already synced items will continue to sync and update. If the option **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. It is possible to filter more than one option for each field.
* Select **Apply** after creating the filters and **Save** the integration.
#### 14. Test the Integration
Before deploying the integration to your production environment, perform a verification cycle to confirm data flows correctly between Salesforce and Azure DevOps.
**Verification Steps**
1. **Initial Creation:**
* Create a test case in Salesforce.
* Create a test work item in Azure DevOps.
* Confirm that the counterparts appear on the opposite side according to your mapping rules.
2. **Field & Feature Validation:**
* **Updates**: Modify a mapped field and confirm the change is reflected in the linked item.
* **Comments & Attachments**: Add a comment or upload a file to verify the sync direction and visibility.
* **Status Transitions**: Change the status on one side and verify the linked item updates accordingly.
3. **Audit Logs:**
* Access the **Logs** tab within the platform.
* Review the entries to confirm successful executions and identify any potential mapping errors or permission conflicts.
***
### Conclusion
Following this guide lets you set up the Salesforce-Azure DevOps integration with Getint. This configuration synchronizes cases, work items, comments, and status changes across your CRM and your development platform, so customer-facing teams and engineering teams work from the same information.
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).
# Jira Airtable integration
**Introduction**
The Jira–Airtable integration with Getint provides a practical solution for project and data management. It combines Jira’s structured task tracking with Airtable’s flexible database features, creating a single interface that supports efficiency and collaboration. This guide explains how to set up the integration step by step, helping teams improve productivity, maintain data accuracy, and achieve real‑time synchronization aligned with business needs.
### Step-by-Step Setup Guide
**1. Launch Getint within Jira**
* Navigate to "Apps" and select "Airtable integration for Jira."
**2. Create Integration**
* Click "Continuous Sync" or "Migration."
{% hint style="danger" %}
**Note:** The "Continuous Sync" functionality ensures consistent data integration, which is Getint's standard operation mode. For transferring pre-existing data, consider the "Migration" feature available as a premium option. For more details, contact our support team.
{% endhint %}
**3. Token Generation (Password for Jira Cloud)**
* For Jira Cloud, generate a Jira token. This token will act as your password:
* Go to Atlassian Account Settings.
* Navigate to Security and generate an API token, then use this token as the password for Jira integration.
**4. Choose the Apps and Establish Connections**
* Ensure you are logged in as a user with admin rights, click on "Select App" and choose Jira.
* Select "Create New" to establish a new connection with your Jira instance and add the URL of your Jira instance (omit the trailing "/ ").
* Enter the login credentials of the admin user.
**5. Select the Jira Project**
* Once the connection is established, choose the Jira project you want to connect to from the dropdown menu.
**6. Generate Airtable Token**
* Go to Airtable, ensure that you have created the "Last Modified Time" column, then create the Access Token. Follow the steps [here](https://docs.getint.io/guides/quickstart/connection#airtable) for the token with the correct scope.
**7. Connect to Airtable**
* If no connection is established yet, create a new one.
* Use the Airtable token generated as a password. Then select the space and table.
**8. Type Mapping**
* Map Jira issue types such as Task, Bug, Epic, and Story to Task in Airtable.
{% hint style="danger" %}
Please note that at the moment, we only support the "Task" issue type for this integration.
{% endhint %}
**9. Field Mapping**
* Designate specific fields for synchronization and map them accordingly.
* If you need fields that are not appearing for your integration, including labels or custom fields, contact us at . We continually improve our product based on user feedback and value your insights.
**10. Finalize Integration**
* Name your project and click "Create" to finalize the integration setup.
**11. Filtering:**
It is possible to filter the synchronization to have it customized for your needs and requirements.
**UI Filtering Option:**
* Click on the filtering icon near the app icon in your integration. This will apply to that side of the integration.
* Select if the filtering applies to All, New, and Synced items.
* Note that if the option *"New items"* is selected, the filtering will apply only to the new items, and the already synced items will continue to sync and update. If the option *"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. It is possible to filter more than one option for each field.
* Select "Apply" once you have created the filters and "Save" the integration.
**12. Test the Integration**
To ensure everything is working correctly, create tasks and go to the reporting section to verify that all syncs are functioning as expected. If you encounter any issues, please contact our support team for assistance.
Leverage the Jira-Airtable integration by Getint to optimize your project management and data processes. For further assistance or feedback, contact us at our [Help Center](https://getintio.atlassian.net/servicedesk/customer/portals).
# Jira Asana integration
Integrate Jira with Asana using Getint to enhance workflows with other teams, facilitate communication among teams, companies, and customers, or migrate to Jira while keeping your backlog.
Asana and Jira offer key project management advantages: Asana’s user-friendly interface and flexible tasks complement Jira’s robust issue-tracking and development tools. Getint’s integration synchronizes tasks and timelines in real time across Jira Cloud, Data Center, or On-Premise, streamlining communication, boosting productivity, fostering collaboration, and aligning teams.
***
### Asana-Jira Licensing Model
The Asana-Jira licensing model with Getint is designed to accommodate different integration needs. Here’s an overview:
#### Standard Licensing
* A Getint license is only required on Jira, allowing seamless data synchronization between Asana and Jira.
This makes setup simpler and faster, without the need for additional configurations in Asana.
#### Flexible License
* For managed services companies or organizations looking to integrate four or more instances (regardless of whether they are the same or different tools), Getint offers a **Flexible License.** This custom license covers a specific number of connections (i.e., up to 10 instances) without restrictions on the tools involved. You can also swap the integrated tools while the license remains active, offering unparalleled flexibility.
For more details on licensing, visit our [**Pricing Page**](https://docs.getint.io/billing-and-services/licensing).
#### Requirements to Build Your Integration:
* The **Getint app** must be installed in Jira.
* Comments are attributed to the user who created the connection. Therefore, we recommend using dedicated Service Accounts for both instances.
* Jira instances must have a dedicated user and an associated API token with permissions to read, write, view, and modify the project.
* **Personal Access Tokens** are required for Jira and Asana authentication. You can find the steps to generate the access token for your connectors here: [Connection Guide](https://docs.getint.io/guides/quickstart/connection#asana).
### Setting Up Your Asana-Jira Integration
#### 1. Access the Getint App in Jira
* Navigate to **Apps** and select **Jira - Asana Integration**.
#### 2. Create Integration
* Click **Create integration** or **Migration**.
#### 3. Token Generation (Password for Jira Cloud)
* For Jira Cloud, generate a Jira token. This token will act as your password:
* Go to **Atlassian Account Settings**.
* Navigate to **Security** and go to **Generate and manage** **API tokens**, then select an API token or an API token with scopes.
* After creation, use this token as the password for Jira integration. More information about access tokens for Jira [here](https://docs.getint.io/guides/quickstart/connection#jira).
#### 4. Generate an Asana Personal Access Token
* Log in to your Asana account and follow the steps in the video below to create the Access Token.
{% embed url="" %}
* Make sure to securely store your token, as it will only be visible once.
#### 5. Connect to Jira
* In Getint, enter your Jira instance URL, username, and the API token.
* Use the Personal Access Token for Jira Cloud.
* Select the Jira project(s) you wish to integrate with Asana.
#### 6. Enter the Asana Token in Getint
Once you have generated a Personal Access Token in your Asana instance, you will now have the option to connect the tool with Getint.
* Paste the **Asana Personal Access Token** into the API token field.
* Select the project(s) you want to sync with Asana.
* Click **Connect** to establish the connection.
#### 7. Issue Type Mapping
* Map the Jira issue types you want to sync with Asana tasks, such as mapping an Asana Task to a Jira task or a Jira bug to an Asana task.
* Consider using the **Quick Build** beta feature for automated type and field mapping, which can streamline the setup process.
#### 8. Item Routing
If you selected multiple projects on either or both sides, you must define Item Routing. 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).
#### 9. Field Mapping
Review or manually map fields within mapped types, including title, description, and assignees.
Add your desired fields, and define the sync direction (unidirectional or bi-directional) with the arrows.
#### 10. Assignee Mapping
Use the assignee mapping option to match Jira assignees to Asana assignees, enabling precise synchronization of task ownership. For more details, visit our doc: [Assignees (users) mapping](https://docs.getint.io/getintio-platform/workflows/assignees-users-mapping).
#### 11. Status Mapping
Map status fields to align between Jira and Asana. For example, **To do** in Jira could be mapped to **Opened** in Asana.
#### 12. Comments & Attachments
When enabling comment synchronization, you can filter by criteria such as created date, author, or visibility (public/private).
* To synchronize attachments, scroll down and enable the option.
{% hint style="warning" %}
**Inline images** aren't supported for the **Description** field.
{% endhint %}
#### 13. Filtering:
It is possible to filter the synchronization to have it customized 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 on the filtering icon near the app icon in your integration. This will apply to that side of the integration.
* Select if the filtering applies to All, New, and Synced items.
* Note that if the option **New items** is selected, the filtering will apply only to the new items, and the already synced items will continue to sync and update. If the option **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. It is possible to filter more than one option for each field.
* Select **Apply** after creating the filters and **Save** the integration.
#### 14. Test the Integration
* Create test issues or tasks in Jira or Asana and observe how they synchronize.
* Ensure 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
Following this guide lets you set up the Jira-Asana integration with Getint. This configuration supports data synchronization of issues, tasks, and workflows across development and project management tools, allowing teams to collaborate while connecting developers and project managers.
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).
# Jira - Asana: Subtasks Synchronization
Making sure your tasks and subtasks play well between Jira and Asana is vital for smooth teamwork. This step-by-step guide will walk you through the process, making it easy to map, configure, and sync tasks and subtasks seamlessly.
### **Mapping Tasks and Subtasks:**
1. **Task and Subtask Mapping:**
* Ensure tasks and subtasks are appropriately mapped between Jira and Asana. Match their counterparts in both tools for effective synchronization.
2. **Enable the Synchronization:**
* Click on the subtasks mapping, navigate to the hierarchy section, and select "Synchronize Subtasks relationship."
* Enable the synchronization for the Subtasks relationships.
* Configure subtask relationships in the dropdown menu. Decide if they should sync with their counterpart or get linked to a specific parent task by providing its ID.
* Click "Apply" and "Save" to apply the changes to the integration.
{% embed url="" %}
1. **Initiating Sync for Subtasks:**
* By configuring the settings, any new subtasks will be automatically synchronized with their parent tasks on Jira and Asana.
2. **Handling Existing Items:**
* If the subtasks were created before this synchronization, it will be necessary to perform a migration to ensure that the older subtasks are migrated. Follow the necessary migration steps to create the relevant link.
**Conclusion:** Synchronizing tasks and subtasks in the Jira<>Asana integration improves collaboration and ensures consistent project management. By mapping, configuring relationships, and enabling synchronization, you create a seamless workflow between the two platforms.
# Jira Azure DevOps integration
Integrating Jira (Software/Service Management) and Azure DevOps (Cloud/OnPremise) is essential for optimizing workflows. Getint's integration bridges the gap between tracking project milestones in Jira and managing development tasks in Azure DevOps. Whether you're using Jira Cloud, Data Center/Server, or On-Premise, this guide will help you set up an efficient information flow between these platforms. Enhance your productivity and collaboration across teams of all sizes by following this guide.
#### Step-by-Step Setup Guide
**1. Access the Getint App in Jira**
Navigate to Jira, go to "Apps," and select "Jira - Azure DevOps Integration."
**2. Create Integration**
* Choose "Continuous Sync" for ongoing data synchronization or "Migration" if you need to transfer existing data.
**3. Token Generation (Password for Jira Cloud)**
For Jira Cloud, generate a Jira token. This token will act as your password:
* Go to Atlassian Account Settings.
* Navigate to Security and generate an API token, then use this token as the password for Jira integration.
**4. Choose the Apps and Establish Connections**
* Ensure you are logged in as a user with admin rights, click "Select App" and choose Jira.
* Select "Create New" to establish a new connection with your Jira instance and add the URL of your Jira instance.
* Enter the login credentials of the admin user.
**5. Select the Jira Project**
* Once the connection is established, choose the Jira project you want to connect to from the dropdown menu.
**6. Connect to Azure DevOps**
* Select the Azure DevOps app and tap on "Create a new connection." Use the Personal token created following the instructions in the guide: [Connections](https://docs.getint.io/guides/quickstart/connection#azure-devops).
* Tap on "Connect."
* Name the connection, input your email, and paste the token generated. Then click "Add."
* Select the Azure DevOps connection and choose the database you want to synchronize.
**7. Map Types**
* Map the Jira issue types you want to sync with Azure DevOps tasks, such as mapping an Azure DevOps task to a Jira issue or a Jira bug.
* Consider using the "Quick Build" beta feature for automated type and field mapping, which can streamline the setup process. Quick Build is currently in the beta stage; if you have feedback or questions about it, please contact our [support.](https://getintio.atlassian.net/servicedesk/customer/portals)
**8. Field Mapping**
Review or manually map which fields to integrate and sync within supported mapped types, make any necessary modifications, and hit apply.
#### Advanced Settings
**9. Comments**
If needed, enable the integration and synchronization of comments.
* Filter the comments with the criteria that suit you. Make them private/public or use the preferred attributes, such as created date or author.
**10. Statuses Mapping**
Enable status mapping, then map the statuses as desired.
* Specify the Azure DevOps field that will keep the status data from Jira, ensuring fields in Azure DevOps mirror your Jira setup (e.g., Done - Closed, Open - Active).
#### **Finalize Integration**
**11. Name the Integration and Click "Create"**
* Name your integration and click "Create" to finalize the setup.
**12. Filtering**
It is possible to filter the synchronization to have it customized for your needs and requirements.
**UI Filtering Option:**
* Click on the filtering icon near the app icon in your integration. This will apply to that side of the integration.
* Select if the filtering applies to All, New, and Synced items.
* Note that if the option "New items" is selected, the filtering will apply only to the new items, and the already synced items will continue to sync and update. If the option "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. It is possible to filter more than one option for each field.
* Select Apply once you have created the filters and "Save" the integration.
**13. Test the Integration**
To ensure everything is working correctly, create tasks and go to the reporting section to verify that all syncs are functioning as expected. If you encounter any issues, please contact our [support team](https://getintio.atlassian.net/servicedesk/customer/portals) for assistance.
#### Conclusion
Leverage the Jira-Azure DevOps integration by Getint to optimize your project management and development processes. This seamless integration enhances collaboration and productivity, ensuring that all tasks and milestones are accurately tracked and managed across platforms. Please contact our [Support Team](https://getint.io/help-center) or [Schedule a Demo](https://calendly.com/d/cpws-jb2-8xx/demo-call-all-team), if you require further assistance.
# How to Setup a Connection with Azure DevOps On-Premise
Connecting your On-Premise infrastructure with Azure can significantly enhance your organization’s capabilities by leveraging cloud resources while maintaining control over your local environment. With this detailed article, you can establish a connection between your Azure DevOps On-Premise infrastructure and any of our supported tools.
### Requirements and Recommendations
Before you begin, ensure you have the following:
* Administrative access to your Azure on-premise environment and the other app you’re integrating.
* Necessary permissions to create and manage projects, types, and fields within the applications.
* Service accounts with the required privileges for integration. It is not recommended to use personal accounts to build your integration. Additionally, it is important to note that comments are added as the user you chose to create the connection. The original author will still appear in the comment footer, but it will be attributed to the user who established the connection.
### Establishing the Connection
1. Launch Getint and look for the **Azure DevOps** in the apps selection.
2. Click **Create New Connection.**
3. Add the **URL** of your server/deployment. Please ensure you use only the main **URL** without any additional information, such as project destinations, and so on.
* These are examples of how URLs should be entered:
* `https://mytfs.internal.com`
* `http://1.32.312.32`
* `https://devops.local:8080/tfs`
* `http://10.0.0.1:8080/tfs`
* Please avoid entering URLs this way:
* `https://devops.local:8080/tfs/Collection/Project`
* `http://10.0.0.1:8080/tfs/tfs/DefaultCollection/Project`
* `http://1.32.312.32/DefaultCollection/Project`
* `https://mytfs.internal.com/SomeCollection/`
{% hint style="danger" %}
If the URLs are not entered correctly, the tool will display an error message, and the connection will not be established.
{% endhint %}
4. Enter the connection details such as the **Connection Name, Collection Name, Username, Password / Personal Access Token**.
5. You can create your **Personal Access Token** by going to the **Security** settings in your Azure Server.
6. Navigate to **Personal access tokens** and click on **+** **New Token.** Then, name your token and authorize it for **Full access.**
7. Return to the connection screen and paste your new token in the appropriate field. Finally, click **Add** at the bottom right to save this connection.
8. Your new connection will be available in the **Select Connection** dropdown list when integrating with Azure DevOps.
9. After selecting the connection, you will be prompted to choose the project you will be syncing. Now click **Connect,** and you’ll be ready to start syncing tasks/issues.
{% hint style="info" %}
If you experience any issues establishing a connection or have any doubts, feel free to contact our support team [here.](https://getint.io/help-center)
{% endhint %}
# Jira - Azure DevOps: Epics and Subtasks Synchronization
Integrating Jira with Azure DevOps can significantly improve team collaboration and workflows. One of the key aspects of this integration is syncing Epics and Subtasks between the two platforms. This article will guide you through the process of setting up and maintaining subtask synchronization using a third-party tool called Getint.
### How to Map Epics and Subtasks
#### 1. Mapping Epics and Subtasks:
* Ensure that Epics and Tasks are mapped accordingly between Jira and Azure DevOps. Match the counterpart items on both sides of the integration.
Example of the correct order for hierarchy levels.
{% hint style="warning" %}
When mapping Epics from Jira, don't forget to also map the **Epic Name** (if available). Otherwise, the epics will fail to create.
{% endhint %}
#### 2. Enable the Epic and Subtask Links:
* Open the Task - Task type mapping. Then, click on the **Hierarchy** tab, and check the box to enable the **Epic relationship**. Afterward, display the dropdown option and select the corresponding parent link for both sides.
* For Subtasks, access the relevant type mapping. Next, activate the **Synchronize Subtasks relationship**. Finally, open the dropdown menu and choose the **Parent Link** option. Determine whether the subtasks should synchronize with their counterpart or be linked to a specific parent task by providing the task's ID.
* After enabling this feature, any new Epics and Subtasks will be automatically synchronized with their parent/child task on Jira and Azure DevOps.
{% embed url="" %}
* Click **Apply** to submit the changes and save your integration.
#### 3. Considerations to Take:
* **Respect hierarchy levels:** Use Quickbuild to automatically align type mappings and create links. For manual integration, order issues correctly to prevent sync errors: **Epics** first, **Stories/Tasks/Bugs** second, and **Subtasks** last.
* **For existing projects:** Move or bulk-move issues in order, starting with Epics, followed by Tasks and Subtasks. This ensures proper sync with existing parents on the other side.
{% hint style="warning" %}
Do not modify the **Hierarchy** options within Epics, as this will break the integration. Only enable relationships for Stories/Tasks/Bugs and Subtasks.
{% endhint %}
# Syncing Dependencies between Jira and Azure DevOps using Getint
## Linking Work Items for Getint Integration
Dependencies allow teams to establish relationships between work items, such as blocked tasks, predecessors, successors, or related work. Synchronizing these relationships is essential when multiple teams collaborate across Jira and Azure DevOps.
Because Jira and Azure DevOps use different dependency models, synchronizing these relationships manually can be difficult. Getint acts as an intermediary, translating dependency information between both systems so that linked work remains connected regardless of the platform being used.
This article explains how to configure dependency synchronization between Jira and Azure DevOps using Getint.
### Understanding Dependencies
Azure DevOps stores dependencies as **Related Work**, whereas Jira stores dependencies as **Linked Items**.
Depending on your process template, Azure DevOps and Jira may provide:
* System-defined links
* Process-defined links
* User-defined links
Common examples include:
* Parent / Child
* Predecessor / Successor
* Related
Before configuring dependencies in Getint, make sure the desired Work Item Link type exists in both Azure DevOps and Jira.
#### In Jira, dependencies are called Linked Work Items:
#### In Azure DevOps, they are called Related Work:
### Setting Up Dependencies
#### Jira - Jira Integration:
1. **Configure Dependencies in Jira:**
* Jira comes ready with the linking issues option enabled. Verify your system setup for any adjustments, and if needed [Configure Dependencies in Jira for your plan](https://support.atlassian.com/jira-software-cloud/docs/configure-dependencies-in-jira-for-advanced-roadmaps/).
2. **Syncing Jira-Jira Dependencies with Getint:**
* Open your Getint instance, select the integration tab, and choose the integration.
* Access the Dependencies section to configure settings.
* Match project dependencies on both ends and ensure corresponding links for accurate mirroring.
* Click **Apply** and then **Save** to enact changes. The next synchronization will update dependencies for new tasks based on matched fields.
{% embed url="" %}
{% hint style="info" %}
If you are dealing with legacy tasks that have not been migrated, anticipate potential errors by migrating them first, so they synchronize correctly.
{% endhint %}
#### **Jira - Azure DevOps Integration:**
1. **Understanding Work Item Links in Azure DevOps:**
* Azure DevOps offers **Related Work** options for linking tasks, featuring system-defined, process-defined, or user-defined link types. To learn more about how to create a Work link in DevOps, see the guides: [Link work items to objects](https://learn.microsoft.com/en-us/azure/devops/boards/backlogs/add-link?view=azure-devops) and [Reference guide for link types](https://learn.microsoft.com/en-us/azure/devops/boards/queries/link-type-reference?view=azure-devops\&source=recommendations).
2. **Syncing Jira-DevOps Dependencies with Getint:**
* Open the integration tab and choose the integration.
* Navigate to Dependencies to configure settings.
* Align Jira dependencies with their Azure DevOps-related work items links.
* Click **Apply** and then **Save** to implement changes. The next sync will seamlessly integrate the new dependencies.
* Getint will then update tasks with the corresponding Work link based on matched fields, applying to new and migrated items. Ensure non-migrated tasks have the necessary link field.
{% embed url="" %}
{% hint style="warning" %}
When mapping fields, do not select the **Linked Issues** option in dropdowns. Use the Dependency box for creating dependencies between platforms.
Links will be established only if both items intended to be linked within the app have already been synchronized by Getint. Otherwise, they will be skipped.
{% endhint %}
### Conclusion
By configuring dependency synchronization in Getint, you can keep relationships between work items consistent across Jira and Azure DevOps. This keeps blockers, predecessors, successors, and related tasks connected, helping teams collaborate more effectively while continuing to work in their preferred platforms.
If you encounter any issues or need assistance configuring dependencies, please visit our [Help Center](https://getint.io/help-center) or [schedule a demo](https://calendly.com/d/cpws-jb2-8xx/demo-call-all-team) with our team. We're happy to help you build the integration that fits your workflow.
# Jira ClickUp integration
Getint integrates Jira with ClickUp for seamless cross-platform project management, blending Jira’s issue tracking with ClickUp’s task management. It supports Jira Cloud and Server with real-time, one- or two-way sync between issues and tasks. This no-code guide enables quick setup to boost team productivity and collaboration.
### Why Choose Getint for Atlassian Native Integrations?
Getint specializes in **secure**, **SOC 2 Type 2 certified integrations** for enterprise environments, ensuring that data synchronization across platforms like **Jira**, **Azure**, **ClickUp**, **Confluence**, and **Trello** remains efficient and secure. With **no-code integrations for Jira**, Getint makes it easy for teams to connect platforms without extensive technical knowledge, offering solutions that integrate natively with Atlassian tools.
### Step-by-Step Guide to Integrating Jira with ClickUp
Here’s how to set up **Jira-ClickUp integration** using **Getint’s real-time sync** solution:
#### 1. Access the Getint App in Jira
* Navigate to Jira, go to **Apps**, and select **ClickUp Integration for Jira** to start the integration process.
{% hint style="info" %}
**Pro tip**: Ensure you’re logged in as an admin user to avoid permission issues during setup.
{% endhint %}
#### 2. Create a New Integration
* Click **Create Integration** for ongoing sync or **Migration** to transfer existing data.
#### 3. Token Generation (Password for Jira Cloud)
* For Jira Cloud, generate a Jira token. This token will act as your password:
* Go to Atlassian Account Settings.
* Navigate to Security and generate an API token, then use this token as the password for Jira integration.
#### 4. Choose the Apps and Establish Connections
* Ensure you are logged in as a user with admin rights, click on "Select App" and choose Jira.
* Select "Create New" to establish a new connection with your Jira instance and add the URL of your Jira instance (omit the trailing "/").
* Enter the login credentials of the admin user.
#### 5. Select the Jira Project
* Once the connection is established, a dropdown menu will appear. Choose the **Jira project** you want to sync with ClickUp.
#### 6. Generate ClickUp API Token
* Follow our video to generate the **ClickUp API Token** and create the connection.
{% embed url="" %}
* Then select the connection, and choose the space and folder you wish to sync.
#### 7. Map Issue Types and Fields
Consider using the **Quick Build beta feature** for automated type and field mapping to simplify the setup.
* Define how Jira issue types will sync with ClickUp task types.
* Example: map a **Jira Task** to a **ClickUp Task** or a **Jira Bug** to a **ClickUp Task**.
* Manually map or modify fields like **Title**, **Description**, **Assignee**, and **Custom Fields** between Jira and ClickUp.
#### 8. Status Mapping
* Consider using the **Quick Build** beta feature for automated type and field mapping, which can streamline the setup process
* Enable and configure **Status Mapping** between Jira and ClickUp.
* Map Jira statuses (e.g., **To Do**, **In Progress**, **Done**) to their corresponding ClickUp statuses for consistency.
#### 9. Sync Comments and Attachments
* If needed, enable the synchronization of comments and attachments. Customize comment syncing, such as making them private or public, or providing the parameters that fit your synchronization. Then apply and save the integration.
#### 10. UI Filtering Option:
* Click on the filtering icon near the app icon in your integration. This will apply to that side of the integration.
* Select if the filtering applies to All, New, and Synced items.
* Note that if the option “*New items”* is selected, the filtering will apply only to the new items, and the already synced items will continue to sync and update. If the option “*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. It is possible to filter more than one option for each field.
* Once you create the filters, name the integration and save it.
#### 11. Test the Integration
* Create sample tasks in both Jira and ClickUp to ensure the integration works as expected.
* Check the **reporting section** to confirm the sync is successful. If issues arise, visit our [**Help Center**](https://getint.io/help-center) for assistance.
#### Advanced Settings for Your Atlassian Integration
For users looking for advanced integration features, Getint allows for custom configurations, such as syncing **comments**, **attachments**, and **custom fields** between Jira and ClickUp. You can also tailor **workflow automation** to your team’s needs, ensuring that your data flows exactly how you need it to.
# Jira Freshdesk integration
The Getint platform connects Jira and Freshdesk to unify project management and customer support. It supports fast ticket syncing, automated workflows, and shared visibility across teams, helping reduce response times and keep both sides aligned. Follow this 2026 guide for a quick setup that works for businesses of all sizes. Use the Jira-Freshdesk integration with Getint for better project and support management.
***
### Jira-Freshdesk Licensing Model
The **Freshdesk-Jira licensing model** with Getint fits various integration needs. Here is an overview:
**Standard Licensing**
* A Getint license is required only on Jira, enabling data synchronization between Freshdesk and Jira.
* This keeps setup simple and quick, with no extra configurations needed in Freshdesk.
**Flexible License**
* For managed services companies or organizations integrating four or more instances (same or different tools), Getint provides a **Flexible License**. This custom option covers a set number of connections (up to 10 instances) without tool limits. You can switch integrated tools anytime during the license term for maximum adaptability.
For licensing details, visit our [**Pricing Page**](https://docs.getint.io/licensing).
**Requirements to Build Your Integration**
* The **Getint app** must be installed in Jira.
* Comments are attributed to the user who created the connection. Therefore, we recommend using dedicated **Service Accounts** for both instances. Create a Service Account here: [How to Create a Jira Service Account](https://docs.getint.io/getting-started-with-the-platform/preparing-for-the-integration#how-to-create-a-jira-service-account).
* A **Personal Access Token** is required for Jira authentication, and an **API key** is required for Freshdesk. Learn more here: [Access Tokens](https://docs.getint.io/guides/quickstart/connection#jira).
### Setting Up Your Jira-Freshdesk Integration
#### 1. Access the Getint App in Jira:
* Navigate to Jira, go to Apps, and select the Getint app (Freshdesk/Freshservice integration for Jira in this case).
#### 2. Create Integration
Click **Create Integration** and select either:
* **Continuous Sync** for ongoing synchronization.
* **Migration** for a one-time data transfer.
#### 3. Generate a Jira API Token
* Log in to your Atlassian account and navigate to **Account Settings** > **Security** > **API Tokens** > **Create and manage API tokens**.
* Choose between **Create API token** and **Create API token with scopes**. Generate the token, copy it, and securely store the token, as it will be used as the password for Jira Cloud.
{% hint style="info" %}
For detailed steps and specific permissions for the Jira user, refer to our guide [Connection](https://docs.getint.io/guides/quickstart/connection#jira).
{% endhint %}
#### 4. Generate a Freshdesk API Key
* Log in to your Freshdesk account, click on your profile picture in the top right corner, and select **Profile Settings**.
* In the sidebar on the right, click on the **View API key** button to access the API key.
* Complete the captcha verification, if prompted, and copy the API Key for integration.
{% embed url="" %}
{% hint style="warning" %}
You can reset the API Key to stop an app from connecting to your helpdesk if you need to. Remember that doing so will also disconnect other apps that use the same key.
{% endhint %}
#### 5. Create a Connection with Jira and Freshdesk
**Jira Connection:**
* Select the **Jira** app. Then enter your Jira instance **URL** (without "/" at the end), username, the Access token generated, and click **Add**.
* Select the Jira project(s) you want to synchronize and select **Connect**.
**Freshdesk Connection:**
* Select **Freshdesk** as the connection app, and click **Create New Connection**.
* Enter your Freshdesk instance URL in the **URL** field and click **Next**.
* Assign a name to the connection and enter the API key as the password.
* **Add** the connection and select it.
#### 6. Configure Type Mapping
* **Quick Build**: Use the Quick Build feature to automatically map fields and types between applications, simplifying the process.
* **Manual Mapping**: For greater control, manually map the types yourself. This approach lets you tailor the mapping to meet your specific needs. Click **+ Add type mapping** to add Jira issue types (Task, Bug, Epic, Story, Incident) and map them to the Freshdesk **Ticket** type.
* For example, **Task ↔ Incident**.
#### 7. Configure Field Mapping
Select the fields to synchronize, such as **Title**, **Description**, **Assignees**, and **Custom** fields. In addition to this, for the Freshdesk connection to work, it is necessary to map some key fields:
1. **Reporter/Requester Mapping**:
* Link the **Reporter** field in Jira to the **Requester** field in Freshdesk.
* Ensure that requesters on both platforms are mapped to allow Getint to match them appropriately.
* In case a fixed value, like an email, is supposed to be defined for this field, the configuration can be done like this:
2. **Status Field**:
* Freshdesk mandates status mapping for the integration to function. A default value needs to be set for the ticket creation only, pointing towards the Freshdesk side, avoiding this option being picked up again when the issues are updated:
3. **Priority Field**:
* Mapping the priority field is necessary for the integration's operation within Freshdesk.
After all fields and types have been configured, give your integration a distinctive name and save the settings.
#### 8. Assignee Mapping
Use the assignee mapping option to match Jira assignees to Freshdesk agents, enabling precise synchronization of ticket ownership. For more details, visit our doc: [Assignees (users) mapping](https://docs.getint.io/getintio-platform/workflows/assignees-users-mapping).
#### 9. Status Mapping
Map status fields to align between Jira and Freshdesk. For example, **To do** in Jira could be mapped to **Open** in Freshdesk.
#### 10. How to Manage Comments & Attachments:
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 distinct logic flows for these items:
* **Bidirectional**: Updates to comments or attachments in either Jira or Freshdesk will reflect in the other platform.
* **Unidirectional to Jira**: Data flows exclusively from Freshdesk to Jira. Changes made in Jira will not sync back to Freshdesk.
* **Unidirectional to Freshdesk**: Data flows exclusively from Jira to Freshdesk. Changes made in Freshdesk will not sync back to Jira.
**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 specific fields while keeping other mapped fields active.
**Comment Privacy**
You can control the visibility of comments synced between Jira and Freshdesk. The integration supports toggling between public and private comments freely, so you can configure public comments on one side to appear as private on the other, and vice versa. This gives your teams full control over what is visible to end users versus internal staff across both platforms.
**Jira Group Restrictions**
For Jira, you can limit comment synchronization based on **Jira Groups**. This ensures that only comments belonging to specific groups are shared across your projects, which is useful for organizations that need to keep certain discussions internal to a team or department.
{% hint style="info" %}
For a full overview of filtering logic, AND/OR conditions, and date-based filtering, refer to the [Comments Filtering documentation](https://docs.getint.io/getintio-platform/workflows/filtering-items-for-integration-in-getint/how-to-filter-comments).
{% endhint %}
#### 11. Filtering Options
Customize synchronization by applying filters:
* After completing your integration, add filters to each app by clicking the filter icon next to its app icon. This will affect the corresponding side of the integration.
* Choose the filter scope:
* **ALL items filter**: Rules will be verified for every item before synchronization.
* **NEW items filter**: Rules will be verified only for newly created items that have not yet been synced.
* **SYNCED items filter**: Rules will be verified for items that were already synced in the past.
Add values for the filters and click **Apply**. For more details on how to use the filter, refer to our [Filtering Guide](https://docs.getint.io/getintio-platform/workflows/items-filtering).
**JQL Filtering (Jira-Specific)**
Beyond standard item filtering, integrations involving Jira support **Jira Query Language (JQL)**. This allows for granular control over exactly which issues enter the synchronization scope.
**Custom JQL Configuration**
In the **Custom JQL** field, you can input a specific query to refine your data set. The platform automatically appends your custom string to the system-generated filters.
* **Logic:** The final query used to identify issues is effectively `(System Filters) AND (Your Custom JQL)`.
* **Example:** If you only want to sync issues currently being worked on, you would enter: `status IN ("In Progress")`
**Key Benefits**
* **Precision**: Target specific issue types, labels, or custom field values that standard UI filters might not cover.
* **Performance**: By narrowing the scope of the sync via JQL, you reduce the volume of data the platform needs to scan, often resulting in faster processing.
* **Flexibility**: Use advanced operators (e.g., `WAS`, `CHANGED`, `is EMPTY`) to handle complex workflow requirements.
#### 12. Test the Integration
Before deploying the integration to your production environment, perform a verification cycle to ensure data flows correctly between **Freshdesk** and **Jira**.
**Verification Steps**
1. **Initial Creation:**
* Create a test ticket in **Freshdesk**.
* Create a test issue in **Jira**.
* Confirm that the items appear in the respective platforms according to your mapping rules.
2. **Field & Feature Validation:**
* **Updates**: Modify a mapped field and confirm the change reflects on the linked platform.
* **Comments & Attachments**: Add a comment or upload a file to verify the sync direction and visibility.
* **Status Transitions**: Change the status (e.g., move a Jira issue to "In Progress") and verify the **Freshdesk** ticket updates accordingly.
3. **Audit Logs:**
* Access the **Logs** tab within the platform.
* Review the entries to confirm successful executions and identify any potential mapping errors or permission conflicts.
***
### Conclusion
By following these steps, you have established a functional integration between **Jira** and **Freshdesk**. This setup automates the synchronization of records, workflows, and communication, bridging the gap between support and development teams.
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).
# Jira Freshservice integration
The Getint platform links Jira and Freshservice to unify project management and IT service management (ITSM). It supports fast ticket syncing, automated workflows, and shared dashboards, cutting response times by up to 40%. Follow our 2026 guide for quick setup across all business sizes. Use Jira-Freshservice integration with Getint for better project and support management.
***
### Jira-Freshservice Licensing Model
The **Freshservice-Jira licensing model** with Getint fits various integration needs. Here’s an overview:
#### Standard Licensing
* A Getint license is required only on Jira, enabling data synchronization between Freshservice and Jira.
* This keeps setup simple and quick, with no extra configurations needed in Freshservice.
#### Flexible License
* For managed services companies or organizations integrating four or more instances (same or different tools), Getint provides a **Flexible License**. This custom option covers a set number of connections (up to 10 instances) without tool limits. You can switch integrated tools anytime during the license term for maximum adaptability.
For licensing details, visit our [**Pricing Page**](https://docs.getint.io/licensing).
#### Requirements to Build Your Integration
* The **Getint app** must be installed in Jira.
* Comments are attributed to the user who created the connection. Therefore, we recommend using dedicated **Service Accounts** for both instances. Create a Service Account here: [How to Create a Jira Service Account](https://docs.getint.io/getting-started-with-the-platform/preparing-for-the-integration#how-to-create-a-jira-service-account).
* **Personal Access Tokens** are required for Jira and Freshservice authentication. Learn more here: [Access Tokens](https://docs.getint.io/guides/quickstart/connection#jira).
### Setting Up Your Jira-Freshservice Integration
#### 1. Access the [Getint](https://marketplace.atlassian.com/apps/1227929/freshservice-freshdesk-integration-for-jira-2-way-work-sync?hosting=cloud\&tab=installation) App in Jira:
* Navigate to Jira, go to Apps, and select the Getint app (Freshdesk/Freshservice integration for Jira in this case).
#### 2. Create Integration
Click **Create Integration** and select either:
* **Continuous Sync** for ongoing synchronization.
* **Migration** for a one-time data transfer.
#### 3. Generate a Jira API Token
* Log in to your Atlassian account and navigate to **Account Settings** > **Security** > **API Tokens** **> Create and manage API tokens**.
* Choose between **Create API token** and **Create API token with scopes**. Generate the token, copy it, and securely store the token, as it will be used as the password for Jira Cloud.
{% hint style="info" %}
For detailed steps and specific permissions for the Jira user, refer to our guide [Connection](https://docs.getint.io/guides/quickstart/connection#jira).
{% endhint %}
#### 4. Generate a Freshservice Personal Access Token
* Log in to your Freshservice account, click on your profile picture in the top right corner, and select **Profile Settings**.
* On the new page, click on **Show API Key** to access the API key.
* Complete the captcha verification, if prompted, and copy the API Key for integration.
{% embed url="" %}
{% hint style="info" %}
You can reset the API Key to stop an app from connecting to your helpdesk if you need to. Remember that doing so will also disconnect other apps that use the same key.
{% endhint %}
#### 5. Create a Connection with Jira and Freshservice
**Jira Connection:**
* Select the **Jira** app. Then enter your Jira instance **URL**, username, the Access token generated, and click **Add**.
* Select the Jira project(s) you want to synchronize and select **Connect**.
**Freshservice Connection:**
* Select **Freshservice** as the connection app, and click **Create New Connection**.
* Enter your Freshservice instance URL in the **URL** field and click **Next**.
* Assign a name to the connection and enter the API token.
* **Add** the connection and select it.
{% hint style="info" %}
For detailed steps on how to configure your **Freshservice API token**, please refer to our guide [Connection](https://docs.getint.io/guides/quickstart/connection#freshservice).
{% endhint %}
#### 6. Configure Type Mapping
* **Quick Build**: Use the Quick Build feature to automatically map fields and types between applications, simplifying the process.
* **Manual Mapping**: For greater control, manually map the types yourself. This approach lets you tailor the mapping to meet your specific needs. Click **+ Add type mapping** to add the types (Incident, Task, Bug, Epic, Story) by yourself.
* For example, **Task ↔ Service Request**.
#### **7. Configure Field Mapping**
Select the fields to synchronize, such as **Title**, **Description**, **Assignees**, and **Custom** fields. In addition to this, for the Freshservice connection to work, it is necessary to map some key fields:
1. **Reporter/Requester Mapping**:
* Link the **Reporter** field in Jira to the **Requester** field in Freshservice.
* Ensure that requesters on both platforms are mapped to allow Getint to match them appropriately.
* In case a fixed value, like an email, is supposed to be defined for this field, the configuration can be done like this:
2. **Status Field**:
* Freshservice mandates status mapping for the integration to function. A default value needs to be set for the ticket creation only, pointing towards the Freshservice side, avoiding this option being picked up again when the issues are updated:
3. **Priority Field**:
* Mapping the priority field is necessary for the integration's operation within Freshservice.
* After all fields and types have been configured, give your integration a distinctive name and save the settings.
#### 8. Assignee Mapping
Use the assignee mapping option to match Jira assignees to Freshservice assignees, enabling precise synchronization of task ownership. For more details, visit our doc: [Assignees (users) mapping](https://docs.getint.io/getintio-platform/workflows/assignees-users-mapping).
#### 9. Status Mapping
Map status fields to align between Jira and Freshservice. For example, **To do** in Jira could be mapped to **Open** in Freshservice.
#### 10. How to Manage Comments & Attachments:
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 distinct logic flows for these items:
* **Bidirectional**: Updates to comments or attachments in either Jira or Freshservice will reflect in the other platform.
* **Unidirectional to Jira**: Data flows exclusively from Freshservice to Jira. Changes made in Jira will not sync back to Freshservice.
* **Unidirectional to Freshservice**: Data flows exclusively from Jira to Freshservice. Changes made in Freshservice will not sync back to Jira.
**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 specific fields while keeping other mapped fields active.
#### 11. Filtering Options
Customize synchronization by applying filters:
* After completing your integration, add filters to each app by clicking the filter icon next to its app icon. This will affect the corresponding side of the integration.
* Choose the filter scope:
* **ALL items filter**: Rules will be verified for every item before synchronization.
* **NEW items filter**: Rules will be verified only for newly created items that have not yet been synced.
* **SYNCED items filter**: Rules will be verified for items that were already synced in the past.
Add values for the filters and click **Apply**. For more details on how to use the filter, refer to our [Filtering Guide](https://docs.getint.io/getintio-platform/workflows/items-filtering).
**JQL Filtering (Jira-Specific)**
Beyond standard item filtering, integrations involving Jira support **Jira Query Language (JQL)**. This allows for granular control over exactly which issues enter the synchronization scope.
**Custom JQL Configuration**
In the **Custom JQL** field, you can input a specific query to refine your data set. The platform automatically appends your custom string to the system-generated filters.
* **Logic:** The final query used to identify issues is effectively `(System Filters) AND (Your Custom JQL)`.
* **Example:** If you only want to sync issues currently being worked on, you would enter:
`status IN ("In Progress")`
**Key Benefits**
* **Precision**: Target specific issue types, labels, or custom field values that standard UI filters might not cover.
* **Performance**: By narrowing the scope of the sync via JQL, you reduce the volume of data the platform needs to scan, often resulting in faster processing.
* **Flexibility**: Use advanced operators (e.g., `WAS`, `CHANGED`, `is EMPTY`) to handle complex workflow requirements.
#### 12. Test the Integration
Before deploying the integration to your production environment, perform a verification cycle to ensure data flows correctly between **Freshservice** and **Jira**.
**Verification Steps**
1. **Initial Creation:**
* Create a test ticket in **Freshservice**.
* Create a test issue in **Jira**.
* Confirm that the items appear in the respective platforms according to your mapping rules.
2. **Field & Feature Validation:**
* **Updates**: Modify a mapped field and confirm the change reflects on the linked platform.
* **Comments & Attachments**: Add a comment or upload a file to verify the sync direction and visibility.
* **Status Transitions**: Change the status (e.g., move a Jira issue to "In Progress") and verify the **Freshservice** ticket updates accordingly.
3. **Audit Logs:**
* Access the **Logs** tab within the platform.
* Review the entries to confirm successful executions and identify any potential mapping errors or permission conflicts.
***
### Conclusion
By following these steps, you have established a functional integration between **Jira** and **Freshservice**. This setup automates the synchronization of records, workflows, and communication, bridging the gap between support and development teams.
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).
# Jira GitHub integration
Integrating Jira with GitHub using Getint connects your project tracking and code management through two-way synchronization. Whether you’re logging issues in Jira or handling code in GitHub, this setup keeps both teams aligned and informed.
This step-by-step guide shows you how to configure the integration using Personal Access Tokens for authentication.
***
### GitHub-Jira Licensing Model
The GitHub-Jira licensing model with Getint is designed to accommodate different integration needs. Here’s an overview:
#### Standard Licensing
* A Getint license is only required on Jira, allowing seamless data synchronization between GitHub and Jira.
This makes setup simpler and faster, without the need for additional configurations in GitHub.
#### Flexible License
* For managed services companies or organizations looking to integrate four or more instances (regardless of whether they are the same or different tools), Getint offers a **Flexible License.** This custom license covers a specific number of connections (i.e., up to 10 instances) without restrictions on the tools involved. You can also swap the integrated tools while the license remains active, offering unparalleled flexibility.
For more details on licensing, visit our [**Pricing Page**](https://docs.getint.io/billing-and-services/licensing).
#### Requirements to Build Your Integration:
* The **Getint app** must be installed in Jira.
* Comments are attributed to the user who created the connection. Therefore, we recommend using dedicated Service Accounts for both instances.
* Jira instances must have a dedicated user and an associated API token with permissions to read, write, view, and modify the project.
* **Personal Access Tokens** are required for Jira and GitHub authentication. You can find the steps to generate the access token for your connectors here: [Connection Guide](https://docs.getint.io/guides/quickstart/connection#github).
### Setting Up Your GitHub-Jira Integration
#### 1. Access the Getint App in Jira
* Navigate to **Apps** and select **Jira - GitHub Integration**.
#### 2. Create Integration
* Click **Create integration** or **Migration**.
#### 3. Token Generation (Password for Jira Cloud)
* For Jira Cloud, generate a Jira token. This token will act as your password:
* Go to **Atlassian Account Settings**.
* Navigate to **Security** and go to **Generate and manage** **API tokens**, then select an API token or an API token with scopes.
* After creation, use this token as the password for Jira integration. More information about access tokens for Jira [here](https://docs.getint.io/guides/quickstart/connection#jira).
#### **4. Generate a GitHub Personal Access Token**
GitHub supports two token types. You can use a Classic token or a Fine-grained token, depending on your needs.
**Generating a GitHub Token (Classic):**
* Log in to your GitHub account.
* Go to **Settings**, then **Developer settings**.
* Select **Personal access tokens** and click **Generate new token**. In the dropdown menu, select **Generate new token (Classic)**.
* Provide a name for your token, select the scopes like the example in the [Connection Guide](https://docs.getint.io/guides/quickstart/connection#github), and save.
* Copy the token and store it securely, as it will only be visible once.
{% embed url="" %}
**Generating a Fine-Grained Token:**
* Log in to your GitHub account.
* Go to **Settings**, then **Developer settings**.
* Select **Personal access tokens**, then go to **Fine-grained personal access tokens**.
* Click **Generate new token**. Choose a name for your token, set the expiration date and repository access, and provide the necessary access permissions in the dropdown list.
* Copy the token and store it securely, as it will only be visible once.
{% embed url="" %}
#### 5. Connect to Jira
* In Getint, enter your Jira instance URL, username, and the API token.
* Use the **Personal Access Token** for Jira Cloud.
* Select the Jira project you wish to integrate with GitHub.
#### 6. Enter GitHub Token in Getint
* Once you have generated a Personal Access Token in your GitHub instance, you will now have the option to connect the tool with Getint.
* Paste the GitHub Personal Access Token into the API token field.
* Select the GitHub repository or the Project you want to sync with Jira.
* Click Save to establish the connection.
#### 7. Issue Type Mapping
* Map the Jira issue types you want to sync with GitHub tasks, such as mapping a GitHub Task to a Jira task or a Jira bug to a GitHub task.
* Consider using the **Quick Build** beta feature for automated type and field mapping, which can streamline the setup process.
#### 8. Field Mapping
* Review or manually map fields within mapped types, including title, description, and assignees.
* Add your desired fields, and define the sync direction (unidirectional or bi-directional) with the arrows.
#### 9. Assignee Mapping
* Use the assignee mapping option to match Jira assignees to GitHub collaborators, enabling precise synchronization of task ownership. For more details, visit our doc: [Assignees (users) mapping](https://docs.getint.io/getintio-platform/workflows/assignees-users-mapping).
{% hint style="warning" %}
When syncing **projects**, make sure your repository is linked to the target project. If it isn’t, assignees won’t appear in the mapping dropdown.
{% endhint %}
#### 10. Status Mapping
* Map status fields to align between Jira and GitHub. For example, **To do** in Jira could be mapped to **Opened** in GitHub.
#### 11. Comments & Attachments
* When enabling comment synchronization, you can filter by criteria such as created date, author, or visibility (public/private).
{% hint style="warning" %}
**Attachment Limitation**: Attachments are currently limited to one-way syncing and are only supported from Jira to GitHub. Attachments in GitHub will not sync to Jira
{% endhint %}
#### 12. Filtering:
* It is possible to filter the synchronization to have it customized 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 on the filtering icon near the app icon in your integration. This will apply to that side of the integration.
* Select if the filtering applies to All, New, and Synced items.
* Note that if the option **New items** is selected, the filtering will apply only to the new items, and the already synced items will continue to sync and update. If the option **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. It is possible to filter more than one option for each field.
* Select **Apply** after creating the filters and **Save** the integration.
#### 13. Test the Integration
* Create test issues or tasks in Jira or GitHub and observe how they synchronize.
* Ensure 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
By following this guide, you can successfully integrate **Jira** and **GitHub** using Getint. This setup enables smooth synchronization of issues, tasks, and workflows between development and project management tools, helping teams collaborate more effectively and bridging the gap between developers and project managers.
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).
# Jira GitLab integration
Integrating Jira with GitLab enables seamless synchronization between project management and version control, enhancing collaboration and workflow efficiency. Follow this comprehensive guide to quickly and easily set up a two-way integration between Jira and GitLab.
***
### GitLab-Jira Licensing Model
The GitLab-Jira licensing model with Getint is designed to accommodate different integration needs. Here’s an overview:
#### Standard Licensing
* A Getint license is only required on Jira, allowing seamless data synchronization between GitLab and Jira.
This makes setup simpler and faster, without the need for additional configurations in GitLab.
#### Flexible License
* For managed services companies or organizations looking to integrate four or more instances (whether the tools are the same or different), Getint offers a **Flexible License.** This custom license covers a specific number of connections (i.e., up to 10 instances) without restrictions on the tools involved. You can also swap the integrated tools while the license remains active, offering unparalleled flexibility.
For more details on licensing, visit our [**Pricing Page**](https://docs.getint.io/billing-and-services/licensing).
#### Requirements to Build Your Integration:
* The **Getint app** must be installed in Jira.
* Comments are attributed to the user who created the connection. Therefore, we recommend using dedicated Service Accounts for both instances.
* Jira instances must have a dedicated user and an associated API token with permissions to read, write, view, and modify the project.
* **Personal Access Tokens** are required for Jira and GitLab authentication. You can find the steps to generate the access token for your connectors here: [Connection Guide](https://docs.getint.io/guides/quickstart/connection#gitlab).
#### Setting Up Your GitLab-Jira Integration
#### 1. Access the Getint App in Jira
* Navigate to **Apps** and select **Jira - GitLab Integration**.
#### 2. Create Integration
* Click **Continuous Sync** or **Migration**.
#### 3. Token Generation (Password for Jira Cloud)
* For Jira Cloud, generate a Jira token. This token will act as your password:
* Go to **Atlassian Account Settings**.
* Navigate to **Security** and go to **Generate and manage** **API tokens**, then select an API token or an API token with scopes.
* After creation, use this token as the password for Jira integration. More information about access tokens for Jira [here](https://docs.getint.io/guides/quickstart/connection#jira).
#### 4. Generate GitLab Token
* Log in to your GitLab account. In the top-left or top-right corner (depending on your version), click on your **Avatar/Profile Picture** and select **Preferences**.
* In the left-hand sidebar, look for the **Access** section (usually near the top) and select **Personal access tokens**.
* Click **Generate token** to open the form, and ensure you select **Legacy token** or **Fine-grained Token**.
For specific permissions, please follow the video tutorials below:
**GitLab Legacy Token Tutorial**
{% embed url="" %}
**GitLab Fine-grained Token Tutorial**
{% embed url="" %}
#### 5. Connect to Jira
* Ensure you are logged in as a user with admin rights, click on **Select App**, and choose Jira.
* Select **Create New Connection** to establish a new connection with your Jira instance and add the URL of your Jira instance (omit the trailing "/").
* Enter the login credentials of the admin user.
#### 6. Select the Jira Project
* Once the connection is established, choose the Jira project you want to connect to from the dropdown menu.
#### 7. Connect to GitLab
* If no connection is established yet, create a new one.
* Use the GitLab token generated as a password.
#### 8. Select GitLab Project
* Select the established GitLab connection and choose the project you want to integrate with.
#### 9. Type Mapping
* Map the Jira issue types you want to sync with GitLab issues, such as mapping a GitLab issue to a Jira task or a Jira bug to a GitLab issue.
* Consider using the **Quick Build** beta feature for automated type and field mapping, which can streamline the setup process.
#### 10. Field Mapping
* Review or manually map which fields to integrate and sync within the mapped types, including title, description, assignees, custom fields, and more.
#### 11. Assignee Mapping
* Map and match assignees according to your desired configuration. For more details, visit our doc: [Assignees (users) mapping](https://docs.getint.io/getintio-platform/workflows/assignees-users-mapping).
#### 12. Comments
* If needed, enable the integration and synchronization of comments.
* Filter the comments with the criteria that suit you. Make them private/public or use the preferred attributes, such as created date or author.
#### 13. Attachments
* Navigate to the **Comments & Attachments** tab within your Jira-GitLab type mappings and toggle on the **Synchronize attachments** setting.
* You can find your GitLab Cookie by right-clicking on your GitLab Groups page and selecting **Inspect**. Go to the **Network** tab, refresh the page, click on the item labeled **groups**, and look for the **Cookie** information inside the **Headers** tab.
{% hint style="warning" %}
Sometimes the developer tools won't display any data for the cookie header. To fix this, click on your Group or Project, and this should make the options visible.
{% endhint %}
* Copy the information and paste it into the **GitLab Cookie Header** field in Getint. Click **Apply** to submit the changes and save your integration.
* Ensure to test the attachments after enabling them.
{% hint style="warning" %}
Currently, attachments are only supported one way from GitLab to the other app in the integration. Also, no API is available to download and upload attachments through a Gitlab integration. As a result, this alternative remains the only option for downloading attachments from synced comments as long as they come from GitLab.
{% endhint %}
#### 14. Finalize Integration
* Name your project and click **Create** to finalize the integration setup.
#### 15. Filtering
It is possible to filter the synchronization to have it customized for your needs and requirements.
**UI Filtering Option:**
* Click on the filtering icon near the app icon in your integration. This will apply to that side of the integration.
* Select if the filtering applies to All, New, and Synced items.
* Note that if the option “*New items”* is selected, the filtering will apply only to the new items, and the already synced items will continue to sync and update. If the option “*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. It is possible to filter more than one option for each field.
* Select **Apply** once you have created the filters and Save the integration.
#### Conclusion
Following these steps, you can effectively integrate Jira with GitLab, ensuring smooth synchronization of tasks, issues, and workflows between the two platforms. This setup enhances collaboration and streamlines project management processes.
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).
# Attachments Sync in GitLab Integration
As of now, there’s a limitation to syncing attachments from GitLab. It doesn’t support attachments natively, but it is possible to sync them with a workaround by providing a cookie header.
### How to sync attachments
1. Please open your type mappings in your Jira Gitlab integration and go to the **Comments & Attachments** tab. Enable **Synchronize attachments:**
2. Get the **Cookie header** from your GitLab account. Use the developer's tool (F12 on Windows) within your GitLab’s groups page and go to **Network** > **Groups** > Click on **Headers** and scroll down to **Cookie**.
3. Copy the information and paste it into the **GitLab Cookie Header** field in Getint. Click **Apply,** to submit the changes and save your integration.
4. Make sure to test the attachments after enabling the feature.
{% hint style="warning" %}
Currently, attachments are only supported one way from GitLab to the other app in the integration. Also, no API is available to download and upload attachments through a Gitlab integration. As a result, this alternative remains the only option for downloading attachments from synced comments as long as they come from GitLab.
{% endhint %}
# Jira HubSpot integration
In today's fast-paced business environment, integrating your project management tools with customer relationship management platforms is essential for maintaining seamless operations and maximizing efficiency. Getint's Jira-Hubspot integration brings together the robust issue-tracking capabilities of Jira with the dynamic CRM functionalities of Hubspot, ensuring a continuous flow of information and enhanced collaboration across your teams. Whether you're looking to set up a two-way or a one-way integration, this comprehensive guide will help you establish a streamlined connection, boosting productivity and facilitating superior project management.
### Step-by-Step Setup Guide
#### **1. Access the Getint App in Jira**
Navigate to "Apps" and select "Hubspot Integration for Jira"
#### **2. Create Integration**
Click "Create integration" for ongoing sync or "Migration" to transfer existing data: [Migration Guide](https://docs.getint.io/guides/migration).
#### **3. Token Generation (Password for Jira Cloud)**
For Jira Cloud, generate a Jira token. This token will act as your password:
* Go to Atlassian Account Settings.
* Navigate to Security and generate an API token, then use this token as the password for Jira integration.
#### **4. Choose the Apps and Establish Connections**
* Ensure you are logged in as a user with admin rights, click "Select App" and choose Jira.
* Select "Create New" to establish a new connection with your Jira instance and add the URL of your Jira instance (omit the trailing "/").
* Enter the login credentials of the admin user.
#### **5. Select the Jira Project**
* Once the connection is established, choose the Jira project you want to connect to from the dropdown menu.
#### **6. Connect to Hubspot**
* Select the Hubspot app and tap on "Create a new connection" Use the Personal token created following the instructions in the guide: [Connections](https://docs.getint.io/guides/quickstart/connection#hubspot)
* Tap on "Connect"
#### **7. Type Mapping**
Map the Jira issue types you want to sync with Hubspot tasks, such as mapping a Hubspot task to a Jira issue or a Jira bug.
Consider using the "Quick Build" beta feature for automated type and field mapping, which can facilitate the setup process.
#### **8. Field Mapping**
Review or manually map which fields to integrate and sync within supported mapped types, make any necessary modifications, and hit apply
{% hint style="warning" %}
To keep your tickets syncing correctly, you MUST map the "Ticket Status" field to a fixed value called "New," just like in the picture above. This lets Jira send new and updated tickets over to HubSpot without any issues. If you don’t do this, you’ll run into a sync error when Jira tries to share data with HubSpot.
The Quick Build feature will add this field mapping by default, but you can also add it manually by selecting Add Field Mapping > HubSpot > Ticket Status > Fixed Value and entering the status for newly created tickets. For most customers, this value is "New," but you can use your status, such as "Open" or "To Do." In these cases, simply enter the corresponding value. For example, map the "Ticket Status" field to the fixed value "To Do."
{% endhint %}
Getint now supports the Satisfaction field in Jira, enabling seamless synchronization and integration of satisfaction ratings across platforms. This new feature ensures that customer feedback and satisfaction metrics are consistently tracked and managed within your Jira projects. This enhancement reflects Getint’s dedication to offering comprehensive and adaptable integration solutions that cater to evolving user needs.
An example of how the Satisfaction field is located in Jira Service Management
The Satisfaction field, located in Jira Service Management, can be utilized to track customer feedback in your Jira-HubSpot integration, enhancing your ability to monitor and improve customer satisfaction.
{% hint style="info" %}
If you need custom development or are trying to sync a field that isn't supported, please reach out to our [Service Center](https://getint.io/help-center) or [Schedule a Demo Call](https://calendly.com/d/cpws-jb2-8xx/demo-call-all-team).
{% endhint %}
### Advanced Settings
#### **9. Comments**
If needed, enable the integration and synchronization of comments.
* Filter the comments with criteria that suit you. Make them private/public or use the preferred attributes such as created date or author.
#### **10. Statuses Mapping**
Enable status mapping, then map the statuses as desired.
* Specify the Hubspot field that will keep the status data from Jira, ensuring fields in Hubspot mirror your Jira setup (e.g., To do - To do, Done - Done).
{% hint style="danger" %}
**Note:** In HubSpot, each mapped type has a different status field. For example, a Deal maps to Stage, while a Ticket maps to Ticket Status. Identify the correct field for the mapped type to ensure the status transition syncs properly.
{% endhint %}
### Finalize Integration
#### **11. Name the Integration and Click "Create"**
Name your integration and click "Create" to finalize the setup.
#### **12. Filtering**
It is possible to filter the synchronization to have them customized for your needs and requirements.
**UI Filtering Option:**
* Click on the filtering icon near the app icon in your integration. This will apply to that side of the integration.
* Select if the filtering applies to All, New, and Synced items.
* Note that if the option "New items" is selected, the filtering will apply only to the new items, and the already synced items will continue to sync and update. If the option "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. It is possible to filter more than one option for each field.
* Select Apply once you created the filters and "Save" the integration.
#### **13. Test the Integration**
To ensure everything is working correctly, create tasks and go to the reporting section to verify that all syncs are functioning as expected. If you encounter any issues, please contact our support team for assistance.
### Conclusion
Following these steps, you can effectively integrate Jira with Hubspot, ensuring smooth synchronization of tasks, issues, and workflows between the two platforms. This setup enhances collaboration and project management processes.
For further assistance contact our support at our [Support Center](https://getint.io/help-center).
# Jira Jira integration
Integrating Jira with Jira through Getint gives teams a reliable way to connect project management and collaboration workflows. The integration synchronizes data across different projects on the same platform, so users can track and manage Jira tickets, tasks, bugs, and epics across multiple Jira environments.
For example, a company building several products, such as mobile phones, computers, and smartwatches, can put this to use. Each development team works within its own Jira environment, while Getint connects them by integrating and filtering the relevant projects. Teams collaborate effectively, and access restrictions stay in place.
***
### Jira Jira Licensing Model:
The Jira Jira licensing model with Getint is designed to accommodate various integration scenarios. Here's a breakdown:
* **Standard Dual Licensing:** This model requires the Getint license to be installed on both Jira instances involved in the integration. This ensures that each instance is properly licensed and can communicate seamlessly.
* **Remote License:** For situations where installing the Getint app on both Jira instances is not feasible (e.g., when integrating with a partner company that doesn't want to install any additional apps), Getint offers a **Remote License** for a fixed fee. This provides a flexible solution for such cases.
* **Flexible License:** For managed services companies or organizations looking to integrate four or more instances (regardless of whether they are the same or different tools), Getint offers a **Flexible License.** This custom license covers a specific number of connections (i.e., up to 10 instances) without restrictions on the tools involved. You can also swap the integrated tools while the license remains active, offering unparalleled flexibility.
For more information about our licensing options, please read [more.](https://docs.getint.io/billing-and-services/licensing)
### Requirements to Build Your Integration:
* The Jira-Jira Getint app must be installed on both instances unless you’re opting for a **Remote License** (app installed on a single instance only)**.**
* Both Jira instances should include a dedicated user and an associated API token. These users must have permission to read, write, view, and modify the project.
* Comments are attributed to the user who created the connection. Therefore, we recommend using dedicated **Service Accounts** for both instances. Create a Service Account here: [How to Create a Jira Service Account](https://docs.getint.io/getting-started-with-the-platform/preparing-for-the-integration#how-to-create-a-jira-service-account).
* Personal Access Tokens to establish the connections. More information about creating API tokens here: [Access Tokens & Requirements | Getint: Where every ticket finds it's place.](https://docs.getint.io/guides/quickstart/connection#jira)
### Setting Up Your Jira Integration
#### **1. Access the Getint App in Jira:**
* Navigate to Jira, go to **Apps**, and select the Getint app (Jira - Jira integration in this case).
#### 2. Create Integration
Click **Create Integration** and select either:
* **Continuous Sync** for ongoing synchronization.
* **Migration** for a one-time data transfer.
#### 3. Generate a Jira Cloud API Token
* Log in to your Atlassian account and navigate to **Account Settings** > **Security** > **API Tokens** > **Create and manage API tokens**.
* Choose between **Create API token** and **Create API token with scopes**. Generate the token, copy it, and securely store the token, as it will be used as the password for Jira Cloud.
#### Creating a Jira Cloud Token
{% embed url="" %}
{% hint style="info" %}
For detailed steps and specific permissions for the Jira user, refer to our guide [Connection](https://docs.getint.io/guides/quickstart/connection#jira).
{% endhint %}
#### **Generate a Jira Data Center API token API token**
Unlike Jira Cloud, the Data Center does not require a token and can be accessed using an email and password. If you choose to use a token, leave the **email** option blank on the Getint platform:
1. Log in to your Jira Data Center instance.
2. Click on the Avatar at the top right of the screen.
3. Select **Profile** and then **Personal Access Tokens**.
4. Click on **Create Token**, provide a name for your token, and specify whether the token will expire and when.
5. Copy the token and store it in a safe location.
{% embed url="" %}
#### 4. Establish a Connection with Jira:
* Select the **Jira** app. Then enter your Jira instance **URL** (without "/" at the end), username, the Access token generated, the URL of the instance hosting the Getint Forge app in the bottom field, and click **Add**.
* Select the Jira project(s) you want to synchronize and select **Connect**.
#### 5. Choose and Connect the Second Jira Project:
* Repeat the process on the other side. Since you are connecting Jira with Jira, repeat the steps.
{% embed url="" %}
#### 6. Configure Type Mapping:
* **Quick Build (Beta)**: Utilize the Quick Build feature to automatically map fields and types between your applications. This feature simplifies the process.
* **Manual Mapping:** For greater control, manually map the types yourself. This approach lets you tailor the mapping to meet your specific needs. Click **+ Add type mapping** to add Jira issue types (Task, Bug, Epic, Story, Incident) and map them one-to-one.
#### 7. Configure Field Mapping
* Select the fields to synchronize, such as **Title**, **Description**, **Assignees**, and **Custom** fields. After all fields and types have been configured, give your integration a distinctive name and save the settings.
#### 8. Assignees Mapping:
* Map assignees according to your organization’s requirements.
#### 9. Status Mapping
Map status fields to align between Jira and Jira. For example, **To do** in Jira, one Jira could be mapped to **Open** in the other Jira.
#### 10. How to Manage Comments & Attachments:
* Review the **Comments & Attachments** tab. These features are enabled by default, but you can adjust them as needed to suit your organization's requirements.
* You can also modify the sync direction for comments and attachments: **Both ways,** **only to Jira A (left),** or **only to Jira B (right).**
{% hint style="info" %}
You can disable comments and attachments entirely if they are not needed or are restricted in your organization.
{% endhint %}
**Synchronization Directions**
The platform supports three distinct logic flows for these items:
* **Bidirectional**: Updates to comments or attachments in either Jira or Jira will reflect in the other platform.
* **Unidirectional to Jira**: Data flows exclusively from Jira to Jira. Changes made in Jira will not sync back to Jira.
* **Unidirectional to Jira**: Data flows exclusively from Jira to Jira. Changes made in Jira will not sync back to Jira.
**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 specific fields while keeping other mapped fields active.
**Comment Privacy**
You can control the visibility of comments synced between Jira and Jira. The integration supports toggling between public and private comments freely, so you can configure public comments on one side to appear as private on the other, and vice versa. This gives your teams full control over what is visible to end users versus internal staff across both platforms.
**Jira Group Restrictions**
For Jira, you can limit comment synchronization based on **Jira Groups**. This ensures that only comments belonging to specific groups are shared across your projects, which is useful for organizations that need to keep certain discussions internal to a team or department.
{% hint style="info" %}
For a full overview of filtering logic, AND/OR conditions, and date-based filtering, refer to the [Comments Filtering documentation](https://docs.getint.io/getintio-platform/workflows/filtering-items-for-integration-in-getint/how-to-filter-comments).
{% endhint %}
#### 11. Filtering Options:
Customize synchronization by applying filters:
* After completing your integration, add filters to each app by clicking the filter icon next to its app icon. This will affect the corresponding side of the integration.
* Choose the filter scope:
* **ALL items filter**: Rules will be verified for every item before synchronization.
* **NEW items filter**: Rules will be verified only for newly created items that have not yet been synced.
* **SYNCED items filter**: Rules will be verified for items that were already synced in the past.
Add values for the filters and click **Apply**. For more details on how to use the filter, refer to our [Filtering Guide](https://docs.getint.io/getintio-platform/workflows/items-filtering).
**JQL Filtering (Jira-Specific)**
Beyond standard item filtering, integrations involving Jira support **Jira Query Language (JQL)**. This allows for granular control over exactly which issues enter the synchronization scope.
**Custom JQL Configuration**
In the **Custom JQL** field, you can input a specific query to refine your data set. The platform automatically appends your custom string to the system-generated filters.
* **Logic:** The final query used to identify issues is effectively `(System Filters) AND (Your Custom JQL)`.
* **Example:** If you only want to sync issues currently being worked on, you would enter: `status IN ("In Progress")`
**Key Benefits**
* **Precision**: Target specific issue types, labels, or custom field values that standard UI filters might not cover.
* **Performance**: By narrowing the scope of the sync via JQL, you reduce the volume of data the platform needs to scan, often resulting in faster processing.
* **Flexibility**: Use advanced operators (e.g., `WAS`, `CHANGED`, `is EMPTY`) to handle complex workflow requirements.
#### 12. Test the Integration
Before deploying the integration to your production environment, perform a verification cycle to ensure data flows correctly between your JIRAs.
**Verification Steps**
1. **Initial Creation:**
* Create a test ticket in the initial **Jira**.
* Create a test issue in the secondary **Jira**.
* Confirm that the items appear on the respective platforms according to your mapping rules.
2. **Field & Feature Validation:**
* **Updates**: Modify a mapped field and confirm the change reflects on the linked platform.
* **Comments & Attachments**: Add a comment or upload a file to verify the sync direction and visibility.
* **Status Transitions**: Change the status (e.g., move a Jira issue to "In Progress") and verify the **Jira** ticket updates accordingly.
3. **Audit Logs:**
* Access the **Logs** tab within the platform.
* Review the entries to confirm successful executions and identify any potential mapping errors or permission conflicts.
***
### Conclusion
By following these steps, you have established a functional integration between your **Jira** workspaces. This setup automates the synchronization of records, workflows, and communication, bridging the gap between support and development teams.
For further assistance, please get in touch with 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).
# Getint Instance URL
The **Getint instance URL** is a unique identifier for a Getint installation. It is used to establish secure connections between Jira instances, validate licenses, and expose important instance metadata. This article explains what the Getint instance URL is, where to find it, and how it’s used in cross-instance configurations.
### What Is the Getint Instance URL?
The Getint instance URL uniquely represents a Getint instance running within a Jira environment. It allows Getint to:
* Identify another Getint instance on the “other side” of a connection.
* Validate licensing without querying Jira directly.
* Exchange instance-level metadata, such as version and data residency.
From now on, the Getint instance URL is the **single source of truth** for instance identification and license checks.
### Obtain Your Getint Instance URL
Each Jira instance running Getint has its own Getint instance URL.
To find it:
1. Open the **Getint app** in your Jira instance.
2. Navigate to **Settings**, and open the **General** tab. Your **Getint instance URL** is displayed there.
This URL is generated automatically and is specific to that Getint installation.
### Adding the Getint Instance URL to the Connection
When setting up a connection between two Jira instances, you must retrieve the URL from the **counterpart** (the Jira instance you are connecting to).
{% hint style="info" %}
You do not need to provide the Getint instance URL in the connection that is running the integration.
The only exception is when a single Getint instance connects to two different Jira instances, for example, one on the left and another on the right. In this scenario, each connected Jira instance must have its corresponding Getint instance URL specified in the connection configuration.
{% endhint %}
1. Go to the connection configuration (**Workflows > Connections**), locate the Jira connection you want to update, and click the **3-dot button** below “Actions.”
2. Click on **Edit** to modify the connection.
3. Specify the **Getint instance URL of the partner** (Getint instance on the other side), and hit the **Update** button.
4. Now test your integration. This time, you shouldn’t experience any Jira licensing errors.
Once updated, the two Getint connections are linked, allowing for secure and accurate cross-instance communication.
### Licensing Behavior Using the Getint Instance URL
With Forge, licensing is now handled at the Getint level rather than through Jira directly.
* If **Jira 2 is licensed**, license validation is performed by querying the **Getint instance** identified by the provided instance URL.
* Getint no longer asks Jira whether a license exists.
* Instead, Getint asks the **other Getint instance**: “Is there an explicit license associated with this instance URL?”
### Summary
* Every Getint installation has a unique **Getint instance URL**.
* The instance URL is available in the **Getint app** > **Settings** > **General**.
* No need to specify an ID for your local Jira instance (the Jira that is running the integration), regardless of whether it is configured as the left or the right side of the connection. Just focus on grabbing the Getint URL for the counterpart instance.
* License validation is now performed via Getint using the instance URL, not Jira.
* Additional metadata, such as version and data residency, is tied to the instance URL.
Using the Getint instance URL ensures clear identification, accurate license validation, and a scalable foundation for cross-instance integrations.
### Need Assistance?
If you encounter any issues retrieving your Getint instance URL, configuring the connection, or validating licensing, please contact our [**Support Team**](https://getint.io/help-center) for assistance.
# Jira Jira licensing
Jira Jira Licensing Model Explained
**Overview of Our Licensing Model**
Our standard licensing approach is tailored to the number of connections or instances you're integrating. Simplified, this means you only need a single app installed on Jira to facilitate integration (e.g., connecting 1x Jira instance to 1x Azure DevOps requires just the Jira app).
**Special Considerations for Jira-Jira Integrations**
However, integrating Jira with another Jira (both Software and Service Management) instance necessitates a different model. Why the exception? Previously, our model did not differentiate between the sizes of the companies being integrated. This often led to scenarios where large enterprises were linked with smaller ones, paying only for the smaller instance's license but requiring enterprise-level support and generating data volumes typical of larger organizations. This discrepancy meant the costs incurred by us were not adequately covered by the licensing fees.
To address this, the basic requirement for Jira-Jira integrations is to have a valid license (app installed) on each Jira instance being connected by Getint. The integration can be managed from a single user interface on one of the Jira instances, with the app installation serving primarily for licensing purposes.
**Remote License Option**
We understand there might be situations where installing an app on both Jira instances is not feasible, such as when integrating with a partner company unwilling to install any Jira apps on their end. For these cases, we offer a "Remote License" for a fixed fee, providing a flexible solution to this challenge. For more details, please contact .
**Flexible License for Managed Services and Multi-Instance Integrations**
For managed services companies or any organization looking to integrate four or more instances (regardless of whether they are the same or different tools), we introduce our "Flexible License." This custom license fee covers a specific number of connections (e.g., up to 10 instances), without restrictions on the tools involved. You are also free to swap the integrated tools while the license remains active, offering unparalleled flexibility to adapt to changing needs.
For inquiries about our "Remote License" or "Flexible License" options, or for further clarification on our Jira licensing model, please reach out to us. We're here to ensure your integration process is smooth, compliant, and optimized for your specific business requirements.
# Time Tracking in Getint – One-Way Synchronization
In Getint, time-tracking synchronization is available, but there are some important distinctions to keep in mind. While the **Original Estimate** can be mapped both ways between systems, the **Remaining Estimate** and **Time Spent** are limited to one-way synchronization. These fields must be mapped to a text field in the target system. In this guide, we will explain how time-tracking synchronization works, and the best way to configure your mappings to ensure accurate and effective data flow.
### Understanding Time Tracking Fields
#### **1. Original Estimate:**
This field represents the initial estimate of time required to complete a task or issue.
* **Two-Way Synchronization**: You can map the **Original Estimate** field in both directions, meaning it can be updated and synced from either system.
#### **2. Remaining Estimate:**
This field represents the amount of time left to complete the task or issue.
* **One-Way Synchronization**: The **Remaining Estimate** can only be synced in one direction. It needs to be mapped to a text field in the target system. You will see a "read-only" indicator when configuring the mapping, meaning that changes made in the target system will not sync back.
#### **3. Time Spent:**
This field tracks the actual time that has been spent working on a task or issue.
* **One-Way Synchronization**:
Similar to the **Remaining Estimate**, the **Time Spent** field can only be synchronized in one direction and must be mapped to a text field. It cannot be updated from the target system and only serves as a reference.
{% hint style="warning" %}
Note: The mapping of these fields is disabled by default to map both ways.
{% endhint %}
### Configuring Time Tracking in Getint
To set up time tracking synchronization, follow these steps:
* **Original Estimate Mapping (Two-Way)**:
* When mapping the **Original Estimate**, you can choose to sync the field in both directions. This is useful if both systems need to keep track of the initial time estimates for tasks.
* Select the **Original Estimate** field in both systems during the field mapping process. Ensure that it is mapped as a two-way sync to allow updates from either side.
* **Remaining Estimate & Time Spent Mapping (One-Way)**:
* For the **Remaining Estimate** and **Time Spent**, select these fields in the source system.
* In the target system, map these fields to text fields. Since these fields are one-way sync only, you will see a "read-only" label when configuring the mappings, indicating that they can only be updated in the source system.
* Any updates made in the source system will be reflected as text in the target system.
### Key Considerations
* **Text Field Mapping**: Since **Remaining Estimate** and **Time Spent** are mapped to text fields in the target system, their values will not be interactable or updateable in the target system. They serve as a static reference point for the time-tracking data.
* **Read-Only Fields**: These fields are marked as "read-only" during the field mapping process, meaning that changes can only be made from the source system and not in the target system.
* **Consistency**: It's crucial to ensure that your team is aware of the one-way synchronization for the **Remaining Estimate** and **Time Spent** fields. All updates to these fields must be made in the source system to maintain accurate and consistent data across integrations.
### Conclusion
Time tracking in Getint provides valuable synchronization options but with some limitations. While the **Original Estimate** can be synchronized both ways, the **Remaining Estimate** and **Time Spent** fields are limited to one-way synchronization and must be mapped to text fields in the target system.
For more detailed guidance or assistance with configuring your time-tracking integration, visit our [Help Center](https://getint.io/help-center).
# Jira Monday.com integration
Integrating Jira with Monday.com using Getint improves workflows, strengthens communication, and makes migrations more efficient. Monday’s intuitive interface and flexible workflows work well alongside Jira’s powerful issue-tracking features. This integration keeps tasks, updates, and timelines aligned, helping teams stay organized and work more effectively.
With Getint, you can connect your Monday.com boards to Jira Cloud, Jira Data Center, or On-Premise environments, keeping tasks synchronized and up to date across your workspace.
***
### Monday-Jira Licensing Model
The Monday.com–Jira licensing model with Getint is designed to support different integration scenarios. Below is a quick overview:
#### Standard Licensing
* A Getint license is only required on the Jira side, simplifying the setup process and removing the need for additional configuration within Monday.com.
#### Flexible License
* For managed service providers or organizations planning to connect four or more instances (whether they involve the same tools or different platforms), Getint offers a **Flexible License**. This custom license covers a defined number of connections (for example, up to 10 instances) without limiting the types of tools you can connect. You can also change the connected tools while the license is active, giving you greater operational flexibility.
For more information about licensing options, visit our [**Pricing Page**](https://docs.getint.io/billing-and-services/licensing).
#### Requirements to Build Your Integration:
Before setting up the integration, make sure the following requirements are met:
* The Getint app must be installed in **Jira**.
* Comments are assigned to the user who creates the connection, so we recommend using dedicated service accounts for both systems.
* Jira instances should have a dedicated user with an API token that has permissions to read, write, view, and edit project data.
* **Personal Access Tokens** are required for Jira and Monday.com authentication. You can find the instructions for generating access tokens in the [Connection Guide](https://docs.getint.io/guides/quickstart/connection#monday.com).
### Setting Up Your Monday-Jira Integration
#### 1. Access the Getint App in Jira
* Navigate to **Apps** and select **Jira - Monday Integration**.
#### 2. Create Integration
* Click **Create integration** or **Migration**.
#### 3. Token Generation (Password for Jira Cloud)
* For Jira Cloud, generate a Jira token. This token will act as your password:
* Go to **Atlassian Account Settings**.
* Navigate to **Security** and go to **Generate and manage** **API tokens**, then select an API token or an API token with scopes.
* After creation, use this token as the password for Jira integration. More information about access tokens for Jira [here](https://docs.getint.io/guides/quickstart/connection#jira).
#### 4. Generate a Monday.com Personal Access Token
* Log in to your Monday.com account and follow the steps in the video below to create the **Access Token**.
{% embed url="" %}
* Make sure to securely store your token, as it will only be visible once.
#### 5. Connect to Jira
* In Getint, click on **Connect App** and choose Jira.
* Enter your Jira instance URL, username, and the API token.
* Use the **Personal Access Token** for Jira Cloud.
* Select the Jira project(s) you wish to integrate with Monday.com.
#### 6. Enter the Monday.com Token in Getint
Once you have generated a Personal Access Token in your Monday.com instance, you will now have the option to connect the tool with Getint.
* Click on **Connect App**, and choose Monday.com. Paste the **Monday.com Personal Access Token** into the API Token field.
* Select the board(s) you want to sync with Monday.com.
* Click **Connect** to establish the connection.
#### 7. Issue Type Mapping
* Map the Jira issue types you want to sync with Monday.com items, such as mapping a Monday.com Item to a Jira task or a Jira bug to a Monday.com Item.
* Consider using the **Quick Build** beta feature for automated type and field mapping, which can streamline the setup process.
#### 8. Item Routing
If you selected multiple projects/boards on either or both sides, you must define Item Routing. 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).
#### 9. Field Mapping
Review or manually map fields within mapped types, including title, description, and assignees.
Add your desired fields, and define the sync direction (unidirectional or bi-directional) with the arrows.
#### 10. Assignee Mapping
Use the assignee mapping option to match Jira assignees to Monday.com assignees, enabling precise synchronization of task ownership. For more details, visit our doc: [Assignees (users) mapping](https://docs.getint.io/getintio-platform/workflows/assignees-users-mapping).
#### 11. Status Mapping
Map status fields to align between Jira and Monday.com. For example, **To do** in Jira could be mapped to **New** in Monday.com.
#### 12. Comments & Attachments
When enabling comment synchronization, you can filter by criteria such as created date, author, or visibility (public/private).
{% hint style="danger" %}
Please be aware that replies to comments (also known as subcomments) are not supported by Getint, and they will not trigger synchronization. If an update is added before a sync is triggered, and a reply is subsequently added to the update, the tool will bring the subcomment to the other side. However, due to a technical limitation from Monday.com, we cannot guarantee that this will work consistently, so please manage expectations.
{% endhint %}
* To synchronize attachments, scroll down and enable the option.
{% hint style="warning" %}
As indicated in the Getint UI, inline images are not supported for Monday integrations. Also, attachments need to be uploaded from the **Files** column in your Monday board; otherwise, they will fail to sync.
{% endhint %}
#### 13. Filtering:
It is possible to filter the synchronization to have it customized 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 on the filtering icon near the app icon in your integration. This will apply to that side of the integration.
#### 14. Test the Integration
* Create test issues or tasks in Jira or Monday.com and observe how they synchronize.
* Ensure 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
Following this guide lets you set up the Jira-Monday.com integration with Getint. This configuration supports data synchronization of issues, tasks, and workflows across development and project management tools, allowing teams to collaborate while connecting developers and project managers.
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).
# Synchronizing Attachments in a Monday.com Integration
Our tool allows users to migrate and synchronize attachments from Monday tasks to other management software we support. However, please note that inline images are not currently supported for synchronization.
### Key Points and Considerations
* **File Size Limit:** Monday enforces a 500MB file size limit for task attachments. Be mindful of this limitation when dealing with large files.
* **Inline Images:** We currently do not support inline images. Please note that they won’t be properly synchronized.
* **Enabling the Feature:** Attachments are disabled by default. They need to be activated manually within your integration settings.
* **Attachments Limitation:** Uploading attachments from the **Files** section within the tasks is not supported. Attachments need to be uploaded from the **Files** column in your Monday.com board.
### How to Sync Attachments
1. Navigate to the **Comments & Attachments** section in the mapping configuration.
2. Scroll down to **Synchronize attachments** and enable the option.
3. Go to your **Monday.com** workspace and upload attachments from the **FILES** column in your **Monday.com board.**
{% hint style="warning" %}
Always upload attachments from the **FILES** column rather than the **Item/Task** menu to ensure file synchronization with the other app.
{% endhint %}
4. Choose the synchronization direction for your attachments. Options include **Both ways** (bi-directional sync), **Only to app A** (left)**,** and **Only to app B** (right) for unidirectional sync.
5. Click **Apply** at the bottom right to submit your changes. Then, **Save** your integration.
{% hint style="info" %}
If you’re experiencing difficulties syncing attachments or have any other questions, please contact us at our [Support Center.](https://getint.io/help-center)
{% endhint %}
# How to Insert Monday.com Items into Specific Groups Using Getint
Groups on Monday provide a way to organize tasks, projects, and workflows efficiently. When integrating with Jira, Asana, Azure DevOps, or other tools through Getint, users may need to automatically assign items to specific groups instead of having them placed in a default category.
This guide explains how to configure custom field mapping to ensure that items land in the correct group during synchronization.
### Why Assign Items to Specific Groups
By default, new tasks synced into Monday may not be placed in the intended group, requiring manual adjustments. Using custom field mapping, teams can ensure items are categorized correctly without additional effort.
#### Benefits
* Improves organization by ensuring items are placed in the right group automatically.
* Reduces the need to manually move tasks after sync.
#### **Step 1: Create a Custom Field in the Source Tool**
To enable group assignment, a custom field must be created in the source tool. This field will determine where each item is placed on Monday.
Since the process varies by platform, refer to the official instructions for creating custom fields. For this guide, we will use Jira - Monday integration:
* [**How to Create a Custom Field in Supported Software**](https://getintio.atlassian.net/wiki/spaces/Support/pages/898170881/How+to+Insert+Monday.com+Items+into+Specific+Groups+Using+Getint#) (full guide).
* **Jira** - follow the steps on [Create a Custom Field](https://support.atlassian.com/jira-cloud-administration/docs/create-a-custom-field/) and add the field to the issue types:
When setting up the field:
* Use a **Dropdown (Single Select) or Picklist** to match group values.
* Ensure that all issue types contain the new field.
#### **Step 2: Map the Custom Field to Monday.com** **Groups in Getint**
Once the custom field is set up, configure Getint to recognize and use it for group assignment.
* Open **Getint** and navigate to the integration.
* Select **Type Mapping** then add **Field Mapping** and locate the custom field created in Step 1. Map this field to the **Group** field in Monday.
* Click on the cog icon to match the groups.
* Define the synchronization direction:
* **Unidirectional (Source to Monday)** – Items are assigned a group based on the source tool but will not update if moved manually
* **Bidirectional (Sync Both Ways)** – Group changes will reflect in both systems
* Click **Save** to apply the mapping
{% hint style="warning" %}
The Group field **must be** mapped to a dedicated custom field instead of a status field, as statuses function separately in synchronization.
{% endhint %}
#### **Step 3: Test the Integration**
Once the setup is complete, verify that it functions correctly by testing with new items.
* Create a task in the source tool and set the **Group Assignment** field to a specific group.
* Wait for the sync to happen and check that the item appears in the correct group.
Ticket assigned to the Group selected
If items are not assigned as expected, review:
* The values entered in the custom field
* Field mapping settings in Getint
* Sync logs for potential mapping errors
### Conclusion
By mapping a custom field in the source tool to the **Group field**, users can ensure that items are automatically placed in the correct category, eliminating manual adjustments and improving workflow efficiency.
For further assistance, check the [**Getint Help Center**](https://getint.io/help-center) or contact support.
# Jira Notion integration
Getint’s Jira-Notion integration creates a unified workspace by syncing project data across platforms. Currently supporting title and description fields—with more mapping options on the roadmap—the integration is designed for rapid deployment via a **3-minute MVP setup**. To bridge any current feature gaps, Getint provides expert support, including **custom scripts and personalized onboarding**, to help teams navigate complex workflows.
***
### Notion-Jira Licensing Model
The Notion-Jira licensing model with Getint is designed to accommodate different integration needs. Here’s an overview:
#### Standard Licensing
* A Getint license is required only on Jira, enabling seamless data synchronization between Notion and Jira.
This makes setup simpler and faster, without the need for additional configurations in Notion.
#### Flexible License
* For managed services companies or organizations looking to integrate four or more instances (regardless of whether they are the same or different tools), Getint offers a **Flexible License.** This custom license covers a specific number of connections (i.e., up to 10 instances) without restrictions on the tools involved. You can also swap the integrated tools while the license remains active, offering unparalleled flexibility.
For more details on licensing, visit our [**Pricing Page**](https://docs.getint.io/billing-and-services/licensing).
#### Requirements to Build Your Integration:
* The **Getint app** must be installed in Jira.
* Comments are attributed to the user who created the connection. Therefore, we recommend using dedicated Service Accounts for both instances.
* Jira instances must have a dedicated user and an associated API token with permissions to read, write, view, and modify the project.
* **Personal Access Tokens** are required for Jira and Notion authentication. You can find the steps to generate the access token for your connectors here: [Connection Guide](https://docs.getint.io/guides/quickstart/connection#notion).
### Setting Up Your Notion-Jira Integration
Set up your MVP integration in minutes with this step-by-step video guide.
{% embed url="" %}
#### 1. Access the Getint App in Jira:
* Navigate to Jira, go to **Apps**, and select the Jira Notion integration app.
* Select **Create Integration**, then **Continuous Sync** or **Migration** based on your requirements.
#### 2. Token Generation (Password for Jira Cloud)
* For Jira Cloud, generate a Jira token. This token will act as your password:
* Go to **Atlassian Account Settings**.
* Navigate to **Security** and go to **Generate and manage** **API tokens**, then select an API token or an API token with scopes.
* After creation, use this token as the password for Jira integration. More information about access tokens for Jira [here](https://docs.getint.io/guides/quickstart/connection#jira).
#### 3. Generate a Notion Personal Access Token
* Click the **ellipsis** (···) in the top-right corner of your Notion app.
* Select **Add a Connection** > **Manage Connections** > **Develop or Manage integrations**.
* Click **+ New Integration**, give it a name, and configure your permissions.
* Secure your **Internal Integration Secret** (API token) for the next step.
* Under **Content Access**, ensure you select the specific teamspace containing the project you want to sync.
{% embed url="" %}
* Make sure to securely store your token, as it will only be visible once.
#### 4. Connect to Jira
* In Getint, click on **Connect App** and choose Jira.
* Enter your Jira instance URL, username, and the API token.
* Use the Personal Access Token for Jira Cloud.
* Select the Jira project you wish to integrate with Notion.
{% hint style="warning" %}
You can only select one project when syncing with Notion. Selecting multiple projects will cause Notion to disappear from your available integration options.
{% endhint %}
#### 5. Configure Getint for Notion
* In the Getint app, choose **Notion** as the connection app.
* Select **Create a new connection**, name it, and provide the **API Token**.
* Select the connection you want to integrate.
* Choose the Notion database to synchronize.
{% embed url="" %}
#### 6. Map Types
* Link Jira types (Task, Bug, Epic, Story) to synchronize with Notion.
* Consider using the **Quick Build** beta feature for automated type and field mapping, which can streamline the setup process.
* **Manual Mapping**: For greater control, manually map the types yourself. This approach lets you tailor the mapping to meet your specific needs. Click **+ Add type mapping** to add the types (Task, Bug, Epic, Story) yourself.
* For example, **Task ↔ Task**.
{% embed url="" %}
#### 7. Field Mapping
* Map key fields such as **Title**, **Description**, **Assignees**, and **Custom** fields.
* You can use the arrows to distinguish the sync direction of the fields.
* Once your fields and types are configured, assign a unique name to your integration and save your settings.
{% embed url="" %}
{% hint style="warning" %}
The **Description** field in Notion supports a maximum of 2000 characters. To avoid sync errors and blank description fields when transferring text from Jira to Notion, ensure your content does not exceed this limit. Keeping descriptions concise and within the character count helps maintain data integrity and prevents synchronization issues.
{% endhint %}
#### 8. Assignee Mapping
Use the assignee mapping option to match Jira assignees to Notion assignees, enabling precise synchronization of task ownership. For more details, visit our doc: [Assignees (users) mapping](https://docs.getint.io/getintio-platform/workflows/assignees-users-mapping).
#### 9. Status Mapping
Map status fields to align between Jira and Notion. For example, **To do** in Jira could be mapped to **Open** in Notion.
#### 10. How to Manage Comments:
Check the **Comments** tab. These settings are active by default, but you can modify them to fit your specific requirements.
**Synchronization Directions**
The platform supports three distinct logic flows for these items:
* **Bidirectional**: Updates to comments in either Jira or Notion will reflect in the other platform.
* **Unidirectional to Jira**: Data flows exclusively from Notion to Jira. Changes made in Jira will not sync back to Notion.
* **Unidirectional to Notion**: Data flows exclusively from Jira to Notion. Changes made in Notion will not sync back to Jira.
**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 entirely. This prevents any data transfer for these specific fields while keeping other mapped fields active.
{% hint style="warning" %}
Attachment syncing is currently not supported for Notion integrations.
{% endhint %}
#### 11. Filtering
Customize synchronization by applying filters:
* After completing your integration, add filters to each app by clicking the filter icon next to its app icon. This will affect the corresponding side of the integration.
* Choose the filter scope:
* **ALL items filter**: Rules will be verified for every item before synchronization.
* **NEW items filter**: Rules will be verified only for newly created items that have not yet been synced.
* **SYNCED items filter**: Rules will be verified for items that were already synced in the past.
Add values for the filters and click **Apply**. For more details on how to use the filter, refer to our [Filtering Guide](https://docs.getint.io/getintio-platform/workflows/items-filtering).
{% embed url="" %}
**JQL Filtering:**
* Beyond standard item filtering, integrations involving Jira support **Jira Query Language (JQL)**. This allows for granular control over exactly which issues enter the synchronization scope.
**Custom JQL Configuration**
In the **Custom JQL** field, you can input a specific query to refine your data set. The platform automatically appends your custom string to the system-generated filters.
* **Logic:** The final query used to identify issues is effectively `(System Filters) AND (Your Custom JQL)`.
* **Example:** If you only want to sync issues currently being worked on, you would enter:
`status IN ("In Progress")`
**Key Benefits**
* **Precision**: Target specific issue types, labels, or custom field values that standard UI filters might not cover.
* **Performance**: By narrowing the scope of the sync via JQL, you reduce the volume of data the platform needs to scan, often resulting in faster processing.
* **Flexibility**: Use advanced operators (e.g., `WAS`, `CHANGED`, `is EMPTY`) to handle complex workflow requirements.
{% embed url="" %}
#### 12. Duplicate Setup and Select Different Projects
* Go to **Workflows**.
* Click on the 3 dots on the right side and select **duplicate**.
* A side panel will appear. Select a new name for the integration (by default, the integration will be called **copy of** if the same projects are established).
* In the dropdown menu, select the projects that you would like to integrate.
* For each side, select **Connect**. Then **Duplicate**.
* Save the new integration.
{% embed url="" %}
### Conclusion
By following these steps, you have established a functional integration between **Jira** and **Notion**. This setup automates the synchronization of records, workflows, and communication, bridging the gap between support and development teams.
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).
# Jira Salesforce integration
Integrating Salesforce with Jira using Getint improves team collaboration. Real-time data sync allows the management of customer requests, tasks, bugs, and projects without manual input. This integration supports Salesforce Lightning, Classic, and various Jira deployments, including Cloud, Data Center, and Service Management.
***
### **Salesforce-Jira Licensing Model**
The **Salesforce-Jira licensing model** with Getint is designed to accommodate different integration needs. Here’s an overview:
#### **Standard Licensing**
* A Getint license is only required on Jira, allowing seamless data synchronization between Salesforce and Jira.
* This makes setup simpler and faster, without the need for additional configurations in Salesforce.
#### **Flexible License**
* For managed services companies or organizations looking to integrate four or more instances (regardless of whether they are the same or different tools), Getint offers a **Flexible License.** This custom license covers a specific number of connections (i.e., up to 10 instances) without restrictions on the tools involved. You can also swap the integrated tools while the license remains active, offering unparalleled flexibility.
For more details on licensing, visit our [**Pricing Page**](https://docs.getint.io/billing-and-services/licensing)**.**
### **Requirements to Build Your Integration**
* The **Getint app** must be installed in Jira.
#### **Salesforce API Requirements**
Salesforce requires API access for integration. API access is enabled by default in the following editions:
* Enterprise Edition
* Unlimited Edition
* Performance Edition
* Developer Edition
API access is **NOT enabled** by default in:
* Group Edition
* Essentials Edition
* Professional Edition
{% hint style="info" %}
If using a Salesforce edition without API access enabled, please contact Salesforce support or refer to the Salesforce Help & Training Community.
{% endhint %}
#### **Authentication and Access Requirements**
* OAuth authentication is required to establish a secure connection between Salesforce and Jira.
* Comments are attributed to the user who created the connection. Therefore, we recommend using dedicated Service Accounts for both instances.
* Jira instances must have a dedicated user and an associated API token with permissions to read, write, view, and modify the project.
* **Personal Access Tokens** are required for Jira authentication. Learn more here: [Connection Guide](https://docs.getint.io/guides/quickstart/connection#salesforce).
### **Setting Up Your Salesforce-Jira Integration**
#### **1. Access the** [**Getint**](https://marketplace.atlassian.com/apps/1223930/issue-sync-integration-for-jira-getint-issue-sync?hosting=cloud\&tab=overview) **App in Jira:**
* Navigate to Jira, go to Apps, and select the Getint app (Salesforce integration for Jira in this case).
#### **2. Create Integration**
Click **Create Integration** and select either:
* **Continuous Sync** for ongoing synchronization.
* **Migration** for a one-time data transfer.
#### **3. Generate a Jira API Token**
* Log in to your Atlassian account and navigate to **Account Settings > Security**.
* Generate an API token.
* Copy and securely store the token, as it will be used as the password for Jira Cloud.
For detailed steps, refer to our guide [Connection](https://docs.getint.io/guides/quickstart/connection#jira).
#### **4. Create a connection to Jira and Salesforce and authorize Getint**
**Jira Connection:**
* Select the **Jira** app. Then enter your Jira instance **URL**, username, and Access token generated.
* Select the Jira project you want to synchronize and select **Connect**.
**Salesforce Connection:**
* Select **Salesforce** and click **Create a Connection**.
* Enter your Salesforce instance URL in the **URL** field and click **Next**.
* Assign a name to the connection and enter the **client\_id** and **client\_secret** credentials.
* **Add** the connection and select it.
{% hint style="info" %}
For detailed steps on configuring your **Salesforce credentials**, please refer to our guide [Connection](https://docs.getint.io/guides/integration-synchronization/jira-salesforce-integration/salesforce-oauth-authentication).
{% endhint %}
#### **5. Configure Type Mapping**
* **Quick Build (Beta):** Use the Quick Build feature to automatically map fields and types between applications, simplifying the process.
* **Manual Mapping:** For greater control, manually map the types yourself. This approach lets you tailor the mapping to meet your specific needs. Click **+ Add type mapping** to add the types (Case, Task, Bug, Epic, Story) by yourself.
* **Story ↔ Case**
#### **6. Configure Field Mapping**
* Select the fields to synchronize, such as **Title**, **Description**, **Assignees**, and **Custom** fields.
* Ensure synchronization flow is defined for each field, using the arrows and selecting **Apply**.
{% hint style="info" %}
Some custom field types may not be supported. Please check our [Connectors Salesforce page](https://docs.getint.io/getting-started-with-the-platform/apps-connectors/salesforce) for a list of supported fields. If a field is missing or you need custom development, visit our [Help Center](https://getint.io/help-center).
{% endhint %}
#### **7. Configure Status Mapping**
Ensure you are using the correct fields for each instance's status.
* Navigate to the **Status Mapping** tab.
* Use the dropdown menu to map Salesforce statuses to their Jira equivalents (e.g., **Open ↔ To Do**).
* **Apply** the status mappings.
#### **8. How to Manage Comments & Attachments:**
* Review the **Comments & Attachments** tab. These features are enabled by default but can be adjusted to meet your organization's needs.
* You can adjust the sync direction for comments and attachments to be bidirectional, **unidirectional to Jira**, or **unidirectional to Salesforce**. Also, you can completely disable comments and attachments if they are unnecessary or restricted in your organization.
{% hint style="warning" %}
Public/chatter comments and attachments do not automatically sync from Salesforce to Jira. To ensure they appear in Jira, update either the Salesforce ticket or the Jira ticket, depending on whether bidirectional sync is enabled.
{% endhint %}
#### **9. Filtering Option**
Customize synchronization by applying filters:
* After completing your integration, add filters to each app by clicking the filter icon next to its app icon. This will affect the corresponding side of the integration.
* Choose the filter scope:
* **ALL items filter:** Rules will be verified for every item before synchronization.
* **NEW items filter:** Rules will be verified only for newly created items that have not yet been synced.
* **SYNCED items filter:** Rules will be verified for items that were already synced in the past.
Add values for the filters and click **Apply**. For more details on how to use the filter, refer to our [Filtering Guide](https://docs.getint.io/getintio-platform/workflows/items-filtering).
**JQL Filtering (For Jira Side Only)**
* In addition to the Item Filtering options mentioned above, Jira apps also support JQL (Jira Query Language) Filtering, allowing you to refine and customize which items are included in the sync.
* Under the field Custom JQL, it is possible to provide a JQL, which will be the filter for your sync and appended to the one generated when searching for issues in Jira (i.e., status in (“In Progress”)).
* Name your integration and click on **Create** to save the integration.
#### **10. Test the Integration**
* Create a test case in Salesforce and a test task in Jira.
* Verify synchronization by performing actions like adding comments, attachments, or changing statuses.
* Check logs in Getint to ensure the integration is working as expected.
{% embed url="" %}
#### **11. Duplicating Your Setup and Selecting Different Projects:**
* Navigate to Workflows.
* Click the three dots on the right and choose Duplicate.
* A side panel will appear. Enter a new name for the integration, which defaults to "copy" if the same projects are used.
* In the dropdown menu, choose the projects to integrate.
* For each side, click Connect, then Duplicate.
* Save the new integration.
### **Conclusion**
At Getint, we're dedicated to providing exceptional support throughout your integration journey. Our team is committed to delivering the best customer experience. For any questions about this integration or assistance with the setup process, don't hesitate to open a ticket at our [Help Center](https://getint.io/help-center) or [Schedule a Demo](https://calendly.com/d/cpws-jb2-8xx/demo-call-all-team). We're here to help!
# Salesforce OAuth Authentication
Starting version 1.78, Salesforce customers must configure OAuth authentication, deprecating our previous connection method. To do this, start by creating the necessary credentials in Salesforce. These credentials will connect your Salesforce instance and Getint, facilitating smooth and efficient data synchronization.
### How to Set Up OAuth Authentication in Salesforce
1. Log in to your Salesforce instance, click the **Cog icon** in the top right corner of your screen, and click on **Setup** to open your user settings.
2. Go to **Platform Tools** > **Apps** > **External Client Apps** > **External Client App Manager.**
3. Click **New External Client App.**
4. Provide a **custom name**, **your email**, and the **API name.**
5. **Enable OAuth**:
* Scroll down and enable **OAuth.**
* Provide the **Callback URL:** `https://login.salesforce.com/services/oauth2/callback`.
* Select the **OAuth Scope:** The only one required is *Manage user data via APIs (API).*
{% hint style="info" %}
Salesforce requires the Callback URL to use HTTPS for security purposes.
{% endhint %}
6. Scroll down to the section **Flow Enablement** and enable **Client Credentials Flow**. Then, disable the rest of the options in the **Security** section.
7. **Create the External Client App**:
* Click **Create** at the bottom of the screen.
* After creation, navigate back to edit settings. The new Client should’ve been created.
8. **Edit Settings for the new Client**:
* Click **Edit**, and display the **OAuth Policies**.
9. Enable **Client Credentials Flow** and provide the username found under **Personal Information** in your profile. Then, click **Save** to submit your changes.
10. **Generate** `client_id` **and** `client_secret`**:**
* Switch from the **Policies** tab to the **Settings** tab.
* Click **Consumer Key and Secret**.
* It will redirect you to the verification screen.
* Copy the **Consumer Key (**`client_id`**)** and **Consumer Secret (**`client_secret`**)**.
With these credentials, you can create a connection with Salesforce in Getint.
11. **Create a Salesforce Connection in Getint**:
* Select **Salesforce** and click **Create a Connection.**
* Enter your **Salesforce Instance URL** in the URL field and click **Next.**
* Name the connection and provide the **client\_id** and **client\_secret.**
* Add and select the connection to finalize the process.
{% hint style="warning" %}
Ensure to use the correct URLs to connect to your instance:
*
*
{% endhint %}
# Jira ServiceNow integration
Connect Jira and Jira Service Management with ServiceNow to keep work moving between teams. The integration keeps data consistent by bridging the gap between IT teams working in ServiceNow and software development teams working in Jira. It provides a unified workspace where users can manage Jira incidents, problems, changes, and service requests within ServiceNow, and the other way around.
### Requirements to Build Your Integration:
* A Jira instance with a dedicated user, and an API token for that user.
* A ServiceNow instance with a dedicated user. For testing purposes, you can create a developer instance here:[ServiceNow Developers](https://developer.servicenow.com/dev.do)
{% hint style="info" %}
For a detailed guide on how to create a ServiceNow user, please visit the following link: [How to create a ServiceNow user.](https://docs.getint.io/guides/integration-synchronization/jira-servicenow-integration/creating-a-servicenow-user-for-getint-integration)
{% endhint %}
* For Jira **Cloud customers,** download the corresponding app from the Atlassian Marketplace, and launch it. Please note that we support both Jira Software and Jira Service Management.
* For Jira **Data Center,** please click your profile icon at the top right corner of your Jira instance, click **Atlassian Marketplace,** and use the option **Find new apps** to search for our **Jira ServiceNow integration app by Getint** (similar to the apps found below).
### Setting up your ServiceNow Integration
#### 1. Accessing Getint:
* Launch the app, and click **Create integration** or **Migration.**
#### 2. Token Generation for Jira Cloud:
* For **Jira Cloud,** generate a Jira token. This token will act as your password.
* Go to **Atlassian Account Settings.**
* Navigate to **Security** and generate an API token, then use this token as the password for Jira integration.
#### 3. Establishing a Connection with Jira:
* Ensure you’re logged in as a user with admin rights, click on **Connect App,** and select Jira. Choose **Create New** to set up a fresh connection with your Jira instance and input the URL of your Jira instance.
* After establishing the connection, select the **Jira project** you want to connect to from the dropdown menu.
#### 4. Establishing a Connection with ServiceNow:
* Connect to **ServiceNow.** If no connection is established yet, create a new one.
You can find your credentials within the settings in your ServiceNow instance.
{% hint style="info" %}
It is crucial to grant specific access permissions to your ServiceNow user; otherwise, the connection will fail. You can find the full list of required permissions [here.](https://docs.getint.io/guides/integration-synchronization/jira-servicenow-integration/creating-a-servicenow-user-for-getint-integration)
{% endhint %}
#### 5. Type Mapping:
* **Quick Build (Beta)**: You can use the Quick Build feature to automatically map fields and types between your apps. It’s a convenient way to make the process easier.
* **Manual Mapping**: If you prefer more control, you can manually map the types yourself. This allows you to customize the mapping based on your specific requirements.
* **Mapping ServiceNow Projects**: Projects in ServiceNow are part of the [Strategic Portfolio Management](https://www.servicenow.com/docs/bundle/vancouver-it-business-management/page/product/project-management/concept/c_ProjectApplicationOverview.html) (SPM) module. This module must be installed so that project mappings appear as an option in the dropdown list when pairing your type mappings. You can find more information about this module [here.](https://www.servicenow.com/docs/bundle/vancouver-it-business-management/page/product/project-management/concept/c_ProjectApplicationOverview.html)
Project mapping in Jira ServiceNow integration
* After enabling this module, you can start syncing ServiceNow projects from your **Project workspace.**
* These will sync just like any other ServiceNow table, such as incidents, change requests, and more. Consequently, any new project from ServiceNow can be seamlessly transferred as a new task in Jira.
#### 6. Field Mapping:
* Review or manually map which fields to integrate and sync within the mapped types, including title, description, assignees, custom fields, and more.
Example of automatic field mappings with Quick Build where you can also add fields manually while using Quick Build.
#### 7. Assignees:
* Map **Assignees** according to your user pairing requirements.
Assignees in Jira (left). Assigned to in ServiceNow (right)
#### 8. How to Manage Comments & Attachments:
* Check the **Comments & Attachments** tab. These are activated by default, but you’re free to modify them depending on your organization’s needs.
* For ServiceNow integrations, there’s an option to further customize how comments are created under **Customize comments creation.** It can be incredibly helpful to make specific comments that either go Public or Private or **be skipped completely.**
* You can also choose the sync direction for attachments: **both ways**, **only to App A (left)**, or **only to App B (right)**. This feature adds an extra layer of customization to meet your organizational needs.
{% hint style="info" %}
You can disable comments and attachments entirely if they are not needed or are restricted in your organization.
{% endhint %}
#### 9. How to Map Statuses:
* Map **Statuses.** Ensure you’re using the correct fields that represent the statuses for each app.
#### 10. Finishing Your Integration
* Name your project and click **Create** at the top right corner to finish the integration setup.
#### 11. UI Filtering
* After finalizing your integration, you may also add filters to each app. Select the filter icon adjacent to the app icon within your integration. This action will affect the corresponding side of the integration.
* **Define Filter Rules**:
* **ALL items filters**: Rules will be verified for every item before synchronization.
* **NEW items filters**: Rules will be verified only for newly created items that have not yet been synced.
* **SYNCED items filters**: Rules will be verified for items that were already synced in the past.
For more information about this feature, please visit Items Filtering.
* You can also use custom queries to synchronize tickets only when the Assignment Group is set to a specific value. For example:
A custom query to sync ServiceNow tickets by the Assignment Group ID
#### 12. Case Scenario for Items Filtering:
* For example, If you want to integrate **Jira Project A** with ServiceNow Incidents that belong to **Assignment Group A**, use the filter items feature. In Getint, you can configure the connection by mapping the types and fields between ServiceNow and Jira, ensuring that fields like **Assignee** and **Assignment Group** are correctly synchronized.
* On a separate integration, you can set up (or duplicate the existing integration) to integrate **Jira Project B** with ServiceNow Incidents that belong to **Assignment Group B.** Here, different filtering will be needed. You can define filter rules in Getint to control which items are synchronized, specifying criteria such as status or priority to ensure only relevant items are synced. This helps manage data efficiently and avoids unnecessary clutter. Remember to save the integration once the filters are applied to ensure they are active.
Filtering items by Assignment Group
#### 13. Test your Integration:
* Ensure you aren’t experiencing any errors and that your integration is running smoothly. Create test scenarios to validate the functionality of your setup.
ServiceNow ticket created for testing purposes
A new Jira ticket was created on the other end as a result of the integration
### Conclusion
By following these steps, you can easily integrate Jira with ServiceNow, ensuring efficient synchronization of tasks, issues, and workflows across both platforms. This configuration promotes collaboration and streamlines project management processes. Please contact our [Support Team](https://getint.io/help-center) or [Schedule a Demo](https://calendly.com/d/cpws-jb2-8xx/demo-call-all-team), if you require further assistance.
# Creating a ServiceNow User for Getint Integration
In general scenarios, Admin access is not provided to a ServiceNow instance. The best practice/recommendation is to create a dedicated user (with several different access controls) to connect a ServiceNow instance to Getint and sync the data.
### How to Create a ServiceNow User
#### **1. User Creation:**
* Log in to ServiceNow, click **All** at the top left corner, and navigate to the **Users** (under User Administration) section.
* Click on **New** to create a new user, and enter all relevant user details.
* Enter the User details, and click **Submit** to create the user.
{% hint style="warning" %}
Ensure that you untick **Password needs reset** when creating a new user. If you skip this step, the system will block the connection and display an error stating that you lack sufficient permissions. This message is misleading, as the issue isn’t related to permissions, but simply that the password is set to reset.
{% endhint %}
* After creating the user, you can now generate a password. Do so by clicking **Set Password** in the right corner of the screen. Save the password, and now you can use the full credentials to create a connection with Getint.
#### **2. Create a Role:**
* Navigate to **System Security** > **Users and Groups** > **Roles.**
* Click on **New** and enter relevant details for the new role.
* Click **Submit** to create the role.
#### **3. Elevate System Admin to Security Admin:**
* Click on your profile image and select **Elevate Role.** In the pop-up, choose **security\_admin** and click **Update.** This step elevates the **System Admin** to **Security Admin** and will allow you to modify the **ACL** settings.
#### 4. Tables Access & ACLs Needed:
As we are tailoring access for our users, some base ACLs are required so that the connection with the ServiceNow instance works properly, allowing users to create, edit, and read their fields.
Here is a list of the tables for which ACLs must be created for the integration user role(s), along with the purpose each table serves within this process:
* **Dictionary Entry \[sys\_dictionary]**\
This is the ServiceNow Data Dictionary, which defines the structure and attributes of every field on every table.\
The Getint user needs read access to this table to introspect the schema of the records being synchronized. By reading this table, Getint identifies a field's type (e.g., reference, string) and its properties (e.g., maximum length, required status). This information is crucial for accurately translating and mapping data types between ServiceNow and other software.
* **Field Class \[sys\_glide*****\_*****object]**\
This table stores definitions for the fundamental data types (e.g., string, integer, reference) used by fields across the instance.
The dedicated user requires read access to this table because it is closely related to sys\_dictionary. It provides the low-level, technical classification of the field types. This access helps Getint's logic correctly interpret and handle the data being pulled or pushed, ensuring that all synchronized fields adhere to their native ServiceNow data constraints.
* **Choice \[sys\_choice]**\
This table contains all the predefined drop-down options (choices) for choice fields in the system, such as Incident State or Priority values.
The Getint user must have read access to retrieve both the internal value (the numerical/system value) and the display label (the user-friendly name) for these choices. This is essential for the core integration function of status and value mapping, ensuring that a status correctly corresponds to the appropriate, valid choice value in ServiceNow.
* **Journal Entry \[sys\_journal\_field]**\
This table is where Journal-type field entries are stored, specifically, records like Additional comments and Work notes from synchronized tickets.
The dedicated user requires read and create/write access to this table to manage bi-directional communication. This access allows Getint to extract comments from a ServiceNow record to sync to the integrated software, and conversely, to write comments back into the correct ServiceNow journal field, maintaining a full communication history.
#### 5. Granting User Access: Create Permission Records in ServiceNow
* Go to **System Security** > **Access Control (ACL).** Now, in the **ACL**, create **six new records** as follows:
**Record 1:**
* Click **New** to create a new record.
* Select **Read** from the **Operation** dropdown.
* In the **Name** field, select **Dictionary Entry \[sys\_dictionary]** in the first dropdown and **\*** in the second dropdown.
* Provide a **Description.**
* In the **Requires Role** section, add the role created in **Step 2** above.
* Click **Submit** at the top right corner, and **Continue** to create the new ACL record.
**Record 2:**
* Repeat the steps as **Record 1,** but this time select **None** in the second dropdown instead of the **\* (asterisk).**
**Record 3:**
* Repeat the previous steps, but in the **Name** field, choose **Field class \[sys\_glide*****\_*****object]** in the first dropdown and **\*** in the second dropdown.
**Record 4:**
* Repeat the previous steps, but in the **Name** field, choose **Choice \[sys\_choice]** in the first dropdown and **\*** in the second dropdown.
**Record 5:**
* Repeat the previous steps, but in the **Name** field, choose **Field class \[sys\_glide*****\_*****object]** in the first dropdown and **None** in the second dropdown.
**Record 6:**
* Repeat the previous steps, but in the **Name** field, choose **Journal Entry \[sys\_journal\_field]** and **None** in the second dropdown.
{% hint style="warning" %}
Do not forget to add the **getint role** in the **Requires role** section for all six records.
{% endhint %}
#### **6. Configure User Permissions:**
* Go to **Users Administration** > **Users.**
* Search for the user created in **Step 1.**
* Click on the user ID and navigate to the **Entitled Custom Tables** section.
* In the **Roles** tab, click **Edit.**
* In the **Collections** section:
* Search for **itil** and move it to the **Roles list.**
* Also, search for the role created in **Step 2** and add it to the **Roles list.**
* Click **Save** and then **Update** to finalize the changes for the user.
With these steps, all permissions are now configured for this ServiceNow user, allowing to establish a connection between Getint and ServiceNow.
# Creating a Custom Field in ServiceNow
Creating custom fields in ServiceNow enables better data organization and adapts the platform to meet specific business requirements. This opens a new way to map data fields across various platforms, ensuring seamless data flow and synchronization.
### How to Create Custom Fields in ServiceNow
Here’s a step-by-step guide to creating custom fields in ServiceNow:
#### 1. Select the Appropriate Table:
* Choose the table where the new custom field will be created. ServiceNow organizes its data in tables, such as Incidents, Change, or Task, and each table can have customized fields.
#### 2. Access the Form Layout to Create a Custom Field:
* Click the three horizontal bars (as shown below) and select **Configure > Form Layout**.
* In the **Create new field** section, provide the necessary details:
* **Name**: Enter the name of the field.
* **Type**: Select the field type.
* **Field Length**: Specify the length of the field.
* **View Name**: Choose the view for displaying the field (Default view is recommended).
* **Section**: Determine which section the field will be displayed in.
* Click **Add** to create the field.
{% hint style="warning" %}
As of the publication date of this article, Getint supports the following field types: Date, Dropdown, Text, Reference, and URL.
{% endhint %}
#### 3. Place the Field
* Use the ServiceNow **slushbucket** (the term slushbucket refers to a user interface component used to transfer items between two lists) to place the new field in the desired position on the form.
Think of it as a method for sorting and organizing data within forms and catalog items
* Click **Save** to finalize your changes.
#### 4. Test Your Custom Field
* Ensure the new field appears correctly on the form and functions as intended.
* It is important to also test the field in your ServiceNow integration to validate it is working as expected. The new field should be available from the dropdown list of field mapping.
The newly created custom field appears when searching for ServiceNow fields
When integrating ServiceNow with other tools using Getint, mapping custom fields is essential to maintain consistent data synchronization. Getint facilitates field mapping by allowing users to connect different platforms' fields, which may vary in naming conventions and types. If fields unique to ServiceNow (like Assignment Group) need to be mapped to other platforms, creating corresponding custom fields in those platforms can ensure a smooth integration experience.
These steps help customize the ServiceNow environment to fit specific use cases, enhance data management, and improve workflow automation. For more information about our tool or if need assistance with your integration, please contact our [Help Center](https://getint.io/help-center).
# How to Restrict Access to Specific Tables for Integration
### Use Case:
If you want to restrict full access to specific tables in ServiceNow for certain companies during integration, you can do this by adding Business Rules. This allows you to specify which tables you don't want to provide access to.
For example, if you only want to integrate **Incidents** and not **Change Requests**, you can restrict access to the **ChangeRequest** table.
**Scenario:**
Integrating **ChangeRequest** (ServiceNow) ↔︎ **Story** (Jira)
Sample integration ChangeRequest (ServiceNow) ↔︎ Story (Jira)
If you restrict access to the **ChangeRequest** table, attempting to create a Story in Jira will result in an error when trying to create a ChangeRequest in ServiceNow. This error will appear in the Getint integration logs.
### How to Deny Access to the ChangeRequest Table
* Go to **Administration > Business Rule**.
* Follow the steps shown in the images below to create a new Business Rule.
* Configure the fields as shown.
Create a new Business Rule
Everything should be set as in the picture above
Go to the Advanced tab and paste the script shown below
* In the **Advanced** tab, paste the following script to block access to the **ChangeRequest** table:
```
(function executeRule(current, previous) {
// Bypass restriction for admin users
if (gs.hasRole('admin')) {
return; // Allow admins to proceed
}
// Abort any operation on the change_request table
current.setAbortAction(true); // Prevent any operation from completing
// Apply a query that results in no records being returned
current.addQuery('number', "00000000000"); // An invalid query to ensure no records are returned
})(current, previous);
```
This script will prevent any operation (Insert, Update, Query, or Delete) from happening on the **ChangeRequest** table by aborting the action and returning no records.
### How to Restrict Access to Other Tables
To restrict access to other tables, simply repeat the steps described above for the **ChangeRequest** table.
The only change required is to select a different table in the **Table** field. You can restrict access to various tables such as:
* **Requested Item**
* **Incident**
* **Incident Task**
* **Problem**
* Other tables like **sys\_dictionary** or **journal\_field\_type** which we may have allowed access to in previous ACLs.
### Summary
By following this approach, you can ensure that companies only access the tables necessary for their integration and block unwanted access to other tables.
If you need any further help or if you are experiencing issues with your installation, feel free to open a support ticket at our [Support Portal.](https://getint.io/help-center)
# How to Restrict "Incident" Data to Specific 3rd Party Companies
### Who is this tutorial for?
This tutorial is for users integrating multiple 3rd parties (e.g., multiple companies using Jira) with ServiceNow, and you want to ensure that each company only sees their relevant data.
### Use Case
The examples here are based on the **Incident** type in ServiceNow. However, you can apply the same logic to other types like Change Request, Requested Item, Incident Task, etc.
If your ServiceNow instance is integrated with multiple 3rd party companies using Jira, this setup ensures that each company only sees the data associated with their **Assignment Group** in the Getint integration.
{% hint style="info" %}
**Important**: When creating an Incident in ServiceNow, always specify the **Assignment Group** field.
{% endhint %}
### How does it work?
Example integration Incident ↔︎ Bug
* **Incident 1** created in ServiceNow with **Assignment Group: company1** will result in Getint creating a Bug in **company1's Jira**.
* **Incident 2** created in ServiceNow with **Assignment Group: company2** will result in Getint creating a Bug in **company2's Jira**.
* **Incident 3** created in ServiceNow **without an Assignment Group** will not create any Bug in Jira, even if the integration is enabled.
When a **Bug is created in Jira** by company1 or company2:
* Getint automatically creates a corresponding Incident in ServiceNow with the appropriate **Assignment Group** matching the company (e.g., company1 or company2).
#### Quick Steps
* **Create an Assignment Group** in ServiceNow (e.g., **company1**).
* **Create a user** with the username **company1** and assign the roles: **getint**, **sn\_incident\_read**, **sn\_incident\_write**.
* **Add Business Rules** for incidents (and other relevant types) to restrict access (Insert, Update, Read) based on the Assignment Group and username.
* **Add Business Rules** to ensure that each company only uses its own Assignment Group.
#### Step 1: Create an Assignment Group in ServiceNow
To ensure that each company only has access to its own Incidents and data, first create an **Assignment Group** in ServiceNow.
* Go to **User Administration > Groups**.
* Create a new Assignment Group.
Create a new Assignment Group
* Name the group (e.g., **company1**).
Create an Assignment Group with name company1
#### Step 2: Create a ServiceNow User for Each Company
For tutorial purposes, the **Assignment Group name** should match the **username** for the integration user. Of course, it is possible to use any assignment group but, in such case, scripts defined below will have to be adjusted.
* Go to **User Administration > Users** and create a new user (e.g., **company1**).
* Set the **User ID** to **company1**.
* Set the password for the user.
* Assign the roles: **getint**, **sn\_incident\_read**, **sn\_incident\_write**. If the **getint** role doesn’t exist, create it as described earlier.
Create new user
{% hint style="info" %}
**Important note:**
[In this tutorial, ](https://docs.getint.io/guides/integration-synchronization/jira-servicenow-integration/creating-a-servicenow-user-for-getint-integration)we created the **getint\_integration** user (and it applies for most cases where you have a single ServiceNow and single Jira to integrate), but we need to create another user (for each company) and assign roles: **getint**, **sn\_incident\_read**, **sn\_incident\_write**)
{% endhint %}
User ID is the most important (company1)
After creating a user. Edit the user password.
Generate and then copy the password
Uncheck and click Update.
Assign Roles to the user
Assign getint, sn_incident_read, sn_incident_write. If you don't see role getint then create it as described here.
#### Step 3: Add a Business Rule to Restrict Access to Incidents by Assignment Group and Username
You need to create Business Rules to ensure that data visibility is restricted by **Assignment Group** and **username**.
**Requirements:**
* The Assignment Group (e.g., **company1**) is created.
* The user with the matching username (e.g., **company1**) and with the roles assigned: (**getint**, **sn\_incident\_read**, **sn\_incident\_write**
{% hint style="info" %}
**Important:** The username and Assignment Group must be identical (case-sensitive).
{% endhint %}
**Steps:**
* Go to **Administration > Business Rule**.
* And follow the steps shown in the pictures below:
Create a new Business Rule
Everything should be set as in the picture above
Go to Advanced tab and paste script shown below.
* Create a new Business Rule with the following script:
```
(function executeRule(current, previous) {
var userName = gs.getUserName(); // Get the current user's username
// Bypass restriction for admin users
if (gs.hasRole('admin')) {
gs.info("Admin user, bypassing group restriction.");
return; // Allow admins to proceed
}
// Handle querying incidents where assignment group matches the username
if (!current.isNewRecord()) { // Only add this condition for non-insert actions
current.addQuery('assignment_group.name', userName); // Compare assignment group's name with the username
gs.info("Querying incidents where assignment group matches username: " + userName);
}
// Handle inserts - set the assignment group based on the username
if (current.isNewRecord()) { // If this is an insert operation
var userGr = new GlideRecord('sys_user_group');
userGr.addQuery('name', userName); // Find the group by username
userGr.query();
if (userGr.next()) {
current.assignment_group = userGr.sys_id; // Set the assignment group to the group found
gs.info("Set assignment group to: " + userGr.name + " for user: " + userName);
} else {
gs.error("No matching assignment group found for username: " + userName);
}
}
// Handle updates - restrict changes if assignment_group doesn't match the username
if (!current.isNewRecord() && current.assignment_group.changes()) { // If it's an update and assignment_group has changed
var newAssignmentGroup = current.assignment_group.getDisplayValue().toLowerCase();
// Check if the new assignment group matches the current user's group
if (newAssignmentGroup !== userName.toLowerCase()) {
gs.addErrorMessage("You cannot change the assignment group to one that does not match your username.");
gs.error("Update blocked: Attempt to change assignment group to: " + newAssignmentGroup + " by user: " + userName);
current.setAbortAction(true); // Prevent the update from completing
}
}
})(current, previous);
```
This script ensures that users only see Incidents assigned to their group, and it sets the **Assignment Group** automatically for new records.
#### Step 4: (Optional) Add Business Rule to Hide Other Assignment Groups
This step is **optional** and only serves to hide other Assignment Groups, ensuring that 3rd parties will only see their own Assignment Group (which matches their username) in the integration configuration.
{% hint style="info" %}
**Important**: Even if a 3rd party company attempts to use an Assignment Group other than their own, Getint will ignore it and still enforce the use of the username as the Assignment Group.
{% endhint %}
**Purpose:**
This Business Rule ensures that each company only sees its own Assignment Group and hides others. This is useful for preventing 3rd parties from seeing Assignment Groups that do not belong to them.
**Steps:**
* Go to **Administration > Business Rule**.
* Create a new Business Rule following the steps shown in the images below.
* Set the fields as shown in the image.
You can also hide all groups and leave group created specifically for 3rd party (ex. “company1”)
Everything should be set as in the picture above
Go to Advanced tab and paste script shown below
* Script: In the Advanced tab, paste the following script to restrict the visibility of Assignment Groups based on the current user's username:
```
(function executeRule(current, previous /*null when async*/) {
// Get the current user's username
var userName = gs.getUserName();
// Bypass restriction for admin users
if (gs.hasRole('admin')) {
gs.info("Admin user, bypassing group restriction.");
return; // Allow admins to proceed
}
// Get the group name of the current group being queried or interacted with
var groupName = current.name.getDisplayValue();
// Log values for debugging (optional)
gs.info("User: " + userName + " | Group: " + groupName);
// Restrict the query to return only groups where the group name matches the username
current.addQuery('name', userName);
})(current, previous);
```
This rule ensures that only the group matching the username will be visible to each company during the integration process.
Example for user "allegro." Only one Assignment Group is visible because username is allegro.
#### Step 5: Add Business Rule to Restrict Access to Comments from Incidents
**Steps:**
* Go to **Administration > Business Rule**.
* And follow steps shown on the pictures below:
Make sure to select sys_journal_field table
Go to Advanced tab and paste script shown below
* Create a new Business Rule with the following script
```
(function executeRule(current, previous /*null when async*/) {
var username = gs.getUserName();
// Filter records where the 'name' field is 'incident'
current.addQuery('sys_class_name', 'incident'); // Ensure we are working with incidents only
// Create a new GlideRecord for incidents
var gr = new GlideRecord('incident');
gr.addQuery('sys_class_name', 'incident'); // Ensure we are filtering incidents
gr.query();
var incidentSysIds = [];
while (gr.next()) {
var assignmentGroupId = gr.getValue('assignment_group'); // Get the sys_id of the assignment group
var groupRecord = new GlideRecord('sys_user_group');
if (groupRecord.get(assignmentGroupId)) { // Fetch group record
var groupName = groupRecord.getValue('name'); // Get the group name
if (groupName === username) {
incidentSysIds.push(gr.getValue('sys_id')); // Add the incident's sys_id if it matches
}
}
}
// Now add the query to 'current' to return only the incidents with the collected sys_ids
if (incidentSysIds.length > 0) {
current.addQuery('element_id', 'IN', incidentSysIds); // Filter current to only include these sys_ids
} else {
current.addQuery('element_id', 'IN', ['-1']); // No matching incidents, return an empty set
}
})(current, previous);
```
#### Step 6: Add Two Business Rules to Restrict Access to Attachments from Incidents
**Steps:**
* Go to **Administration > Business Rule**.
* And follow steps shown on the pictures below:
In the first step you will restrict access to the **sys\_attachment** table, and in the second step you will restrict access to the **sys\_attachment\_doc** table (which holds the data for each attachment).
* Restrict access to **sys\_attachment** table
Make sure to select sys_attachment table
Go to Advanced tab and paste script shown below:
* Create a new Business Rule with the following script
```
(function executeRule(current, previous /*null when async*/) {
var username = gs.getUserName();
// Filter attachments that are linked to incidents
current.addQuery('table_name', 'incident'); // Filter only attachments related to incidents
// Create a new GlideRecord to query incidents
var gr = new GlideRecord('incident');
gr.addQuery('sys_class_name', 'incident'); // Ensure we are filtering incidents
gr.query();
var incidentSysIds = [];
while (gr.next()) {
var assignmentGroupId = gr.getValue('assignment_group'); // Get the sys_id of the assignment group
var groupRecord = new GlideRecord('sys_user_group');
if (groupRecord.get(assignmentGroupId)) { // Fetch group record
var groupName = groupRecord.getValue('name'); // Get the group name
if (groupName === username) { // Compare assignment group with the username
incidentSysIds.push(gr.getValue('sys_id')); // Add the incident's sys_id if it matches
}
}
}
// Now add the query to 'current' to return only the attachments linked to the incidents with the matching assignment group
if (incidentSysIds.length > 0) {
gs.error("Matching incident sys_ids: " + incidentSysIds.join(", "));
current.addQuery('table_sys_id', 'IN', incidentSysIds); // Filter current to only include attachments linked to these incidents
} else {
gs.error("No matching incidents found for user: " + username);
current.addQuery('table_sys_id', 'IN', ['-1']); // No matching incidents, return an empty set
}
})(current, previous);
```
* Restrict access to **sys\_attachment\_doc** table
**Steps:**
* Go to **Administration > Business Rule**.
* And follow steps shown on the pictures below:
Make sure to select sys_attachment_doc table
Go to Advanced tab and paste script shown below:
* Create a new Business Rule with the following script
*
```
(function executeRule(current, previous /*null when async*/) {
var username = gs.getUserName();
// Create a new GlideRecord for attachments related to incidents
var attachmentGR = new GlideRecord('sys_attachment');
attachmentGR.addQuery('table_name', 'incident'); // Filter for attachments related to incidents
attachmentGR.query();
var attachmentSysIds = [];
while (attachmentGR.next()) {
var incidentId = attachmentGR.getValue('table_sys_id'); // Get the sys_id of the related incident
// Query the incident to get the assignment group
var incidentGR = new GlideRecord('incident');
if (incidentGR.get(incidentId)) {
var assignmentGroupId = incidentGR.getValue('assignment_group'); // Get assignment group id
var groupRecord = new GlideRecord('sys_user_group');
if (groupRecord.get(assignmentGroupId)) { // Fetch group record
var groupName = groupRecord.getValue('name'); // Get the group name
if (groupName === username) {
attachmentSysIds.push(attachmentGR.getValue('sys_id')); // Add the attachment sys_id if it matches
}
}
}
}
// Now add the query to 'current' to return only the documents linked to the attachments with the collected sys_ids
if (attachmentSysIds.length > 0) {
gs.error("Matching attachment sys_ids for user: " + username + " - " + attachmentSysIds.join(", "));
current.addQuery('sys_attachment', 'IN', attachmentSysIds); // Filter current to only include attachment docs linked to these attachments
} else {
gs.error("No matching attachments found for user: " + username);
current.addQuery('sys_attachment', 'IN', ['-1']); // No matching attachments, return an empty set
}
})(current, previous);
```
### Summary
We have now restricted data access for each company to the Incidents associated with their Assignment Group. You can apply similar logic to other tables, such as Change Request, to restrict full access.
If you need any further help or if you are experiencing issues with your integration, feel free to open a support ticket at our [Support Portal.](https://getint.io/help-center)
# Integrating Multiple Jira Projects into a Single ServiceNow Instance
With our **many‑to‑one** feature, users can integrate multiple Jira projects into a single ServiceNow instance. Because of ServiceNow’s specific architecture, certain configurations need to be handled differently, including **item routing**.
This guide explains how to connect several Jira projects to a single ServiceNow instance and define the rules that determine which Jira project receives each ServiceNow work item, whether that is Project A, B, C, or any other.
**Tick Sync many projects before you build the integration**: If you do not tick **Sync many projects** on the Jira side while setting up the connection, the integration stays locked to the single Jira project you selected. The option cannot be enabled later, so adding a second project means building a new integration from scratch.
The reverse does work. An integration created with **Sync many projects** enabled can be reduced back to a single Jira project, although the interface continues to display the many projects layout and Item Routing has to be updated to match the new selection.
{% hint style="warning" %}
**ServiceNow Integrations:**
When configuring many-to-many sync with ServiceNow, **Sync many projects** will only be available on the source app side (i.e., Jira).
Getint connects to the entire **ServiceNow instance** (not individual projects), so configure **Item Routing** in the source app to route tickets from ServiceNow.
{% endhint %}
### Creating a One-to-Many Integration
1. To synchronize multiple projects, begin by creating an integration as you normally would. Next, choose Jira as the connector on the left side.
2. Next, either select an existing connection or create a new one. After the connection is set, you’ll see a checkbox labeled **Sync many projects** above the dropdown list.
3. Select the projects you want to sync, then click **Connect**.
{% hint style="info" %}
An **X** appears next to each project name. Click it to remove a project from the selection if you chose the wrong one.
{% endhint %}
4. Select ServiceNow as the counterpart application, then either create a new connection or select an existing one.
{% hint style="warning" %}
Unlike many-to-many project syncing, Jira-ServiceNow integrations only require selecting many projects from the Jira side. ServiceNow lacks individual projects, so we connect to the **entire instance** (not specific boards).
{% endhint %}
5. Click **Start with Mapping Types** to map the work item types.
6. After mapping issue types, you can start adding fields to them. At the time we’re publishing this article, the **Quick Build** feature is not available for many-to-many projects. You will need to map fields manually.
#### Defining Conditions in Items Routing
The next step is to define conditions, as routing refers to the path a work item takes across connected systems. By setting clear rules, you ensure Getint knows which project each incoming work item belongs to and what type it should have.
Since ServiceNow is treated as a single instance rather than a workspace with multiple projects, you configure routing for items syncing from ServiceNow to Jira, meaning the criteria fields are from the ServiceNow work items.
Please follow the next steps to set up the rules for syncing your items, and then review the subsequent configuration steps to confirm that transitions, field mappings, and workflows are properly aligned.
{% hint style="warning" %}
When populating the operator field values as criteria for the items syncing from ServiceNow, use the Sys ID of the ServiceNow field values instead of the text values. This process will be broken down below.
{% endhint %}
1. Select the project where the item coming from ServiceNow will be routed to, and specify which issue type it should sync as.
2. To collect the Sys ID of the field values, you just have to right-click the value (while on the work items list view) and click **Copy sys\_id**. Paste the copied value, with CTRL/Command + V or right-click > paste, on the operator value afterwards.
\
3\. Choose the field that will trigger the sync. For example, click **+Add New Field** to add conditions across multiple fields. If all conditions are met, the item will sync to the project you are routing it to.
4. Click **Apply** to submit the changes, then save the integration. After that, test the integration to confirm that routing works correctly and items are syncing as expected.
#### Removing or Adding Projects to Existing Integrations
You may need to adjust the projects connected to an integration. This can involve adding new projects to expand its scope or removing existing ones to simplify or restructure it. Follow the steps below to make these changes:
* Click the box for the Jira app. In this example, it is on the left side of the integration.
* Use the dropdown list to browse your projects and add new ones. You can also remove projects from the integration by clicking the **X** icon next to the project name. This works the same way as when you added or removed projects during the initial setup.
* Close the tab and save the integration to submit your changes.
{% hint style="warning" %}
You need to define new conditions to route work items to any new project you’ve added.
{% endhint %}
#### **Switching Between Single Project and Many Projects Syncs**
The **Sync many projects** option can only be enabled while you are setting up the Jira connection. Moving between the two modes works in one direction only.
**Single project to many projects is not possible**: An integration built without **Sync many projects** stays tied to the Jira project selected during setup, and the checkbox is no longer available once the integration exists. To cover additional Jira projects, create a new integration with the option ticked, then rebuild the type mappings, field mappings, and routing conditions. After testing the replacement, disable or delete the original integration.
**Many projects to single project does work**: Follow the steps in the previous section and remove Jira projects until one remains. Two points to keep in mind:
* The interface still looks like a many-project sync. The checkbox stays ticked, and the project field continues to behave as a multi-project selector, even though only one Jira project is selected.
* Item Routing has to be updated to reflect the change. Conditions that pointed to the removed projects no longer resolve, so review the rules and adjust them so that every ServiceNow work item routes to the remaining Jira project.
Because the restriction only applies in one direction, tick **Sync many projects** during setup whenever there is a chance that more Jira projects will join the sync later, even if you start with a single project.
{% hint style="warning" %}
Work items will not sync while Item Routing still references a Jira project that has been removed from the integration. Update the conditions before saving.
{% endhint %}
### Conclusion
As ServiceNow is more complex than most IT management software, there are a few considerations to take into account when connecting it to multiple Jira spaces.\
Tweak your integration until the data is syncing as expected, observe the receiving end of the synchronization to ensure that work items are being created under the configured type, keep in mind that the operator values are based on the Sys ID of the ServiceNow field values, and let the integration take care of the synchronization once everything is up and running.
Need more help? Visit our [Help Center](https://getint.io/help-center) or reach out to support by clicking the chat bubble for direct assistance.
# REST API requests list
Below, you can find a list of endpoints that will call during integration configuration and data synchronization.
### During integration configuration
[/api/now/table/sys\_db\_object?sysparm\_query=sys\_name%3DTask](https://dev57744.service-now.com/api/now/table/sys_db_object?sysparm_query=sys_name%3DTask) - finding task table details.
[/api/now/table/sys\_db\_object?sysparm\_query=super\_class%3De3f033c4c923101091f9f06464832716](https://dev57744.service-now.com/api/now/table/sys_db_object?sysparm_query=super_class%3De3f033c4c923101091f9f06464832716) - finding tables extending task.
[/now/table/sys\_db\_object/fa257b04c927101091f9f06464832798](https://dev57744.service-now.com/api/now/table/sys_db_object/fa257b04c927101091f9f06464832798) - table meta data.
[/now/table/sys\_db\_object/e3f033c4c923101091f9f06464832716](https://dev57744.service-now.com/api/now/table/sys_db_object/e3f033c4c923101091f9f06464832716) - table meta data.
[/api/now/v2/table/sys\_choice?name=task\&element=assignment\_group](https://dev57744.service-now.com/api/now/v2/table/sys_choice?name=task\&element=assignment_group) - fetching e.g. groups for assignment group field.
[/api/now/v2/table/sys\_user\_group?sysparm\_fields=sys\_id,name](https://dev57744.service-now.com/api/now/v2/table/sys_user_group?sysparm_fields=sys_id,name) - fetching user groups.
[/api/now/v2/table/sys\_user?sysparm\_fields=sys\_id,name](https://dev57744.service-now.com/api/now/v2/table/sys_user?sysparm_fields=sys_id,name) - fetching users who can be assigned.
[/api/now/v2/table/sys\_choice?name=incident\&element=state](https://dev57744.service-now.com/api/now/v2/table/sys_choice?name=incident\&element=state) - fetching options for state field.
[/api/now/table/sys\_dictionary?sysparm\_query=name=incident](https://dev57744.service-now.com/api/now/table/sys_dictionary?sysparm_query=name=incident) - fetching fields from incident table.
[/api/now/table/sys\_dictionary?sysparm\_query=name=task](https://dev57744.service-now.com/api/now/table/sys_dictionary?sysparm_query=name=task) - fetching fields for task table.
### During synchronization
[/api/now/v2/table/incident?sysparm\_fields=sys\_id,sys\_updated\_on\&sysparm\_limit=50\&sysparm\_offset=0\&sysparm\_query=%5Esys\_updated\_on%3E%3D2021-03-24+14%3A15%3A03null](https://dev57744.service-now.com/api/now/v2/table/incident?sysparm_fields=sys_id,sys_updated_on\&sysparm_limit=50\&sysparm_offset=0\&sysparm_query=%5Esys_updated_on%3E%3D2021-03-24+14%3A15%3A03null) - fetching incidents.
[/api/now/v2/table/incident](https://dev57744.service-now.com/api/now/v2/table/incident) - creating incidents.
[/api/now/v2/table/incident?sysparm\_query=sys\_id%3D680e615edb83a010a1db5385ca9619e3](https://dev57744.service-now.com/api/now/v2/table/incident?sysparm_query=sys_id%3D680e615edb83a010a1db5385ca9619e3) - fetching incident by sys id.
[/api/now/v2/table/incident/680e615edb83a010a1db5385ca9619e3](https://dev57744.service-now.com/api/now/v2/table/incident/680e615edb83a010a1db5385ca9619e3) - update incident fields, write comments.
[/api/now/v2/table/sys\_journal\_field?sysparm\_limit=100\&element\_id=680e615edb83a010a1db5385ca9619e3](https://dev57744.service-now.com/api/now/v2/table/sys_journal_field?sysparm_limit=100\&element_id=680e615edb83a010a1db5385ca9619e3) - fetching comments for incident.
[/api/now/attachment](https://dev57744.service-now.com/api/now/attachment) - fetching attachments by sys id.
[/api/now/attachment/upload](https://dev57744.service-now.com/api/now/attachment/upload) - upload attachments.
At Getint, we take feedback and customer inquiries seriously. Therefore, if you experience any errors while trying to integrate your app, or if you have any custom requirements, please raise a ticket at our support channel [here.](https://getint.io/help-center)
# ServiceNow OAuth Authentication
To set up OAuth authentication, begin by creating credentials in the Application Registry. Once set up, these credentials allow you to connect a ServiceNow instance to Getint, enabling seamless data synchronization.
### Creating Application Registry for OAuth Authentication
#### 1. Find Application Registry in All tab
#### 2. Create a New Application Registry
#### 3. Click Create an OAuth API endpoint for external clients
#### 4. Fill in the Name input and Submit
#### 5. Enter the newly created Application Registry
#### 6. Click the padlock to show the Client Secret
Generated client ID and client secret can be now used during connection setup in Getint.
### **Generating Access & Refresh tokens manually via POSTMAN**
#### 1. Create POST request:
* Set **URL** to https\://**instance**.service-now\.com**/oauth\_token.do**
* Select **x-www-form-urlencoded** in the **Body** tab and add the following properties:
* **client\_id** - client\_id from Application Registry
* **client\_secret** - client\_secret from Application Registry
* **username** - ServiceNow User name
* **password** - ServiceNow User password
* **grant\_type** - must be named **password**
#### 2. You will get the following response
{% hint style="info" %}
At Getint we take feedback seriously. Our company aims to bring solutions to many different use cases. Therefore, we highly advise you to contact our [Support Team](https://getint.io/help-center) or [Schedule a Demo](https://calendly.com/d/cpws-jb2-8xx/demo-call-all-team), if you require further assistance.
{% endhint %}
# Troubleshooting Conflicting Business Rules for ServiceNow Integration
Business Rules are server-side scripts that execute during record display, insertion, deletion, or table queries. They are typically used to automate field updates based on specific conditions.
When integrating ServiceNow via Getint, Business Rules can occasionally revert or block changes before they reach the integration point. This guide provides troubleshooting methods to identify triggered Business Rules and implement effective workarounds.
### Assessing Getint logs for Sync Failure
* If the Business Rule completely blocks activity from inbound API requests, our logs will display it right away with an error message that also points out which specific Business Rule is conflicting with the integration.
We can see that there is a Business Rule in place, called Testing business rule that is blocking the creation of incidents via Getint.
* As the Sync Details screen explicitly displays which Business Rule is blocking the creation of Incidents, you can pretty much review how this Business Rule is operating on your ServiceNow instance, and work on it so it doesn’t disrupt your integration.
Filtering the Business Rules by the affected table (Incidents) and by the name gathered from the Getint logs, we found the business rule affecting the integration and can now work on it.
### Investigating Triggered Business Rules
When Getint updates ServiceNow via REST, the transaction is **non-interactive**, meaning that the changes applied to your work items/tables won’t display entries in the Script Tracer or the Debug Business Rules (Details). This is because those ServiceNow tools only register web browser transactions, so the UI debugging tools don’t capture anything.
With the above in mind, there are a few steps that you can perform to investigate which Business Rule was triggered, so you can identify it and act accordingly (update the business rule, disable it, delete it, etc).
#### 1. Verify the Active Business Rules for that Table
* In your application navigator, paste **sys\_script.list** and hit enter.
* A list of all business rules of your workspace will be displayed.
* Filter them by table name, so you can see all business rules that may have conflicted with the work item type/table in question.
* You can also configure the list layout by adding more columns to help you narrow the investigation down quicker. Adding the **Script** column, for example, will display the specific script running on that Business Rule, which may come in handy.
#### 2. Identify Suspicious Rules
* Look specifically for rules that touch assignment fields, such as assigned to, assignment group, caller, etc.
* Verify the timing (WHEN) of any suspicious business rules (If your integration sends: u\_assigned\_to = User A, a "Before Update” rule can silently change it to: User B).
#### 3. Confirming the Conflicting Business Rule
* Adding the **Set field value** column might also help you narrow down the search. It will display the field update logic, so if a Business Rule is updating a field to a specific value, you will be able to see it.
* We can then see if the listed Business Rule updates any field values of the records from that table, and if they do, what the value would be.
* Upon verifying that the Business Rule in specific, we could see that it should trigger **Before** an Incident is updated (based on a request to update the record). The criteria for the Business Rule to trigger is: If State is **In Progress**, then the **Short Description** field should be updated to a specific String text.
* Additionally, check for the **Advanced** tab (in case it's enabled) to ensure no other scripts are running along with this Business Rule.
* You can then patch your Business Rule, so it stops conflicting with **REST API** updates coming from Getint.
If you need any further help or if you are experiencing issues with your installation, feel free to open a support ticket at our [Support Portal.](https://getint.io/help-center)
# Troubleshooting ServiceNow Access and Synchronization Issues
### Use Case
When integrating with ServiceNow, you may choose to restrict your dedicated user’s access to specific tables to enforce boundaries. However, overly strict limitations can lead to insufficient permissions, preventing Getint from retrieving data correctly and disrupting synchronization.
Out-of-the-box (OOB) modules installed via the Application Manager may require specific ACLs to be assigned to the dedicated user's role to access necessary tables and ensure proper syncing.
This guide walks you through how to grant the required permissions or troubleshoot common access issues that may appear during setup.
### Assign OOB Roles for Easier Setup
Base OOB roles can be assigned to your dedicated user to grant read, write, and create access to the **Incident**, **Problem**, and **Change** tables.
If you’re encountering access errors when syncing these work items and prefer not to assign the more extensive **ITIL** role, consider using OOB roles customized to your needs.
#### Understanding Roles in ServiceNow
Roles in ServiceNow can inherit other roles, which helps with permission management. You can view these associations by navigating to:
**System Security** > **Users and Groups** > **Roles**
Locate a specific role and click to see inherited roles in the **Contains Roles** tab.
Additionally, roles can include specific ACLs to grant change permissions and access to various tables.
### Role Access Breakdown
#### Incident
* **sn\_incident\_read** Grants read access to Incident records.
* **sn\_incident\_write** Enables creation and editing of Incident records.
sn_incident_read role
sn_incident_write role
#### Change
* **sn\_change\_read** Provides read access to Change records.
* **sn\_change\_write** Allows creation and modification of Change records.
sn_change_read role
sn_change_write role
#### Problem
* **sn\_problem\_read** Enables reading of Problem records.
* **sn\_problem\_write** Supports creating and editing of Problem records.
Each role displays inherited permissions in the **Contains Roles** tab at the bottom.
sn_problem_read role
sn_problem_write role
### Removing Unwanted ACLs from OOB Roles
If you're concerned about assigning OOB roles that may include excessive permissions, you can query ACLs and trim them to fit your integration scope.
#### Steps to Query ACLs
1. In the **Application Navigator**, type `sys_security_acl_role_list.do` and press **Enter**.
2. It will lead you to a page that lists all ACLs within your ServiceNow workspace. You can then filter the ACLs by role.
3. Running the filter with conditions **ROLE - IS - \[yourRoleName]** will output all ACLs associated with the specified role. You can then customize all ACLs assigned to the specified role (you can also add tags to each ACL, so you can track their operation type, as you won’t be able to see it through this screen).
### Adding ACLs for Vendor and Scoped Applications
For integrations involving modules like **Customer Service Management (CSM)** or **Project Portfolio Management (PPM)**, dedicated users must have ACLs aligned with corresponding work item tables.
For example, syncing the **Project** work item from **PPM** requires read, write, and create ACLs for the **Project** table. Without these, syncing will fail even if mappings exist in Getint.
View of the Project Portfolio Management, through the Application Manager.
#### Example Error:
```
{"message":"Insufficient rights to query records","detail":"Field(s) present in the query do not have permission to be read"}
```
Dedicated user doesn’t have read ACL for the Project table.
After installing a vendor application, you must create ACLs corresponding to the table and work item that you’d like to synchronize. Make sure to assign the ACLs to the dedicated user’s role:
{% hint style="info" %}
In this case, we installed Project Portfolio Management. Searching for **Project** in the name dropdown of the ACL creation screen fetches the right table for the work item Project that we are looking to sync.
{% endhint %}
After assigning the **Read** ACL for the Project table to the dedicated user's role, Getint successfully retrieved items from the Project table. However, because the **Create** ACL was still missing, the integration was unable to generate new Project work items in ServiceNow.
To ensure smooth data synchronization, confirm that the dedicated user's role includes all required ACLs. These typically include **Read**, **Write**, and **Create** permissions for the relevant tables.
Ensure to add Read, Write, and Create ACLs to the dedicated user’s role for the integration to run smoothly.
#### Working with Scoped Applications
* Scoped applications like **CSM** operate in isolated environments. You cannot use the `.*` ACL operator unless you change the **global scope**. This ACL operator is required for Getint to synchronize data, and without the ACLs with this operator you might experience access issues.
.* ACL is missing from the dropdown, as we are not in the scope of the application.
* To change your current scope, click the **Application Scope** icon, and then click on the first option:
* Filter the application by name, then click it. When the application is selected, your ServiceNow tab should refresh, and the global scope will change the one selected:
You can confirm that you are within the scope of the application by hovering your mouse over the application scope icon.
* You should now be able to create ACLs of the scoped application’s tables with the .\* operator:
The .* operator for ACL can now be selected, as we are within the application’s scope.
### Debugging Field-Level ACLs
You can debug individual work item fields to uncover their ACLs, identify missing permissions, and assign only those needed for syncing. This lets you control which fields Getint can access while excluding any restricted data.
#### How to Debug Fields
1. Type **Debug Security** in the navigator, and select **Debug Security Rules** under System Security.
{% hint style="warning" %}
Avoid impersonating before opening the Debug application. Doing so will prevent access, even if the user has the **script\_debugger** role. Instead, open the Debug application first and impersonate after the debug window is active.
{% endhint %}
2. The Debug application window will appear. Impersonate the user, minimize the window, and navigate to the work item you want to debug.
Debug application window.
3. When debugging is active, a small **Bug** icon appears beside fields governed by ACL rules. Clicking it reveals the applicable ACLs and their evaluation results.
4. The fields appear greyed out, indicating the dedicated user lacks Write permissions, even though they have access to the Incidents application and table.
{% hint style="info" %}
A **True** result for a Read ACL means the dedicated user has a role with Read access to the field.
A **False** result for a Write ACL means the user lacks Write permission for the field.
{% endhint %}
5. Granting Write ACL for the Urgency field to the dedicated user’s role enables editing of that field.
Write ACL for the Incident's Urgency field has been added to the getint_integration role assigned to the dedicated user.
6. The field is no longer greyed out, and its values are now editable.
Getint can now sync the Urgency field, while leaving the data of other unwanted fields out of access.
### Fields Not Visible Due to Business Rule
When reducing the access of the dedicated user, or when limiting its ACLs/roles, you may notice some fields missing from the work item:
Fields such as Assignee and Assignment Group are missing from the view.
If the dedicated user doesn't have **ITIL** or **snc\_incident\_read** roles, trying to switch the view from Self-Service to Default to display those missing fields will always switch it back to Self-Service.\
\
This happens due to a Business Rule in place. You can add the dedicated user role to the list of roles allowed to switch the view to default with the following process:
* Type **Business Rules** in the application navigator, and select the option under **System Definition**.
* Type **incident** in the search bar, and click on the **Incident Functions** option:
* Switch to the Advanced tab, and copy this text (from the first space until the penultimate parenthesis):
* Paste the text right after the penultimate parenthesis, and change the "sn\_incident\_read“ role for the role you have created for your dedicated user (in my case, it’s getint\_integration):
* Now the dedicated user should be able to switch views to Default, without it switching back to Self-Service, allowing you to visualize the fields from the work item properly while logged in through the dedicated user (or while impersonating it):
Default View can now be selected, and the fields previously not visible are now displayed.
### Summary
Use these steps to control what Getint can access and sync from ServiceNow.
* For a straightforward setup, assign OOB roles.
* To limit permissions, query ACLs, remove excess, and customize the role.
* Vendor applications like PPM or scoped apps like CSM require targeted ACLs. Make sure to switch scopes and add `. *` ACLs as needed.
* Debug field-level permissions to ensure the user can read and write the intended fields.
If you need any further help or if you are experiencing issues with your installation, feel free to open a support ticket at our [Support Portal.](https://getint.io/help-center)
|