Mac, iPhone and iPad tickets, worked inside Addigy.
Neo reads your Addigy devices, alerts and script library while it works a ticket. It runs scripts and device commands on Apple devices, with technician approval where you want it.
What Neo does with Addigy.
Every Apple device, mapped
Neo syncs the Macs, iPhones and iPads in your Addigy organization, and its child organizations when the key can read them. It links each device to its PSA company.
Runs your Addigy scripts
Neo searches your Addigy script library for a match to the issue and runs it on the Mac. Each run uses the script as it is in Addigy at that moment.
Approval on what matters
You set an access level and approval per permission group. Erasing, locking or removing a device always asks a technician first.
Concrete work Neo handles in Addigy.
Alert triage
Reads received Addigy alerts and system events for the device, then acknowledges, mutes or resolves the alert when the agent has write access.
Script runs on Macs
Finds the right script in your library and runs it as root on the named Mac. The agent can read the command output afterwards.
macOS and iOS updates
Reads installed and available OS updates per device and schedules an install on the devices you name. An install can restart the device.
Lost or stolen devices
Finds the device by serial number or user. Lost mode, lock and erase each go to a technician for approval before Neo sends them.
Live in under an hour.
Connect, configure, go. No code, no long implementation.
Connect Addigy
Create an API v2 key in your top-level Addigy organization and paste it into the Addigy card in Neo. Neo checks that the key can read devices and policies before it saves.
Check device mapping
Neo maps each device to a PSA company through your Addigy client organizations and policies. Confirm the result on the Device Mapping tab and assign any unmapped device.
Choose what agents can do
Pick an access profile for each agent: Read Only, Helpdesk, IT Admin or Full Automation. Helpdesk asks a technician before commands, MDM actions and updates.
Questions about the Addigy integration.
What can Neo change in Addigy?+
Only the actions Neo supports: run scripts and commands, restart, shut down or rename a device, unlock a user account, work alerts, move devices between policies, deploy a profile, schedule OS updates and assign devices to end users. Neo refuses any other Addigy write. It never reads the managed admin password or other stored secrets.
Which actions need technician approval?+
You set approval per permission group. Some actions always ask a technician, whatever the setting: erasing, locking or removing a device, turning on lost mode, rotating the FileVault key or the managed admin password, and creating, changing or removing an Addigy console user.
What does the Addigy API key need?+
One API v2 key from your top-level organization with View Devices and read access to policies. Read access to child organizations lets Neo sync their devices too. To find and run scripts, add View Predefined Commands and Execute Commands.
We also manage Windows devices. Does that work?+
Addigy manages Apple devices only. Connect a second RMM for Windows devices. Neo connects several RMMs at once, and each device stays with the RMM it came from.
Ready to wire up Addigy?
14-day free trial. No credit card. Live in under an hour, right inside your stack.