Integrations — Overview
Each integration collects numbers per customer and metric during a snapshot. The table shows what each integration provides and how customers are identified.
| Integration | Provides (metrics) | Customer identity | Rename detection |
|---|---|---|---|
| ALSO Marketplace | Seats per product (monthly / annual commitment / prepayment kept separate), Azure consumption per subscription | ALSO AccountId (stable) | ✔ automatic |
| Autodesk | active users per product (60 days) | Team ID (stable) | ✔ automatic |
| Balena | Devices | own mapping organization → customer | — (own mapping) |
| Bitwarden | Seats per organization | Customer name on the API key | — (own mapping) |
| ELOVADE | Storage (TB) and more | Customer number (stable) | ✔ automatic |
| HaloPSA¹ | billable hours per charge type (proof of service) | Client ID (stable) | ✔ automatic |
| Hetzner | Servers | own mapping via project label | — (own mapping) |
| Lywand | Domains, IPv4, endpoints, network devices | Customer ID (stable) | ✔ automatic |
| MailStore | Archives per instance | Instance ID (stable) | ✔ automatic |
| Meraki | Devices per model, active license | Organization ID (stable) | ✔ automatic |
| Microsoft 365 | Licenses sold/assigned per product | Tenant ID (stable) | ✔ automatic |
| NinjaOne | Servers, workstations | Organization ID (stable) | ✔ automatic |
| Printix | printing users | Tenant ID (stable) | ✔ automatic |
| SMTP2GO | active subaccounts | Username (stable) | ✔ automatic |
| Veeam | Workloads (VB365, VBR, Cloud Connect) | Company ID (stable) | ✔ automatic |
| Manual portals | maintained values (licenses or €) | Customer name (manual) | — (manual) |
¹ In the app, HaloPSA is a separate menu item above weclapp (no entry under Integrations): services are a separate invoice document and do not appear on the weclapp license invoice — details on the HaloPSA page.
Common operation
All integrations follow the same pattern:
- Gear icon in the portal view → enter credentials → Test connection → save.
- Camera button → first snapshot.
- After that, the nightly schedule collects automatically.
Secrets are never shown again after saving; leaving a secret field empty when saving means "keep unchanged". If querying one portal fails (maintenance, expired key), the rest still collects — the affected portal is reported as failed in the snapshot result.