> ## Documentation Index
> Fetch the complete documentation index at: https://docs.neoagent.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Connecting GoTo Connect to Neo

> Create an OAuth client in the GoTo Developer Center, then save its client ID and secret with a personal access token or an authorization code in Neo

Neo signs in to GoTo Connect as one user of your account, through an OAuth client you create for Neo. You need a GoTo Connect **super admin**, because Neo reads every user's presence and calls.

## 1. Choose the user Neo acts as

Neo can do what this user's permissions and the client's scopes allow. Use a super admin. To read call transcripts, the user also needs the **Access call recordings** permission, and recording with transcription must be on in GoTo Connect. GoTo's recording API is in beta: ask [developer-support@goto.com](mailto:developer-support@goto.com) to turn it on for the OAuth client you create in step 2. A dedicated user keeps the connection working when a person leaves.

## 2. Create the OAuth client

**1. Open the GoTo Developer Center**

Sign in at [developer.logmeininc.com](https://developer.logmeininc.com/clients) and choose **OAuth Clients**, then **Create a client**.

**2. Name it and add a redirect URI**

Name it "Neo", and add the redirect URI `https://localhost`. GoTo asks for one; Neo uses it only for the authorization code sign-in.

**3. Choose the scopes**

Select the GoTo Connect scopes for the areas your agents use (see the table below). `users.v1.read` is required: Neo checks the connection with it.

**4. Copy the client ID and secret**

Copy the **Client ID** and **Client Secret**. GoTo shows the secret once.

| Neo area | GoTo scopes |
| - | - |
| Account & Locations | `voice-admin.v1.read`, `voice-admin.v1.write` |
| Users, Lines & Identity | `users.v1.read`, `users.v1.lines.read`, and the SCIM identity scopes |
| Extensions & Forwarding | `voice-admin.v1.read`, `voice-admin.v1.write` |
| Call Queues | `voice-admin.v1.read`, `voice-admin.v1.write` |
| Devices & Phone Numbers | `voice-admin.v1.read`, `voice-admin.v1.write` |
| Presence & Live Calls | `presence.v1.read`, `presence.v1.write`, `call-events.v1.events.read`, `call-parking.v1.read` |
| Call History & Reports | `cr.v1.read`, and the contact center analytics scopes if you use them |
| Place & Control Calls | `calls.v2.initiate`, `call-control.v1.calls.control` |
| Call Transcripts | `recording.v1.read` |
| Voicemail & Fax | `voicemail.v1.voicemails.read`, `voicemail.v1.voicemails.write`, `fax.v1.read`, `fax.v1.write` |
| Text Messages | `messaging.v1.read`, `messaging.v1.write`, `messaging.v1.send` |
| Webhooks & Event Subscriptions | each API's `notifications.manage` scope |

## 3. Sign in: a personal access token

This is the simplest sign-in. If your GoTo account cannot create personal access tokens, use the authorization code in step 4 instead.

**1. Allow the grant on the client**

In the Developer Center, edit the client, open **Grant types**, turn on **Personal Access Token**, and save.

**2. Create the token**

Signed in as the user from step 1, open [myaccount.goto.com](https://myaccount.goto.com), choose **Developer Tools**, and click **Create token**. Give it the same scopes as the client, and copy it: it shows once.

**3. Save it in Neo**

In the Neo Dashboard, open **Integrations** and find the GoTo Connect card, under Phone & VoIP. Choose the sign-in **Personal access token**, enter the client ID, the client secret and the token, and click **Save settings**. Neo signs in and reads the user's GoTo Connect setup before it saves, so a wrong secret, a grant that is off, or a missing scope is refused straight away, with GoTo's reason.

## 4. Or sign in: an authorization code

**1. Open the sign-in link**

As the user from step 1, open this link in a browser, with your client ID in place of `CLIENT_ID`:

`https://authentication.logmeininc.com/oauth/authorize?client_id=CLIENT_ID&response_type=code&redirect_uri=https://localhost`

**2. Copy the code**

Sign in and allow access. The browser then opens `https://localhost` and shows an error page: that is expected. Copy the value after `code=` from the address bar.

**3. Save it in Neo at once**

On the GoTo Connect card, choose the sign-in **Authorization code**, enter the client ID, the client secret, the redirect URI `https://localhost` and the code, and click **Save settings**. A code works once and for a few minutes. Neo exchanges it and keeps the connection alive from then on.

> [!WARNING]
>
> If the token is revoked, the user is removed, or the OAuth client is deleted, Neo loses access until you save new credentials here.

## 5. Turn GoTo Connect on per agent

Open the agent, go to its **Tools & Settings** tab, click **Phone & VoIP**, and expand the **GoTo Connect** block. Pick one of its **Presets**, or set each area yourself.

| Preset | What runs on its own | What asks a technician |
| - | - | - |
| **Read Only** | Every read | No write is allowed |
| **Helpdesk** | Every read | Every change, call and text. Users and webhooks stay read only |
| **IT Admin** | Every read, and changes to extensions, forwarding, queues, devices, numbers, calls, voicemail and texts | Users and groups |
| **Full Automation** | Every read and write | Webhooks, deleting or changing a location, and the updates that replace a whole list or record |

## Use it for dispatch

To have dispatch skip a technician who is on the phone, use the **Dispatcher Agent** template and give it the **Presence & Live Calls** and **Users, Lines & Identity** areas as Read Only. Each technician's PSA email must be their GoTo email. Ask Neo Support to set it up for you.

## Use it for a ticket on each call

A scheduled agent with **Call History & Reports** and **Call Transcripts** as Read Only, and your PSA's ticket and time entry rights, opens a ticket for each customer call and logs it as a time entry. Use the **GoTo Connect Call Tickets** template.

## Limits

GoTo allows 10 requests a second per API, and Neo keeps to that. Call transcripts and AI summaries exist only when GoTo Connect records and transcribes the call, and AI summaries need GoTo's advanced reporting.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.