GoTo Resolve

GoTo Resolve (formerly LogMeIn Resolve) is a remote monitoring and management (RMM) platform. This connector brings in the devices managed through your GoTo Resolve account.

At a glance

Required permissions

Why Personal Access Token

GoTo offers a few ways to obtain an access token. The Authorization Code flow (with a Refresh Token to keep it alive) is the standard choice for an interactive, user-facing application, but it needs a browser-based login and consent step, and GoTo’s own documentation confirms its refresh tokens are periodically and silently rotated — a new one is occasionally issued in place of the old one, with no way for an unattended background job to notice and react. The Personal Access Token grant is what GoTo itself documents as the option for scripts and API integrations that run without a user present: no browser step, and the token stays valid until it’s manually revoked, rather than rotating on its own. That reliability is why Navigator uses it here.

Recommended: generate the token from a dedicated GoTo user account set up for this integration, not an individual employee’s personal account. GoTo attributes every API call made with a token back to that token’s owning user in its own activity/audit history, so a shared integration account keeps sync activity clearly distinguishable from that person’s own actions, and means the connection won’t unexpectedly break if that individual’s account is later disabled or they leave the organization.

Setup

This connector uses GoTo’s Personal Access Token flow — there’s no browser authorization click-through required. Two separate portals are involved, and the first one isn’t linked from anywhere in the newer developer.goto.com site’s own navigation, so you have to go there directly.

1. Sign into developer.logmeininc.com/clients directly. Create an OAuth Client if you don’t have one yet, scoped to support:.
2. In that client’s settings, turn on the “Personal access token” toggle (“Allow users to manually generate a token to access APIs without going through the full OAuth flow”) → Save.
3. Go to myaccount.goto.com → Developer Tools → Create token, scoped to support:. Save the resulting token — it’s shown once. Both the Client ID/Secret and the token are required together: the token identifies the authorizing user, the client identifies the application exchanging it, and GoTo’s token endpoint checks both on every request.
4. In Navigator, go to Connectors → Add a Connector → GoTo Resolve.
5. Enter your Client ID, Client Secret (both from step 1), and Personal Access Token (from step 3).
6. Save. Navigator validates the credentials and enqueues a first sync immediately.

What data this connector provides

• Devices: every device managed through GoTo Resolve, including hostname, manufacturer, model, serial number, OS details, IP and MAC addresses, storage, and disk encryption status.

Known limitations

• GoTo Resolve’s own users are GoTo support/technician accounts, not your organization’s directory users, so this connector provides device data only.
• The Personal Access Token doesn’t expire on a fixed schedule, but it can be revoked from myaccount.goto.com at any time — if a sync starts failing with an authentication error, check there first.