> ## 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 Moovila to Neo

> Register an app in Moovila, get a refresh token with Moovila's Postman collection, and save them in Neo

You connect Moovila once at the MSP level. Moovila's API uses OAuth: you register an app in Moovila, sign in to it once, and give Neo the app's Client ID and Client Secret and the refresh token from that sign-in. Neo keeps the token up to date from then on.

The connection reads what the Moovila user who signs in can see, so sign in as a user who can see every project you want agents to read.

## 1. Register an app in Moovila

You need Moovila's **Integrations Manager** permission for this step.

<Steps>
  <Step title="Open the Moovila API tile">
    In Moovila, open **More Options** in the left navigation, then **Integrations**, then the **Moovila API** tile. Click **Add an Application**.
  </Step>

  <Step title="Name the app and set the callback">
    Name it "Neo". For the callback URL, enter the Callback URL that Moovila's Postman collection shows in step 2 (with **Authorize using browser** on, it is `https://oauth.pstmn.io/v1/browser-callback`).
  </Step>

  <Step title="Tick the data">
    Tick **Projects and Tasks**, **Users**, **Time Entries** and **Lookup Tables**. All four are read access. Save.
  </Step>

  <Step title="Copy the details">
    Open the app and copy the **Client ID** and **Client Secret**.
  </Step>
</Steps>

## 2. Get a refresh token

Moovila offers only the sign-in flow, so you sign in once with Moovila's own Postman collection, as [Moovila's guide](https://moovila.zendesk.com/hc/en-us/articles/28861599846669-Moovila-API-Setting-up-and-Testing-Queries-in-Postman) shows.

<Steps>
  <Step title="Open the collection">
    In Postman (the desktop app or the web), fork Moovila's collection from that guide.
  </Step>

  <Step title="Enter the app's details">
    In the collection's **Variables**, paste the Client ID and Client Secret into **client\_id** and **client\_secret**, and save.
  </Step>

  <Step title="Sign in">
    On the collection's **Authorization** tab, click **Get New Access Token**, and sign in to Moovila as the user whose view Neo should have.
  </Step>

  <Step title="Copy the refresh token">
    In the token Postman shows, copy the **Refresh Token** (a value like `1b4e28ba-2fa1-11d2-883f-0016d3cca427`), not the Access Token. Do not use this token anywhere else, because Neo keeps it up to date.
  </Step>
</Steps>

## 3. Add the details in Neo

<Steps>
  <Step title="Open Integrations">
    Open [**Integrations → Moovila**](https://dashboard.neoagent.io/integrations?tab=directory\&open=moovila) in the Neo Dashboard. The card is under Other.
  </Step>

  <Step title="Save">
    Paste the **Client ID**, **Client Secret** and **Refresh Token**, and click **Save**. Neo checks them with Moovila before it saves, so a wrong value is rejected straight away.
  </Step>
</Steps>

If Moovila later refuses the token (the session ended, the app was deleted, or its Client Secret was reset), Neo tells you in your inbox. Get a new refresh token as in step 2 and save it again.

## 4. Turn Moovila on per agent

Open the agent from [**Agents**](https://dashboard.neoagent.io/agents), go to the Integrations section, and configure the Moovila block. The one profile, **Read Only**, reads every group. For capacity estimates, the agent needs **Projects and Tasks**, **Users** and **Lookup Tables**; the calculation runs in the agent's [sandbox](/agents/tools/built-in/sandbox), which every agent has.

See [Moovila API](/agents/tools/management/moovila-api) for what each group covers.


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