Ask the Community
Groups
Integrating with ConnectWise Automate (formerly LabTech) - Connect IT Community | Kaseya
<main> <article class="userContent"> <p>Introduction</p> <p>Use this article as a guide to create and maintain an RMM integration with LabTech, now known as ConnectWise Automate (formerly LabTech). This gives you information about CPU, memory, disk usage, last reboot, etc.</p> <p>It should only take about an hour to get up and running with your RMM. This is a rough estimate based on our experience with several partners who integrated with their RMM.</p> <table><tbody><tr><td> <br>The ConnectWise Automate (formerly LabTech) sync described below will do the following:<br><br><ul><li>Discovers all clients and computers</li> <li>Matches clients to organizations in IT Glue using the exact <strong>Company Name</strong> (same mapping used by ConnectWise)</li> <li>Suggests organizations based on name and pattern recognition</li> <li>Matches computers to configurations in IT Glue using a <strong>MAC address or serial number</strong> </li> <li>Suggests configurations based on exact name</li> <li><em>(Optional) Location matching<br>Used to match locations to sub-organizations in IT Glue</em></li> </ul></td> </tr></tbody></table><p>For more information about the device mappings, see <a href="https://kaseya.vanillacommunities.com/kb/articles/aliases/itglue/hc/en-us/articles/360004934137-RMM-field-mappings" rel="noopener nofollow">RMM Field Mappings</a>.</p> <p>Prerequisites</p> <ul><li>An SSL connection with a valid certificate (not self-signed) from a trusted authority is required.</li> <li>Manager or Administrator level access to IT Glue.</li> <li>If you're integrating with a PSA and an RMM, you will want to first sync your RMM to your PSA and your PSA to IT Glue to make sure that the required data is available for matching.</li> <li>A Manager role will only be able to see RMM matched/unmatched data for organizations that they have explicit access to. To grant access to RMM data for all organizations, refer to <strong>Step 7</strong> of our <a href="https://kaseya.vanillacommunities.com/kb/articles/aliases/itglue/hc/en-us/articles/360004938478-Adding-and-removing-users" rel="noopener nofollow">Adding and removing users</a> KB article.</li> </ul><p>Instructions</p> <h3 data-id="enter-your-rmm-credentials">Enter your RMM credentials</h3> <p>An SSL connection with a valid certificate (not self-signed) to your RMM is required. Please refer to <a href="/home/leaving?allowTrusted=1&target=https%3A%2F%2Fdocs.connectwise.com%2FConnectWise_Automate%2FConnectWise_Automate_Documentation%2F020%2F010%2F070" rel="noopener nofollow">ConnectWise Automate's documentation</a> for instructions on how to configure this.</p> <ol><li>Create a dedicated Automate user account with the following settings:</li> </ol><ul><li> <strong>General tab</strong> - Select the <strong>Integrator</strong> checkbox in the bottom-left corner of the window. This will bypass Multi-Factor Authentication (MFA) for accounts used for integrations. MFA should not be enabled on the account. <p><br><img src="https://us.v-cdn.net/6032361/uploads/migrated/9EJ7XX6CRRLA/system-usersandcontacts-users-user-integrator.png" alt="System_UsersandContacts_Users_User_Integrator.png" class="embedImage-img importedEmbed-img"></img></p> </li> </ul><ul><li> <strong>Permissions tab</strong> - Allow read-only permissions to clients and select the <strong>Allow HTTP Tunnel</strong> checkbox. If you haven't modified the user class defaults, you can select Help Desk Users. <p><br><img src="https://us.v-cdn.net/6032361/uploads/migrated/SLSPCOI33XF2/perms.png" alt="Perms.png" class="embedImage-img importedEmbed-img"></img></p> </li> <li> <strong>Groups and Clients tab</strong> - Add All Agents and All Clients to Group Membership. <p><br><img src="https://us.v-cdn.net/6032361/uploads/migrated/IDN62137I91E/groups-and-clients.png" alt="Groups_and_Clients.png" class="embedImage-img importedEmbed-img"></img></p> </li> <li>In addition to the user credentials, you need the Fully Qualified Domain Name (FQDN) of the Automate server. <div> <strong>Important. </strong>Make sure that the Client Name <em>and</em> Company fields are populated in Automate and that they contain the same information. If the Company field is left blank for any clients, those clients will not be available to be matched in the IT Glue matching screen.</div> </li> </ul> Log in to IT Glue and navigate to <strong>Account > Integrations</strong>. Then, click on the green <strong>+ New</strong> button and then on the <strong>ConnectWise Automate (formerly LabTech)</strong> icon. <p><br><img src="https://us.v-cdn.net/6032361/uploads/migrated/YM0GKD056IZM/choose-a-platform-to-sync-your-data-with-it-glue.png" alt="Choose_a_platform_to_sync_your_data_with___IT_Glue.png" class="embedImage-img importedEmbed-img"></img></p> Enter your Automate FQDN (labtech.example.com) and login credentials and then click on the <strong>Connect</strong> button. <p><br><img src="https://us.v-cdn.net/6032361/uploads/migrated/OBG3AUKIYZ1I/labtech-credentials-screen.png" alt="labtech-credentials-screen.png" class="embedImage-img importedEmbed-img"></img></p> After you enter your RMM credentials in IT Glue, you will need to match your IT Glue Organizations to either <strong>Clients </strong>or <strong>Locations</strong>.<br><br><table><tbody><tr style="background-color: DCDCDC;"><td><strong>Option</strong></td> <td><strong>Description</strong></td> </tr><tr><td> <p>Clients</p> </td> <td> <p>Matching on clients will allow you to map to top-level organizations in IT Glue.</p> </td> </tr><tr><td> <p>Locations</p> </td> <td> <p>Matching on locations allows you to map to organizations and sub-organizations in IT Glue.</p> </td> </tr></tbody></table><p>You can change this preference at any point. If you change your preference later, existing matches will be reset. For more information about sub-organizations, see <a href="https://kaseya.vanillacommunities.com/kb/articles/aliases/itglue/hc/en-us/articles/360004934517-When-to-use-sub-organizations-" rel="noopener nofollow">Working with sub organizations</a>.</p> <div> <strong> Note:</strong> If the credentials fail for any reason, syncing will stop until you re-enter your credentials.</div> <h3 data-id="sync-data">Sync Data</h3> <ol><li>From the <strong>Account > Integrations</strong> screen, click <strong>Actions > S</strong><strong>tart Manual Sync</strong>.</li> <li>When the sync is complete, the <strong>Status</strong> column changes from <strong>Syncing... </strong>to <strong>OK</strong>.</li> </ol><h3 data-id="organization-matching">Organization matching</h3> <p>IT Glue discovers organizations and configurations and tries to match them to data in your account. The matching logic can be found in the <em>Introduction</em> section of this article. Anything that isn't automatically matched will need to be manually actioned.</p> <ol><li>From the <strong>Account Integrations</strong> screen, find your RMM in the list and click on <strong>Actions > </strong><strong>Matching</strong>.</li> <li>In the <strong>Unmatched </strong>tab, review the unmatched organizations. <ol type="a"><li>If you're happy with a suggested match, click <strong>Accept Suggestion</strong> to accept it. <p><br><img src="https://us.v-cdn.net/6032361/uploads/migrated/CYWYVRNXKPUS/rmm-customer-unmatched-screen-accept-suggested-match.png" alt="RMM-customer-unmatched_screen_accept_suggested_match.png" class="embedImage-img importedEmbed-img"></img></p> </li> <li>If there is no suggested match, or it is incorrect, you can search for and choose a different organization using the <strong>Match To</strong> field.</li> <li>If no organization exists in IT Glue, you can choose to create an organization. You can also choose to ignore groups, which means they won't count as unmatched items in subsequent syncs.<br><div> <strong> Warning.</strong> Before creating an organization from the matching screen, ensure that no corresponding organization already exists, otherwise a duplicate will be created.</div> </li> </ol></li> <li>If any matches are incorrect, click on <strong>Actions > </strong><strong>Change Match</strong> and select a different organization to match to.</li> </ol><h3 data-id="configuration-matching">Configuration matching</h3> <p>Once all organizations have been matched, the same process should be followed for any unmatched configurations.</p> <ol><li>From the <strong>Matched</strong> tab, choose any organization that has unmatched configurations, click the <strong>Actions</strong> button, and select <strong>Match Devices</strong>. <p><br><img src="https://us.v-cdn.net/6032361/uploads/migrated/7QZY11PKVHKA/rmm-customer-matched-screen-match-devices.png" alt="RMM-customer-matched_screen_match_devices.png" class="embedImage-img importedEmbed-img"></img></p> </li> <li>For any unmatched configurations, you can either accept the suggested match, search for an IT Glue configuration by entering the name in the <strong>Match To</strong> column, or create a new configuration by clicking <strong>Actions > Create Configuration</strong>.</li> <li>Before you create configurations, first match any of the devices based on MAC addresses or serial number, for example, virtual servers. When you're done matching, you can create (in bulk or individually) any of the remaining devices coming in from your RMM. <div> <strong>Important.</strong> We don't recommend that you create configurations from your RMM if you'd like to then have them populate from IT Glue to your PSA. New items created from such data will not sync with your PSA unless you choose to do so manually by editing and saving each and every item. This is absolutely manual and is not recommended.</div> </li> <li>Repeat for each organization until all configurations are actioned.</li> </ol><p>Once everything is matched, the RMM setup is complete. At any time, you can come back to these instructions to discover and match new organizations and configurations from your RMM.</p> <h3 data-id="rmm-logic">RMM logic</h3> <p>Before an organization, site, location, or company in an RMM tool can sync with IT Glue to create an IT Glue organization, you must add at least one configuration to it. If there are none and the organization does not already exist in IT Glue from any other source, then it will <strong>not</strong> appear in IT Glue. In this case, you will need to create it manually.</p> <p>Only RMM companies that have at least one RMM record will sync into IT Glue.</p> <p>Related articles</p> <ul><li><a href="https://kaseya.vanillacommunities.com/kb/articles/aliases/itglue/hc/en-us/articles/360004938098-Overview-of-client-onboarding-steps" rel="noopener nofollow">Overview of client onboarding steps</a></li> </ul> </article> </main>