> ## 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.

# Overview

> What the Bigleaf integration brings to your Neo Agent setup

Bigleaf Cloud Connect is the SD-WAN service at your clients' sites: a Bigleaf router load-balances each site's internet circuits, fails over when one degrades, and raises a risk when a circuit or router is down. Connect Bigleaf to Neo and your agents check a site-down or circuit-down alert against Bigleaf's live status, say how long a circuit has been down and which ISP it is, and read a site's circuits, routers and risks when users report an outage.

> [!NOTE]
>
> Bigleaf uses one API token per MSP. Connect it once and every agent you enable can use it, with permissions you control per agent. Bigleaf's API only reads: Neo never changes anything in Bigleaf.

## What Neo can do with Bigleaf

> [card] Site & Circuit Status
>
> Read whether a site is healthy, has circuit issues or is offline, each circuit's status (up, degraded, down), and each router's and switch's status.

> [card] Risks
>
> Read the risks Bigleaf raised for a site, such as a circuit down or too little spare bandwidth, with when each started and Bigleaf's recommended action.

> [card] Site Configuration
>
> Read a site's circuits with their type, ISP bandwidth, usage setting and WAN addressing, its LAN networks, routers and points of presence.

> [card] Companies & Users
>
> Read the Bigleaf companies and Cloud Connect users your token reaches.

## Your clients' sites are mapped automatically

Neo matches each Bigleaf site to a company in your PSA and keeps the mapping on the Bigleaf card's **Organization Mapping** tab. It refreshes the mapping when you save the token, and again on each nightly PSA sync. A client with several locations has one site per location, so several sites can map to one company, and a PSA that holds one company per location maps each site to its own.

Matching tries the site's name first, then the name of the Bigleaf company that owns it: exact, then after stripping a legal-form suffix (Ltd, Inc, LLC). Last comes an AI match for the rest.

**A name match, or one you confirm, is handed straight to your agents**, so they start from the client's sites without looking them up. An AI match is not handed to your agents automatically. It shows on the Organization Mapping tab, where you can confirm or correct it.

Anything Neo could not match stays unmapped and visible on the same tab, where you can set the right company by hand. A mapping you set by hand survives every later sync. On a ticket, an agent reaches only the sites mapped to the ticket's company.

## Next steps

> [card] [Connect Bigleaf](https://docs.neoagent.io/integrations/bigleaf/connecting-to-neo.md)
>
> Create an API token in the Bigleaf Cloud Connect dashboard, save it in Neo and turn it on per agent.


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