Skip to main content
Connect Addigy to bring its policies and device inventory into MSPortal. The setup flow is Connect → Map → Import.

​
Before you start

This is an MSP staff task. You need access to Settings > Integrations, permission to manage integrations, authorized vendor credentials, and companies to receive the imported records. Company users do not configure this connection. In Addigy, open Account > Integrations > API & Webhooks, choose the API v2 token workflow, and create a token with the required permissions. Copy it when generated. See Addigy API v2 documentation.

​
Connect the provider

  1. Open Settings > Integrations, find Addigy, and choose its connection/setup action. Use Configure on the existing connection when managing an established setup.
  2. Enter the connection fields below.
  3. Choose Test Connection and resolve any reported error.
  4. After a successful test, choose Create Integration. This saves the connection and starts discovery. A successful test alone does not create it.
Use the v2 token, not the old v1 Client ID and Client Secret pair. Policies are the external records you map to MSPortal companies; they are not automatically new portal companies. Addigy setup in MSPortal with blank credential inputs MSP example: a new connection before credentials are entered.

​
Map policies to companies

  1. Continue to Map after discovery has returned the provider’s policies.
  2. Select an existing company for each intended record, or use Quick Match and review each suggested company.
  3. Review the pending links, then choose Import Selected to apply the selected imports and pending links. Check the selected records as well as the pending-link count before submitting. The wizard’s Next also attempts to save pending mappings before continuing. Check that the rows show saved links before proceeding.
  4. Remove a pending suggestion to discard that draft. Removing an already saved link takes effect immediately.
Creating a company from the mapping screen creates the company immediately; its new mapping still needs to be saved. Check for an existing company first to avoid duplicates. Moving forward from mapping can start synchronization using the saved links.

​
Import devices

The Import step is an entry point. Select Open Device Import to open the actual device staging and type-mapping page. Review the company and device type before importing. Map provider categories to MSPortal device types, then import the intended records. Where offered, Auto-Sync enables future imports for the mapped category and Ignore excludes a category. These are saved configuration choices, not temporary list filters. Follow Import Devices for selection, type mappings and result handling. Check the import result and resulting Devices records. Complete Setup finishes the wizard; its success message does not prove every background sync or device import has completed.

​
Manage an existing connection

An existing connection offers Retest Connection. Typing a token into that test field does not provide a saved credential rotation workflow on this screen. Do not delete an established connection merely to diagnose a failed test. Reopen the specific connection to review mappings and imports. An existing Connection verified state is not evidence that a fresh retest just ran. Inspect recent sync status and errors when diagnosing stale inventory. The wizard’s Delete action opens a Delete Integration confirmation. Read it before proceeding: deletion is not a refresh or a temporary pause. It does not revoke vendor credentials on the vendor’s behalf.

​
Troubleshooting

​
Frequently asked questions

No. For a new connection, complete the successful test and then choose Create Integration. Existing-connection retesting is also distinct from any credential-update action.
No. Device discovery, saved mappings and inventory imports have separate results. Open the device import page and check the resulting inventory.
No. Provider setup is an MSP settings task. Company access to resulting data depends on portal permissions and company scope.
No. This workflow imports inventory from devices already visible to the connected Addigy account. Enrollment and policy administration remain separate Addigy tasks.