Link a Client to Addigy or Pax8
A Vendor Link maps one Client to its account in one Vendor System. Refreshing records an Observed Count, and the count drives the billing.
Before you start
Every count Pippin bills from is an Observed Count: what a Vendor System reported, for a particular Link, at a particular time. A Link is what makes a count belong to a Client.
Counts push to Stripe unattended. That is the point of usage billing — a Client who added eleven Macs last month should be invoiced for eleven without anyone remembering. Staging changes for approval fails in the other direction: unreviewed quantities go stale, and a shrinking Client is quietly overbilled for months.
The guard on that
A vendor response can be successful and wrong. A renamed Addigy policy, a stale id, a permissions change or a truncated page all return cleanly — and the count collapses while nothing reports an error.
So two pushes are refused outright:
- A quantity of zero.
- A drop of more than half the last good quantity.
The previous good quantity holds instead, and the Link says so. Nobody gets billed nothing for a cycle because a policy was renamed.
Steps
- Open Settings › Integrations and connect the Vendor System once for the Org.
- Open the Client, and choose Vendor Links › Add link.
- Choose the Vendor System, then the policy or company that is this Client’s.
- Choose the metric — devices, users or licenses — and bind it to a price. One Link reporting two metrics is two Billing Lines.
- Choose Refresh. The Observed Count and the time it was read appear on the Link.
Good to know
A vendor webhook triggers a refresh; it never carries the count. Addigy and Pax8 both send events, and Pippin’s response to one is to go and read the whole thing again. A count derived from events cannot be sanity-checked against the last good one — and that check is the only thing standing between a renamed policy and a Client billed for nothing.
The hourly sweep stays running alongside the webhooks. Push is the fast path; the sweep is how you know the fast path was right.
A Client’s fleet can span several Links. Two Addigy policies during a migration is ordinary, and the comparisons that find missing devices look at all of a Client’s Links together — asking one at a time makes each report the other’s devices as missing. See Understand Device Exceptions.
Devices a Vendor System manages under the Client but in no linked policy show as a Coverage Gap on the Client’s page. Nothing else surfaces them.