IT Glue Integration: Configuration

Before You Begin

Before configuring the IT Glue integration, confirm the following are in place.

In IT Glue:

• Flexible Asset Types must already exist for each category you want to sync, such as Workstations or Servers, with the trait fields you intend to map. Trait field names are case-sensitive.
• Passwords you want surfaced in Rev.io must be attached to a Flexible Asset in IT Glue. Standalone passwords in the vault are not synced.
• An IT Glue API key with Password Access enabled. To generate one, navigate to Account > Settings > API Keys in IT Glue. Password Access is required for both password retrieval and for the integration to create records on the IT Glue side.
• Your IT Glue regional endpoint. Available endpoints are US (api.itglue.com), EU (api.eu.itglue.com), and AU (api.au.itglue.com). Using the wrong region fails silently.
• If your IT Glue account restricts API access by source IP, add the following Prismatic egress IPs to the allowlist on the same screen as your API key: 3.132.205.204 and 3.139.185.169.

In Rev.io:

• Your Rev.io Client ID and Client Secret, provided by your account team.
• Asset Types configured for the categories you will be syncing, such as Equipment, License, Other, or custom types.

Configuration

Complete the steps below to configure the IT Glue integration.

1. Click Admin on the sidebar menu and select Integrations Library.
2. Click the Marketplace tab.
3. Locate and select the IT Glue Integration.
4. Click the Configure button. A four-step configuration wizard will launch.
5. Step 1: Connections. Enter your Rev.io Client ID and Client Secret, your IT Glue API Key, and your IT Glue regional URL. Leave Production Mode on unless your account team instructs you otherwise. Click Next.
6. Step 2: Select Flexible Asset Types. Select the IT Glue Flexible Asset Types you want to sync. Only enabled types are shown. Any type not selected here is invisible to the integration, including any passwords attached to assets of that type. Click Next.
7. Step 3: Map Asset Fields. For each selected Flexible Asset Type, map IT Glue trait fields to the corresponding Rev.io fields. Available Rev.io fields include Description, Serial Number, Operating System, IP Address, and Install Date. Asset Name syncs automatically using IT Glue's built-in field. Leave any field unmapped to skip it. 
   NOTE: Serial Number in IT Glue is a trait, not a built-in field. Make sure it exists as a trait on your Flexible Asset Type if you want it to sync. Trait names are case-sensitive. If you rename a trait in IT Glue after mapping, the mapping will silently stop working and will need to be remapped in the wizard.
8. Step 4: Map Asset Types. For each selected Flexible Asset Type, select the Rev.io Asset Type that should be used when a new asset is created on the Rev.io side. For example, map Workstations to Equipment or Software Licenses to License. Click Finish.
9. After the wizard completes, the integration will run an initial organization matching pass. IT Glue organizations are matched to Rev.io customers using fuzzy name matching. Every suggested match starts as Pending. No data flows until you review and accept the suggested links. See the Integrations Library: Data Sync & Mapping article for more information. 
   NOTE: Parent organizations are processed before child organizations to preserve the hierarchy. You can accept, reject, or reassign any link from the integration settings page at any time. Rejecting a link pauses sync without deleting data and can be reversed.
10. Once organization links are accepted, the integration runs an initial asset discovery, matching IT Glue Flexible Assets to existing Rev.io assets by serial number and creating new Rev.io records for anything that does not match. From that point, an hourly sync cycle keeps assets, organization details, and the password list up to date automatically.
11. To sync new customers with IT Glue, open the Integrations tab on the customer profile screen and click the Sync button for the IT Glue integration.

Sync Timing

The table below describes when changes made in either system reach the other.