Connect Addigy for macOS fleet reporting

Addigy manages your customers' Apple fleet. Connect it and Current mirrors that fleet — every managed Mac, its macOS version, FileVault/encryption status, policy compliance, and last check-in — so it shows up in your executive and CIO business reviews. The connection is strictly read-only.

• ＋Your customer list: Current reads your Addigy child organizations directly, so every customer shows up by name — even the ones with no Macs online yet. If your account keeps customers as policies under one master organization instead (a common single-org setup), each policy is listed as a customer too — and mixed setups with both child orgs and policies work as well.
• ＋Device inventory per organization: device name, model, serial, macOS version, and online / last-seen.
• ＋Health signals: FileVault (disk-encryption) status, plus policy/benchmark compliance when Addigy reports it.
• ＋The Addigy organization each device belongs to — used to map devices to your Current companies.

1. 1
   Sign in to the Addigy web app as an admin

   You need an account that can manage integrations for your parent (MSP) organization.
2. 2
   Open Account ▸ Integrations ▸ API & Webhooks

   This is where Addigy's v2 API tokens are created. (The old v1 client-id / client-secret pair was retired on 2026-03-31 — Current uses a v2 API token, sent to Addigy as the x-api-key header, not an Authorization: Bearer token.)
3. 3
   Choose New API Token

   Give it a recognizable name like 'Current (read-only reporting)'. Make sure the token can read your organization tree and devices (the account that creates it needs access to your child organizations) — that's how Current lists your customers. Copy the token — you'll paste it into Current once and never see it again.
4. 4
   Paste it into Current

   In Settings → Integrations, open the Addigy card, paste the API Token, and click Test connection. Current validates it against Addigy live and turns the card green.

In Addigy, each end-customer is usually an organization (a child organization under your MSP org). Current lists all of them and links each to a Current company automatically — first by the Autotask account id Addigy already stores on the organization's policy (an exact match, so this tier fires on Autotask workspaces; on ConnectWise the name match carries the load), then by company name. The name match understands how policy names decorate a company name: a direct match, a suffix ("Northwind Traders - Production"), a site prefix ("GR - Northwind Traders"), an environment tag, or a name that only differs by an encoded character all pair to the right company — as long as exactly one of your companies fits. Anything genuinely ambiguous (two companies that could both be the match) deliberately stays unmapped on the card so you can pick the right company by hand; Current never guesses. A mapping you set by hand is never overwritten by the auto-matcher — and the moment you map a customer by hand, its devices attach within seconds, instead of waiting for the next 6-hour sync.

• ＋Auto-matched: an Addigy organization or policy Current linked for you — by its Autotask account id, or by a name (direct or decorated) that unambiguously matches exactly one of your companies.
• ＋Unmapped: no unambiguous match — usually two of your companies share the name. Pick the company on the card. Its devices sync in the meantime, and they attach within seconds of you mapping it.

Not every Addigy account uses child organizations. A common single-org setup keeps everything under one master organization and separates customers as policies instead. Current handles that: each policy is listed as a customer in the mapping drawer, exactly like a child organization would be — same auto-matching, same hand-mapping. Hybrid accounts, with some real child organizations and some policy-only customers, work too; both kinds appear together in the drawer.

Addigy syncs every 6 hours on a schedule, plus whenever you press Sync now on the card. Because of the rate budget above, a first sync of a large estate may take a couple of scheduled runs to fully populate — that's expected.