Skip to main content
This guide walks you through connecting your Addigy instance to MSPortal.ai using our streamlined setup wizard. Addigy is a cloud-based Apple device management platform, and this integration syncs your policies and macOS/iOS devices into MSPortal.

​
Overview

The Addigy integration syncs your Apple device fleet into MSPortal, allowing you to:
  • Import and manage macOS devices from Addigy
  • Map Addigy policies to your MSPortal companies
  • Keep device inventory synchronized automatically
  • View extended device details including hardware, security, battery, and MDM status
  • Track devices in reports and compliance workflows

​
Prerequisites

Before you begin, ensure you have:
  • Active Addigy account with administrative access
  • MSPortal.ai account with integration management permissions
  • Companies already set up in MSPortal (from your PSA integration or manually created)
The Addigy integration maps policies to existing companies in MSPortal. Import your companies from your PSA integration first, or create them manually before setting up Addigy.

​
Part 1: Generate an API Token in Addigy

Before connecting to MSPortal, you need to create an API token in Addigy.
1

Log into Addigy

Access your Addigy portal at app.addigy.com.
2

Navigate to API Settings

Go to Account > Integrations > API & Webhooks > V2.
Use a V2 API token. The older V1 Client ID and Client Secret pair does not work with MSPortal.
3

Create a New API Token

Click New API Token and give it a descriptive name (e.g., “MSPortal Integration”).
A read-only API token is sufficient for MSPortal to sync your device and policy data. This follows the principle of least privilege.
4

Copy Your Token

Copy the generated API token immediately.
Copy the API token right after creation. It may not be retrievable once you close the dialog. Store it securely for use in MSPortal.

​
Required Information

Before proceeding to MSPortal, ensure you have:

​
Part 2: MSPortal Setup Wizard

MSPortal provides a guided setup wizard to connect and configure your Addigy integration: Connect, Map and Import.

​
Starting the Wizard

1

Navigate to Integrations

In MSPortal, go to Settings > Integrations.
2

Start Setup

Find Addigy and click Connect to launch the setup wizard. For an existing connection, click Configure.

​
Step 1: Connect

Enter your Addigy API token to establish the connection.
1

Enter API Token

Paste your Addigy V2 API token into the API Token field.Addigy setup in MSPortal with blank credential inputs
Your token is stored securely using encrypted vault storage. It is never exposed in logs or API responses.
2

Test Connection

Click Test Connection to verify your token. You will see a green “Connection tested successfully” message when the test passes.If the connection fails:
  • Verify your API token is copied correctly without extra spaces
  • Ensure the token has not been revoked or expired
  • Confirm your Addigy account has API access enabled
3

Create Integration

Once the connection test passes, click Create Integration to save your credentials and proceed. A successful test alone does not save the connection.

​
Step 2: Map Policies

Map your Addigy policies to MSPortal companies. Addigy uses policies as the primary organizational unit (similar to sites in other RMM tools). Only devices from mapped policies will be available for import.
1

Wait for Initial Sync

After creating the integration, MSPortal begins syncing your policies from Addigy. This may take a few minutes depending on the number of policies.
If no policies appear, wait a few minutes and click Check for Policies. The initial sync runs in the background and may take 10 minutes or more depending on device count.
2

Review Policy List

The mapping table displays all policies from Addigy with:
  • Name - The name of the policy in Addigy
  • Mapped - The MSPortal company the policy is linked to
  • Status - Pending for a link that is not saved yet, Saved for a saved link
The Total Items, Mapped and Unmapped tiles above the table show your progress. Click a tile to filter the list to those policies.
3

Use Quick Match (Recommended)

Click Quick Match to find companies with similar names. A Quick Match Results dialog lists each suggested match with its confidence score.
  • Matches at 70% confidence or higher are selected by default. Move the slider to select more or fewer matches.
  • Check or uncheck individual matches, then click Apply Matches.
  • Applied matches appear as Pending in the table. They are not saved yet.
