Connections and Integrations

Connect the tools that Deepwell gets data from: your PSA, your backup products, and your security products. Each Connection holds your credentials for one Integration. Only an MSP Admin can control Connections.

An MSP User can still open the Connections page and see which tools are connected, though each card shows a View only status and its controls are inactive. The page reads "Connections can be viewed, but only an MSP admin can add or edit them."

How to connect a tool

1. Go to Connections, in the Admin menu.
2. Select the card of the tool to connect.
3. Type its credentials and save them. For ConnectWise, Acronis, and SentinelOne, Deepwell tests the credentials as you save them, so you'll know right away if a value isn't correct. Deepwell doesn't test a Custom Connection. See Custom Connections.

The credentials for each tool

Make these credentials in the admin settings or the API settings of the tool.

ConnectWise PSA (before, the name was ConnectWise Manage)

• Domain: the domain of your ConnectWise site, without https://
• Company Name: the company ID that you use to sign in to ConnectWise. This is not the display name of your business.
• Public Key and Private Key: make an API Member in ConnectWise and generate its keys. Deepwell keeps your private key in encrypted form.
• Client ID: make this ID on the ConnectWise Developer Network.

Acronis

• Data Center: the host of your Acronis console, without https://. For example, us5-cloud.acronis.com.
• Client ID and Client Secret: make an API client in the API settings of your Acronis console.

SentinelOne

• Domain: the domain of your SentinelOne management console, without https://
• API Key: generate an API token in your SentinelOne management console.

Custom: a Connection to any other REST API. Select New Custom Connection on the Connections page to make one.

• Name: a name for the Connection.
• Description: optional context about the Connection.
• Domain: the domain of the tool's API, without https://.
• Static or OAuth2: the type of authentication the tool uses.
• Token URL, Client ID, and Client Secret: required for OAuth2. Make these in the tool's own developer settings.
• Headers or query parameters: optional. Deepwell sends these with every request from the Connection.

Custom Connections

Deepwell doesn't test a Custom Connection when you save it, so a wrong domain or credential shows only when a Data Source that uses the Connection runs. After you save one, make a Data Source that uses it and run a Test Request. See Data Sources.

A Static Connection with no headers and no query parameters sends no credentials, so when you save one, Deepwell asks Save without headers or query parameters?. That is correct for a public API only.

With OAuth2, do not add an Authorization header. Deepwell sends the token in that header itself, and shows The Authorization header is reserved for the OAuth2 token. if you add one.

The Integrations catalog

Deepwell's catalog of Integrations keeps growing, so review the Integrations page in the app for the current list rather than treating the examples in this guide as the full set.

For more about how Deepwell keeps these credentials, and about who can get access to them, see Security and Trust and the Privacy Policy.

How to update a Connection

Credentials and tokens can expire, and Deepwell doesn't send you an alert when they do, so a Report that uses the Connection fails at its next run.

To repair the Connection, open the tool's card and type its credentials again. Deepwell checks that you filled the required fields, and it tells you which field is empty if you miss one. Because a tool keeps one Connection, saving again updates that Connection instead of making a second one, and Deepwell warns you before it replaces the credentials it holds.

How to stop using a Connection

Deepwell doesn't delete a Connection for ConnectWise, Acronis, or SentinelOne. A Connection holds the credentials for a tool, and your Data Sources and Organization Imports run through it, so removing one would stop every Report that depends on it.

To stop reporting on one of these tools, archive the Data Sources that use its Connection. See Data Sources. To point a tool at a different account, open its card and type the new credentials, and Deepwell replaces them on the same Connection, so your Data Sources keep working.

A Custom Connection is different. Open its card and select Archive, then confirm with Archive Connection. Deepwell deletes the credentials right away, you can't get them back, and a Data Source that used the Connection stops working. To use the tool again, make a new Custom Connection with new credentials.