The Addigy integration is currently in Beta. Core functionality is complete and available for all users. You will see a “Beta” badge on the Addigy card in the Integrations page.
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.Log into Addigy
Access your Addigy portal at app.addigy.com.
Create a New API Token
Click New API Token and give it a descriptive name (e.g., “MSPortal Integration”).
Required Information
Before proceeding to MSPortal, ensure you have:| Information | Description |
|---|---|
| API Token | The V2 API token generated in Addigy |
Part 2: MSPortal Setup Wizard
MSPortal provides a guided setup wizard to connect and configure your Addigy integration.Starting the Wizard
Step 1: Connect
Enter your Addigy API token to establish the connection.Enter API Token
Paste your Addigy V2 API token into the API Token field.
Your token is stored securely using encrypted vault storage. It is never exposed in logs or API responses.
Test Connection
Click Test Connection to verify your token. You will see a green “Connection successful” 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
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.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 check back. The initial sync runs in the background and may take several minutes.
Review Policy List
The mapping table displays all policies from Addigy with:
- Policy Name - The name of the policy in Addigy
- Mapped To - The MSPortal company (if mapped)
- Confidence - Matching confidence score (for auto-matched policies)
Use Quick Match (Recommended)
Click Quick Match to automatically map policies to companies with similar names. This uses fuzzy matching to find likely matches.
- Policies matched with high confidence are automatically mapped
- Review the results and adjust any incorrect mappings
Manually Map Remaining Policies
For policies that were not auto-matched:
- Find the policy in the list
- Click the company dropdown in the “Mapped To” column
- Search for and select the correct MSPortal company
- The mapping is saved automatically
Step 3: Import Devices
After mapping policies, import devices from Addigy into your MSPortal asset inventory.Open Device Import
Click Open Device Import to access the full device import interface. This opens a dedicated page for managing device imports.
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.Use Quick Match
Click Quick Match to automatically map Addigy device types to existing MSPortal device types with similar names.
Use Quick Create for Remaining Types
Click Quick Create to automatically create new MSPortal device types for any unmatched Addigy types.
Enable Auto-Sync (Optional)
Check the Auto-Sync checkbox for device types you want automatically imported. New devices of these types will be imported without manual intervention during each sync cycle.
Auto-sync requires a device type mapping. You must select a “Maps To” value before enabling auto-sync.
Staged Devices
The Staged Devices table shows devices ready for import from mapped policies.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.
Review Staged Devices
The table displays:
- Device 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)
- Status - Whether the device has been imported
What Gets Synced
| Data Type | Sync Direction | Description |
|---|---|---|
| Policies | Addigy to MSPortal | Policies for mapping to companies |
| Devices | Addigy to MSPortal | All managed Apple devices from mapped policies |
| Device Types | Addigy to MSPortal | Device model classifications for mapping |
| Hardware Details | Addigy to MSPortal | Model, processor, RAM, disk space |
| Security Status | Addigy to MSPortal | FileVault, Firewall, Gatekeeper, SIP, MDM status |
| Network Info | Addigy to MSPortal | IP address, MAC address, hostname |
| Battery Data | Addigy to MSPortal | Battery percentage, charging status, cycle count |
| User Info | Addigy to MSPortal | Current user, user email |
| Online Status | Addigy to MSPortal | Whether the device is currently online |
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
Sync Schedule
Addigy data syncs automatically on the following schedule:| Sync Type | Schedule | Description |
|---|---|---|
| Policies | Daily at 2:00 AM UTC | Syncs all policies from Addigy |
| Devices | Every 4 hours | Syncs devices from mapped policies, updates staged data |
Managing Your Integration
After setup, manage your integration from Settings > Integrations:| Action | Description |
|---|---|
| Configure | Re-open the setup wizard to modify settings or re-map policies |
| Import Devices | Access the device import page directly |
| Resync | Trigger a fresh sync of all data from Addigy |
| Delete | Available inside the Configure wizard - permanently removes the integration |
Re-running the Wizard
You can return to any step of the setup wizard at any time:- Go to Settings > Integrations
- Click Configure on the Addigy card
- Navigate between steps using the step indicators or Back/Next buttons
Updating API Credentials
If you need to update your Addigy API token:Troubleshooting
Connection test fails
Connection test fails
Causes:
- Incorrect API token
- Token has been revoked or expired
- Addigy account does not have API access enabled
- Verify your API token is copied exactly, without extra spaces
- Generate a new API token in Addigy (Account > Integrations > API & Webhooks > V2)
- Confirm your Addigy account has API access permissions
No policies appear in mapping step
No policies appear in mapping step
Causes:
- Initial sync still in progress
- API token lacks read permissions
- Wait a few minutes for the background sync to complete
- Click Sync to trigger a manual sync
- Verify your API token has the necessary read permissions in Addigy
No devices in staging area
No devices in staging area
Causes:
- No policies have been mapped to companies
- Device sync still in progress
- Policies do not have any enrolled devices
- Map at least one policy to a company in the Map step
- Wait for the device sync to complete (can take several minutes initially)
- Click Sync Now to trigger a fresh sync
Import fails for some devices
Import fails for some devices
Causes:
- Device type not mapped
- Policy mapping was removed
- Ensure all device types have a “Maps To” value configured
- Verify the policy is still mapped to a company
- Check for error messages in the import results
Auto-sync not importing new devices
Auto-sync not importing new devices
Causes:
- Auto-sync not enabled for the device type
- Device type not mapped
- Policy not mapped to a company
- Enable the Auto-Sync checkbox for the device type
- Ensure the device type has a “Maps To” mapping configured
- Verify the device’s policy is mapped to a company
Extended device data not showing
Extended device data not showing
Causes:
- Device was recently imported and extended data has not synced yet
- Device is offline and Addigy cannot collect current facts
- Wait for the next sync cycle to populate extended data
- Click Sync Now to trigger a manual refresh
- 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
Related Resources
- Import Devices - Detailed guide on device type mappings, auto-sync, and category ignore
- Devices Module - Managing devices in MSPortal
- Import Companies - General company import guide
- Clear and Resync Integrations - Troubleshooting sync issues
- Datto RMM Integration - Similar RMM integration guide