4

Manually Map Remaining Policies

For policies that were not matched:
  1. Find the policy in the list
  2. Click the company dropdown in the Mapped column
  3. Search for and select the correct MSPortal company
  4. The row shows Pending until you save it
To link several policies to the same company, check their rows, choose the company in the selection bar above the table, and click Assign.
If a company does not exist yet, click the + button in the row (or Create new company above the table) to create it. Check for an existing company first to avoid duplicates.
5

Save Your Mappings

Click Import Selected to save the pending links. The button shows how many changes are waiting. Clicking Next also saves pending links before moving on.
6

Unmap Policies (Optional)

To remove a saved mapping, click the X button next to the mapped company name. Removing a saved link takes effect immediately. Removing a pending link only discards the draft.
You must map at least one policy before proceeding to device import. Devices from unmapped policies will not appear in the import staging area.

​
Step 3: Import Devices

After mapping policies, import devices from Addigy into your MSPortal asset inventory.
1

Open Device Import

Click Open Device Import to access the full device import interface. This opens a dedicated page for managing device imports.
2

Complete Setup

Click Complete Setup to finish the wizard. You can always return to the device import page later from Settings > Integrations. Completing setup does not mean every background sync or import has finished.

​
Part 3: Device Import

The device import page lets you configure device type mappings and selectively import devices. For a detailed guide on device type mappings, auto-sync, and category ignore, see Import Devices.

​
Device Type Mappings

Before importing devices, map Addigy device types to your MSPortal device types.
1

Use Quick Match

Click Quick Match to automatically map Addigy device types to existing MSPortal device types with similar names.
2

Use Quick Create for Remaining Types

Click Quick Create to automatically create new MSPortal device types for any unmatched Addigy types.
3

Enable Auto-Sync (Optional)

Turn on Auto-Sync for device types you want automatically imported. New devices of these types will be imported without manual intervention during each sync cycle. Click Enable All Auto-Sync to turn it on for every mapped type.
Auto-sync requires a device type mapping. You must select a “Maps To” value before enabling auto-sync.
4

Ignore Categories (Optional)

Check the Ignore checkbox for device types you never want to import. Ignored categories are dimmed and excluded from pending import counts.

​
Device Preview

The Device Preview table shows devices ready for import from mapped policies.
1

Trigger a Sync

Click Sync Now in the page header to fetch the latest devices from Addigy.
The initial sync may take some time to complete depending on the size of your fleet. Subsequent syncs are faster.
2

Review Staged Devices

The table displays:
  • Name - Hostname of the device
  • Type - Addigy device classification
  • Company - The mapped MSPortal company
  • Manufacturer - Always Apple for Addigy devices
  • Model - Device model (e.g., MacBook Pro, iMac)
  • OS - Operating system version
  • Status - Whether the device has been imported
3

Search and Filter Devices

Use the search bar to find specific devices. Toggle Show unimported only to hide devices that have already been imported.
4

Select and Import

  1. Check the boxes next to devices you want to import
  2. Click Import Selected to import the selected devices
  3. Imported devices appear in your MSPortal device inventory
To hide devices you never want to import, select them and click Ignore Selected.
For bulk imports, use the device type mapping’s “Import All” button or click “Import All Mapped” instead of selecting individual devices.

​
What Gets Synced

​
Extended Device Data

Devices imported from Addigy include rich extended data visible in the Device Detail view. Click any device in the Devices module to see:
  • Hardware - Processor, RAM, total and free disk space with usage percentage
  • Security - FileVault encryption, Firewall, Gatekeeper, System Integrity Protection (SIP), MDM enrollment, supervised status
  • Network - Hostname, LAN IP, WAN IP, Wi-Fi and Ethernet MAC addresses
  • Battery - Battery percentage, charging status, and cycle count
  • User - Current logged-in user and email
  • System - OS version, agent version, last seen time
