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.

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.

Start your integration journey. Schedule a free consultation with our Getint Integration Expert today!