Importing an Addigy device into MSPortal does not enroll it in Addigy MDM. Enrollment and policy administration stay in Addigy.

​
Sync Schedule

Addigy data syncs automatically on the following schedule: You can trigger a manual sync at any time by clicking Sync Now on the device import page.

​
Managing Your Integration

After setup, manage your integration from Settings > Integrations:

​
Re-running the Wizard

You can return to any step of the setup wizard at any time:
  1. Go to Settings > Integrations
  2. Click Configure on the Addigy connection
  3. Navigate between steps using the step indicators or Back/Next buttons

​
Retesting the Connection

1

Open Integration Settings

Go to Settings > Integrations and click Configure on the Addigy connection.
2

Retest

On the Connect step, click Retest Connection. MSPortal tests the saved token. You can also paste a token into API Token to test it.
Retesting does not save a new token. The Connect step on an existing Addigy connection has no credential update action. If you need to replace the token, contact support@msportal.ai. Do not delete a working connection just to diagnose a failed test, because deleting removes its mappings.

​
Troubleshooting

Causes:
  • Incorrect API token
  • Token has been revoked or expired
  • A V1 credential was used instead of a V2 token
  • Addigy account does not have API access enabled
Solutions:
  1. Verify your API token is copied exactly, without extra spaces
  2. Generate a new V2 API token in Addigy (Account > Integrations > API & Webhooks > V2)
  3. Confirm your Addigy account has API access permissions
Causes:
  • Initial sync still in progress
  • API token lacks read permissions
Solutions:
  1. Wait a few minutes for the background sync to complete
  2. Click Check for Policies, or Resync on the Integrations page
  3. Verify your API token has the necessary read permissions in Addigy
Cause: The link was still Pending when you left the page. Pending links are drafts until you save them.Solution: Re-select the company and click Import Selected (or Next). Check that the row shows Saved.
Causes:
  • No policies have been mapped to companies
  • Device sync still in progress
  • Policies do not have any enrolled devices
Solutions:
  1. Map at least one policy to a company in the Map step and save it
  2. Wait for the device sync to complete (can take several minutes initially)
  3. Click Sync Now to trigger a fresh sync
Causes:
  • Device type not mapped
  • Policy mapping was removed
Solutions:
  1. Ensure all device types have a “Maps To” value configured
  2. Verify the policy is still mapped to a company
  3. Check for error messages in the import results
Causes:
  • Auto-sync not enabled for the device type
  • Device type not mapped
  • Policy not mapped to a company
Solutions:
  1. Enable Auto-Sync for the device type
  2. Ensure the device type has a “Maps To” mapping configured
  3. Verify the device’s policy is mapped to a company
Causes:
  • Device was recently imported and extended data has not synced yet
  • Device is offline and Addigy cannot collect current facts
Solutions:
  1. Wait for the next sync cycle to populate extended data
  2. Click Sync Now to trigger a manual refresh
  3. Verify the device is online in your Addigy portal

​
Best Practices

Map Policies First

Always map your Addigy policies to companies before trying to import devices. Unmapped policy devices will not appear in staging.

Use Quick Match

Start with Quick Match for policy mapping, then manually adjust any incorrect matches. It saves significant time.

Enable Auto-Sync

For device types you always want imported (like MacBooks and iMacs), enable Auto-Sync to reduce manual work.

Ignore Unwanted Types

Use the Ignore checkbox to permanently hide device types you do not manage. This keeps your pending import counts clean and accurate.

​
Security and Privacy

  • Credential Storage: Your Addigy API token is encrypted using vault storage and never exposed in logs or responses
  • Data Isolation: All synced data is tenant-isolated and only visible to your organization
  • Read-Only Access: MSPortal only requires read access to Addigy data; it never modifies your Addigy configuration
  • Rate Limiting: MSPortal uses conservative API rate limits to avoid triggering Addigy’s rate limit protections

​
Need Help?

For assistance with the Addigy integration, contact support@msportal.ai.